Laptop crashes playing two games

Nutty_Bara · Nov 15, 2023

Red Dead 2 & Horizon Zero and I think one time playing Shadow of the Tomb Raider
WhoCrashed said its the CPU

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

wiganken · Nov 15, 2023

It may be heat related but more details would help others to help you.
Windows build?
How much RAM?
Screen shot photos of any on-screen messages when crash happens.

ubuysa · Nov 15, 2023

Please make the Google Drive file public (ie. available to anyone with the link).

Nutty_Bara · Nov 15, 2023

32GB of RAM
There is no heat when it crashes its been more hotter and games have run fine
WinBuild 10.0.22631 22631
Zero Dawn is on Steam Red Dead is on Epic I play it through Steam so my controller works
Just a stranded whea uncorrectable error screen

Nutty_Bara · Nov 15, 2023

I changed the Drive setting

wiganken · Nov 15, 2023

Nutty_Bara said:
WinBuild 10.0.22631 22631

If you are on Windows 10 you may get better help if you post on tenforums. This is the windows 11 forum. Good luck.

Nutty_Bara · Nov 15, 2023

wiganken said:
If you are on Windows 10 you may get better help if you post on tenforums. This is the windows 11 forum. Good luck.

wiganken · Nov 16, 2023

That screenshot looks so different to what I expected to see when looking for Win 11 version and build. See photo of what I see on my machine. Are you running a non-standard version of W11?
Your W11 screenshot is missing some info so try windows update.

See: - How to fix WHEA_UNCORRECTABLE_ERROR - Microsoft Support

Also see: - How to Fix the WHEA Uncorrectable Error

ubuysa · Nov 16, 2023

From the four 0x124 WHEA_UNCORRECTABLE_ERROR dumps, the argument 1 value of 0x4 indicates that the hardware exception was in the PCI subsystem. If we examine the PCIe section of the error record (address in argument 2) we can see the VEN and DEV idea of the PCI device that's failing...

Rich (BB code):

===============================================================================
Section 0     : PCI Express
-------------------------------------------------------------------------------
Descriptor    @ ffffc48a0c5750a8
Section       @ ffffc48a0c5751c8
Offset        : 416
Length        : 208
Flags         : 0x00000001 Primary
Severity      : Fatal
fffff805224099a0: Unable to get Flags value from nt!KdVersionBlock

Port Type     : Root Port
Version       : 1.1
Command/Status: 0x0407/0x0010
fffff805224099a0: Unable to get Flags value from nt!KdVersionBlock
Device Id     :
  VenId:DevId : 8086:a0bc
  Class code  : 030400
  Function No : 0x00
  Device No   : 0x1c
  Segment     : 0x0000
  Primary Bus : 0x00
  Second. Bus : 0x00
  Slot        : 0x0000
Dev. Serial # : 0000000000000000
fffff805224099a0: Unable to get Flags value from nt!KdVersionBlock
Express Capability Information @ ffffc48a0c5751fc
  Device Caps : 00008001 Role-Based Error Reporting: 1
  Device Ctl  : 0027 ur FE NF CE
  Dev Status  : 0011 ur fe nf CE
   Root Ctl   : 0008 fs nfs cs
fffff805224099a0: Unable to get Flags value from nt!KdVersionBlock

The VEN and DEV values of 8086 and 0ABC identifies the device as the Intel (8086) PCIe Root Port (0ABC).

This could be a motherboard issue of course, or even a PCIe device issue possibly, but it may also simply be a driver issue....

Pop all PCIe cards out and reset them fully.
Ensure that any additional PCIe card power cables (graphics card, WiFi/Bluetooth card, etc.) are fully connected at both ends.
Check your motherboard vendor's website for updated chipset drivers and install them.
If there are no new drivers there the download the Intel Driver & Support Assistant and run that looking for updated Intel drivers.
If that finds no new drivers then check your motherboard vendor's website for a BIOS update and install that.
If all the above fails then check that your PSU is good and of sufficient power.

If none of that helps then I would suspect the motherboard.

BTW. The fifth dump is a 0xEF CRITICAL_PROCESS_DIED bugcheck. The dump shows the failing process (from argument 1) as svchost.exe...

Code:

0: kd> !process ffffa98758ade080
PROCESS ffffa98758ade080
    SessionId: 0  Cid: 058c    Peb: f1845e4000  ParentCid: 039c
    DirBase: 1e06d6000  ObjectTable: ffffe208fa258b40  HandleCount: <Data Not Accessible>
    Image: svchost.exe
    VadRoot ffffa98758a3ab10 Vads 151 Clone 0 Private 1413. Modified 10. Locked 2.
    DeviceMap ffffe208fa307a70
    Token                             ffffe208fa257060
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         114296
    QuotaPoolUsage[NonPagedPool]      27232
    Working Set Sizes (now,min,max)  (3630, 50, 345) (14520KB, 200KB, 1380KB)
    PeakWorkingSetSize                3528
    VirtualSize                       2101364 Mb
    PeakVirtualSize                   2101369 Mb
    PageFaultCount                    4215
    MemoryPriority                    BACKGROUND
    BasePriority                      8
    CommitCharge                      1543
    Job                               ffffa9874f1b6040

        *** Error in reading nt!_ETHREAD @ ffffa98758a74080

