[BUG REPORT] nvlddmkm.sys DPC_WATCHDOG_VIOLATION (0x133) on Hibernate
Resume with RTX 5090 — Reproducible on Multiple Systems, Persists Across
Driver 591.74 and 595.97
Environment
GPU: NVIDIA RTX 5090Dv2 (GB202, Blackwell)
CPU: AMD Ryzen 9 9950X3D
Motherboard: MSI PRO X870E-P WIFI (BIOS version A40)
RAM: 96GB DDR5 6000MHz
Storage: 4TB NVMe SSD (system drive)
PSU: 1300W Platinum ATX 3.0
OS: Windows 11 (Kernel Version 26100, Build 26100)
Drivers Tested: 591.74 (original), 595.97 (DDU clean reinstall)
Summary
After resuming from Hibernate (S4 sleep state), the system consistently
crashes with a 0x133 DPC_WATCHDOG_VIOLATION bluescreen approximately
145–148 seconds after the resume completes. The crash is caused by
nvlddmkm.sys running an ISR at IRQL DISPATCH_LEVEL beyond the watchdog
timeout threshold.
This issue:
- Reproduces consistently on EVERY hibernate resume attempt
- Has been confirmed on TWO separate machines with identical hardware
- Persists across driver versions 591.74 and 595.97
- Was verified after DDU clean uninstall + fresh install of 595.97
- Does NOT occur during normal usage (gaming, rendering, desktop work)
- Does NOT occur with S3 sleep (only S4 Hibernate triggers the crash)
Reproduction Steps
- Boot the system normally and allow it to stabilize
- Initiate Hibernate via Start Menu → Hibernate, OR allow system to
auto-hibernate after idle timeout - Wait for system to fully power off (Hibernate file written to disk)
- Press power button to resume
- Wait approximately 145–148 seconds after the resume animation appears
- System crashes with 0x133 DPC_WATCHDOG_VIOLATION
Expected Result: System resumes from Hibernate and restores all
previous application state normally.
Actual Result: System crashes ~145 seconds after resume, forcing
a full cold reboot. All session data is lost.
WinDbg Analysis (!analyze -v) — Driver 595.97
BUGCHECK_CODE: 0x133 (DPC_WATCHDOG_VIOLATION)
BUGCHECK_P1: 0x1 (cumulative timeout at DISPATCH_LEVEL)
BUGCHECK_P2: 0x1e00 (watchdog period in ticks)
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
IMAGE_NAME: nvlddmkm.sys
MODULE_NAME: nvlddmkm
SYMBOL_NAME: nvlddmkm+10b2f7
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
PROCESS_NAME: System
Key Stack Frames:
nt!KeBugCheckEx
nt!KeAccumulateTicks+0x59c
nt!KiUpdateRunTime+0x9b
nt!KeClockInterruptNotify+0x3ee
nt!KiCallInterruptServiceRoutine+0x32c
nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
nt!KiInterruptDispatchNoLockNoEtw+0x3c
[interrupted context: nvlddmkm+0x10b2f7]
Cross-Version Comparison
The FAILURE_ID_HASH is identical across both driver versions, confirming
this is the same underlying bug:
Driver 591.74: SYMBOL_NAME = nvlddmkm+107467
FAILURE_ID_HASH = {f97493a5-ea2b-23ca-a808-8602773c2a86}
Driver 595.97: SYMBOL_NAME = nvlddmkm+10b2f7
FAILURE_ID_HASH = {f97493a5-ea2b-23ca-a808-8602773c2a86}
The offset differs between versions (due to recompilation), but the
crash fingerprint is identical, indicating the same code path is
responsible in both driver releases.
Secondary Effects
After each crash-induced cold reboot, the DeepCool AIO liquid cooler
(connected via USB) fails to reinitialize correctly. The pump and fans
display 0 RPM in the DeepCool control software, and CPU temperatures
rise abnormally. This is a secondary consequence of the abrupt USB
controller reset caused by the crash, not an independent hardware fault.
Confirmed Workaround
Disabling Hibernate entirely via:
powercfg /h off
and using S3 sleep instead completely avoids the crash. This confirms
the bug is specific to the S4 Hibernate resume power state transition
(D3cold → D0) in nvlddmkm.sys.
What Has Been Ruled Out
- Hardware defect: Issue reproduces on two independent machines
- Driver installation corruption: DDU clean install confirmed
- Specific driver version: Both 591.74 and 595.97 affected
- Third-party software conflict: Secondary machine has minimal software
- AMD chipset driver issue: Updated to latest version 7.12.04.858
- Memory issue: System is fully stable during all non-hibernate usage
Attachments
- Minidumps_RTX5090Dv2_HibernateBluescreen.zip (multiple .dmp files
from both driver versions) - WinDbg_Analysis_RTX5090Dv2.txt (full !analyze -v output
from driver 595.97) - SystemInfo_RTX5090Dv2_BugReport.txt (msinfo32 full system info)
- DxDiag_RTX5090Dv2_BugReport.txt (DirectX diagnostic report)
- GPUZ_RTX5090Dv2.png (GPU-Z screenshot showing
GPU and VBIOS details) - EventLog_KernelPower41_6008.evtx (Windows Event Log showing
Kernel-Power Event ID 41
and 6008 crash records)
Request
We are requesting that NVIDIA engineering investigate the nvlddmkm.sys
ISR timeout occurring during S4 Hibernate resume on RTX 5090 (GB202 /
Blackwell architecture). Specifically, we believe the D3cold-to-D0
power state transition sequence during Hibernate resume contains a code
path where an interrupt service routine does not complete within the
Windows DPC watchdog timeout window (~7680ms at DISPATCH_LEVEL).
Given that this issue:
- Affects multiple independent systems with identical hardware
- Persists across multiple driver versions
- Is fully reproducible on demand
- Renders the Hibernate feature completely non-functional on
RTX 5090 systems
We believe this warrants a high-priority fix in an upcoming driver
release.
Thank you for your attention to this report.
Reporter Information
Hardware confirmed affected:
Machine 1: Reporter_A
Machine 2:Reporter_B