Hello again, and welcome.
Of the five dumps uploaded, four of them are Nvidia graphics related, the nvlddmkm.sys Nvidia graphics driver is referenced in all of them. Two of these are TDR timeout failures, that's the Windows Timeout Detection and Recovery feature trying to recover by resetting the graphics card and driver - that will cause a crash to desktop. The first suspect in these cases is the Nvidia graphics driver, the version you have is recent....
Code:
2: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff807`a1fb0000 fffff807`a5a06000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Mar 1 19:55:35 2024 (65E21697)
CheckSum: 0393217E
ImageSize: 03A56000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
However the
Nvidia drivers download website has a more recent driver (552.12 dated 4th April 2024). I would initially suggest that you install that driver.
It's also well worth removing the graphics card and re-seating it firmly. Sometimes that helps with these kinds of issue.
I would also check your chipset drivers because your System log contains a number of WHEA errors for the PCIe root port...
Code:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 15/04/2024 01:11:29
Event ID: 17
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP-677QF36
Description:
A corrected hardware error has occurred.
Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)
Primary Bus:Device:Function: 0x0:0x1:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_8086&DEV_4C01&SUBSYS_373317AA&REV_01
Secondary Device Name:
These may be symptoms of the graphics card issue of course but it's important to check with the Lenovo website.
BTW. Your System and Application logs don't even cover a whole day. If you regularly clean these logs then please stop. They often contain valuable clues, especially historical clues, when you're having problems like this.
The fifth dump is an outlier in that nvlddmkm.sys isn't referenced, it doesn't look like a graphics operation was in progress either. The dump contains a 0xC000001D exception code, that's an illegal instruction execution attempt. Whilst several things can cause this exception bad RAM is one of the common causes. In addition, two of the nvlddmkm.sys dumps fail with 0xC0000005 exceptions - a memory access violation. This exception can also have many causes, bad RAM being a common one. For these reasons I think it worth the effort of running Memtest86 on your RAM to see whether that's the real cause...
- Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
- Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
- If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Let us know how all that goes. If it BSODs again after you've done all the above then please run the SysnativeBSODCollectionApp again and upload the new output. And PLEASE stop clearing logs!