I'm sure you know that svchost.etc runs a great many services that exist only as dlls. It's very likely of course that svchost failed because of the PCIe problem we already know you have.

Helmut · Nov 16, 2023

With Laptops like that it is likely to be a heat problem in which case you need to install some monitoring Application for temperature.

I use CPUID HWMonitor which you can run and it will store the maximum temperatures reached for various items of hardware.

Maybe use 3DMark benchmark which will give you a graph of temperatures of hardware on a timeline, one of which is the CPU.

Precise readings of internal hardware are needed rather than an impression.

Lenovo Vantage App has some basic Hardware Scan (diagnostics).

Make sure ventilation grills under the Laptop are clear and there is sufficient room for air flow.

Nutty_Bara · Nov 17, 2023

Used CPUID HWMonitor CPUs high temp 64C. Everything passed on the hardware scan

Helmut · Nov 17, 2023

Not enough info, what you are showing is an idle temperature, of what hardware you have not said, nor the utilisation %.

The idea is to experiment and take measurements with 100% CPU and 100% GPU utilisation, then change the game settings to lower the CPU and GPU max utilisation to say 50% or something like that.

Then see if these games crash with lower utilisations and probably a bit lower maximum temperatures.

Nutty_Bara · Nov 21, 2023

Lowest settings i can put them HZD a few sec. before it crashed RDR2 about 30seec.

zbook · Nov 21, 2023

1) Download and install the most up to date BIOS:

BIOS Version/Date LENOVO H4CN23WW(V1.08), 2/11/2022

23WW > 33WW

BIOS Update for Windows 10 (64-bit) and Windows 11 (64-bit) - IdeaPad Gaming 3-15IHU6 - Lenovo Support US

pcsupport.lenovo.com

2) Run the various types of Lenovo hardware diagnostics:

If available run the UEFI hardware diagnostics in addition to the custom diagnostics.

Post images or share links displaying the tests performed with results into the newest post.

3) If upgrading the BIOS does not alter the computer unexpected shutdowns and restarts or BSOD consider contacting Lenovo for costs and terms and conditions to extend a warranty.

Nutty_Bara · Nov 24, 2023

Well it appears to be fixed HZD still crashes but its just the game so I live with that.
Updated the BIOS still crashed so I downloaded same other recommended updates. Turned it on/off a baker's dozen times to run a UEFI hardware diagnostics didn't find anything

zbook · Nov 25, 2023

In two days please post a new V2 share link into the newest post.

Nutty_Bara · Nov 27, 2023

GLT-(2023-11-27_14-51-33).zip

drive.google.com

Nutty_Bara · Nov 27, 2023

GLT-(2023-11-27_14-51-33) - Google Drive

drive.google.com

ubuysa · Nov 28, 2023

The three 21st Nov dumps are identical to the others I've looked at for you. They are 0x124 WHEA_UNCORRECTABLE_ERROR bugchecks with an exception indicating a PCIe failure.

I've had a look through your System log and there are several worrying entries in there. The first concerns McAfee...

Code:

Event[18468]
  Log Name: System
  Source: Service Control Manager
  Date: 2023-11-22T07:25:35.9440000Z
  Event ID: 7024
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Seans_GLT
  Description:
The McAfee Maintenance Service service terminated with the following service-specific error:
The specified module could not be found.

Bad third-party drivers can, under some circumstances, cause 0x124 BSODs. All third-party anti-malware products cause BSODs on many systems. I recommend you uninstall McAfee using their specialised tool and rely only on Windows Defender and Windows Firewall - these are plenty good enough. See whether the BSODs stop before doing anything else.

Also, turn Windows Fast Startup off. You appear to have it on and it's known to cause issues with some motherboards and some drivers. With an NVMe drive as your boot drive you get no benefit from Fast Startup in any case.

There are some more worrying errors in the System log however...

Code:

Event[21944]
  Log Name: System
  Source: disk
  Date: 2023-11-27T12:24:21.7410000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Seans_GLT
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[21617]
  Log Name: System
  Source: nvlddmkm
  Date: 2023-11-26T22:05:22.3340000Z
  Event ID: 0
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Seans_GLT
  Description:
N/A

Event[21618]
  Log Name: System
  Source: Display
  Date: 2023-11-26T22:05:23.4820000Z
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info  g
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Seans_GLT
  Description:
Display driver nvlddmkm stopped responding and has successfully recovered.

Event[20558]
  Log Name: System
  Source: Netwtw10
  Date: 2023-11-25T04:19:37.6540000Z
  Event ID: 5005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Seans_GLT
  Description:
Intel(R) Wi-Fi 6 AX201 160MHz : Has encountered an internal error and has failed.

We have a storage drive error (for your NVMe), a graphics card/driver error, and an AX201 WiFi card/driver error. I don't believe that all three devices have had issues at the same time in a three day period. I don't think this is RAM at all, I think it's more likely to be the motherboard.

Remove McAfee and Fast Startup first though, and before you spend any money.