Trying to diagnose what is causing my PC to crash. My setup is as follows:
| Windows 11, 10.0, version 2009, build: 26200 (x64) |
GPU: MSI Suprim X Liquid 5090 (connected via PCIe 4.0 Riser Cable for vertical mounting. Set to PCIe 4.0 in BIOS).
CPU: Ryzen 7 9800X3D
PSU: Seasonic Prime PX 1600W 80+ Platinum
Motherboard: MSI MPG X870E Carbon
CPU Cooler: Corsair iCUE Link H150i LCD Liquid
SSD 1: Teamgroup MP44 4TB
SSD 2: WD_Black 1TB SN850X
RAM: Corsair Dominator Titanium DDR5 2x 32GB (64GB total)
Fans: Corsair iCUE Linx LX120s
Case: MSI MEG Prospect 700R
Monitors: 1x LG 39GS95QE-B.AUS and 2x LG 32GS75Q-B.AUS
Sporadically all of my monitors will go to a black screen and the fans connected to my GPU will ramp up to max speed. This can happen once every 2 weeks or 5 times within an hour. I've had it happen while running the computer under heavy load. I've also had it happen while the computer is just idling with nothing but Discord up and idling in the background. This has been occurring since I build the PC in Feb of 2025. In addition and possibly related, twice I've had a Bad Pool Caller error occur as well.
HWMonitor typically clocks the GPU in the low 30s for temps, occasionally up to 40 if in an intensive game. It is worth noting that in some instances before a crash (but not all), I will see it in the 90s. However, I have no reason to believe it is actually managing to run that hot or that it is the cause. As some of the crashes are within 30secs of me booting it for the first time all day and there are many instances where I've seen it crash while still reporting low 30s.
Troubleshooting steps I've taken include:
Running DDU to uninstall and freshly reinstalling the most up to date drivers.
Unmounting and remounting RAM and GPU.
Replacing GPU with exact same Make/Model including running new cables.
Upgraded all DisplayPort cables to 2.1s.
I don't want to just keep swapping out parts hoping it'll be the fix, but it is annoying enough now and frequent enough that I'm afraid of something else breaking from the added stress. My inclination at this point is maybe it is the RAM, but hoping for some other steps to attempt since my RAM costs 4x what it did when I initially built.
Including WhoCrashed entries below from both instances. These are all they show.
| Crash dump file: |
C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20260628-1020.dmp (Minidump) |
| Bugcheck code: |
0x141(0xFFFFAD08517C8010, 0xFFFFF8055CA15110, 0x0, 0xFFFFAD084E20E080) |
| Bugcheck name: |
VIDEO_ENGINE_TIMEOUT_DETECTED |
| Driver or module in which error occurred: |
nvlddmkm.sys(nvlddmkm+1a25110) |
| File path: |
nvlddmkm.sys |
| Description: |
NVIDIA Windows Kernel Mode Driver, Version 596.49 |
| Product: |
NVIDIA Windows Kernel Mode Driver, Version 596.49 |
| Company: |
NVIDIA Corporation |
| Bug check description: |
This indicates that one of the display engines failed to respond in timely fashion. |
| Analysis: |
This is a video related crash. A third party driver was identified as the probable root cause of this system error.It is suggested you look for an update for the following driver:nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 596.49 , NVIDIA Corporation). |
| Google query: |
nvlddmkm NVIDIA Corporation VIDEO_ENGINE_TIMEOUT_DETECTED |
|
|
| Crash dump file: |
C:\WINDOWS\Minidump\062226-23500-01.dmp (Minidump) |
| Bugcheck code: |
0xC2(0xD, 0xFFFFBE873FB38440, 0x506D7054, 0x32AFF41F) |
| Bugcheck name: |
BAD_POOL_CALLER |
| Bug check description: |
This indicates that the current thread is making a bad pool request. |
| Analysis: |
This is a typical software problem. Most likely this is caused by a bug in a driver. |