Error encountered, system crashing.
Error encountered, system crashing.
I repeatedly encounter Event ID 153 from the source nvlddmkm, which prevents the system from functioning properly. My PC frequently restarts unexpectedly, and I've learned it's a BSOD. The diagnostic report shows: 0x00000116 (0xffff8b858fbee010, 0xfffff8076a531a40, 0xffffffffc000009a, 0x0000000000000004). A dump file is stored at: C:\WINDOWS\Minidump\120525-5375-01.dmp. Related documents are available here: https://drive.google.com/drive/folders/1...drive_link. For these files, the specifications are: MAG B550 Tomahawk 5600x Stock Cooler PNY 3060 12gb 16gb ram T-Force 2x8GB Samsung 980 650W Corsair PSU (model number omitted). I've attempted various fixes: reseating the GPU, updating DDU, installing newer NVIDIA drivers, switching PCIE slots, using older driver versions, performing a clean Windows install, reverting to Windows 10, and checking with Samsung Magician. The NVMe drive appears intact, and I've run chkdsk multiple times. After reinstalling drivers, I still can't locate nvlddmkm in C:\Windows\System32\drivers. This issue has persisted for three days. Help needed.
The exact RAM model is not specified, but it refers to a specific type and quantity. There are 4 sticks.
Thanks for the quick message. My rams are T Force tuf gaming 2x8GB, using dimm slots 2 and 4. I also have xmp turned off.
Here are some examples you can use:
- Nvidia frequently released questionable driver updates, making it challenging to stay updated.
- Users on different networks, like 572.83 DCH, noticed significant changes in stable versions (e.g., from 566.36 to newer numbers).
- Many people experienced memory-related issues with this SSD, despite the device's rated performance.
Verify the GPU on another machine to confirm functionality. This issue might stem from hardware failure, driver loading problems after initial setup, or faulty RAM/CPU. In extreme cases, update the motherboard firmware, reset to defaults, reinstall the OS, and then install the chipset driver.
In the six dump files, two DPC_Watchdog_Violation errors point to the Nvidia GPU. These indicate a failure in the ISR (Interrupt Service Routine). This pattern is common with defective Nvidia cards. The ISR itself doesn’t seem unusual, so the reason it triggers remains unclear. The other four files display a Video_TDR_Failure. This crash shows the GPU stopped responding, Windows reset the driver, but the GPU remained unresponsive, prompting a BSOD. This is essentially a timing issue, not a driver problem. Event ID 153 signals a timeout, suggesting the GPU vanished rather than the driver failed (nvlddmkm.sys is the Nvidia GPU driver). EDIT: To clarify further, a device timeout means it stops responding to requests, which Windows treats as disappearing. These errors were strong indicators of a faulty GPU before. In January of last year, Nvidia released updated drivers. They’ve improved since then, though still not ideal. The 3000 series was less impacted than the 4000 and 5000 series, but some users continued to face problems. The most reliable way to distinguish between driver and GPU issues is using DDU to uninstall the current driver and install a newer one from December 2023, as we’re certain the previous driver was affected by recent problems. DDU guide available – link to version 566.36.
Hi everyone, I’m a friend of @Zeeeeen and assisted with checking and fixing his PC. Here’s what I did: Initially, I cleaned each part (RAM, NVMe, GPU, CPU) and their matching slots. I also replaced the thermal paste on both the GPU and CPU, reinserted everything, and verified all parts were correctly seated. Next, I performed a fresh OS installation. Then, following @Kisai’s advice, I updated the BIOS, installed the motherboard chipset drivers, and added the newest NVIDIA drivers. After that, I ran the Monster Hunter Wilds Benchmark multiple times—at least eight runs—and tested it while streaming YouTube or similar content in the background. I kept this process running for around three hours, and everything stayed stable—no crashes or restarts. The only drawback was that I couldn’t identify the exact faulty component, though @Bjoolz had a valid observation about my friend’s situation. Now I returned the PC to @Zeeeeen, and we’re still checking if the problem remains.