BSOD warning during Windows 10 startup linked to DPC watchdog and error code 133
BSOD warning during Windows 10 startup linked to DPC watchdog and error code 133
Hello, I recently purchased a new HP laptop a few weeks ago, but I frequently encounter the BSOD with a Watchdog violation warning. The crash mostly happens after opening Task Manager and selecting the Network column in the Performance section. I've tried almost all possible solutions without success. - I reinstalled drivers from HP, Microsoft updates, and third-party software, but it didn't work. - After reinstalling the Nvidia driver using DDU and performing a clean install via the Nvidia installer, the issue persisted. - Disabling the discrete GPU in Device Manager, updating the BIOS, reverting to an older BIOS version, and reinstalling the Nvidia driver didn't resolve it. - Cleaning the Windows installation multiple times hasn't helped either. - The maintenance team mentioned they couldn't identify the problem and didn't experience it during their testing. A notable sign is that the fan noise increases slightly before the crash, then becomes a bit louder afterward. Is this normal behavior for a new 11th Gen laptop? I've uploaded system logs from V2 log collector, including dump files and WhoCrashed reports. Could you help me fix this issue? My laptop is brand new and hasn't been used extensively yet. Thank you, DESKTOP-FIEP1AD-(2021-04-22_22-38-49).zip MiniDumps 22-4.zip
Apology for not informing the model... the character is an HP Pavilion 15-dw3008ne. Thanks.
I’m about to share some useful details from the crash dump file. Below are my observations on what’s happening. ___ DPC_WATCHDOG_VIOLATION (133) The DPC watchdog flagged an extended runtime at an IRQL of DISPATCH_LEVEL or higher. Evidence suggests Arg1: 0000000000000000, meaning a single DPC or ISR surpassed its time limit. Usually, the source can be traced via a stack trace. Arg2: 0000000000000501 indicates the DPC time count in ticks. Arg3: 0000000000000500 shows the allocated DPC time in ticks. Arg4: fffff80277afb320, converted to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which adds further context about this particular timeout issue. BUGCHECK_CODE: 133 with several related check values. This situation is helpful because it narrows down the problem to a single event. It points toward a video driver problem—either the driver is failing or the hardware is faulty. Try using DDU to reset the driver, make sure Windows 10 is up to date, and install only the necessary driver for your graphics card (avoid unnecessary packages like GeForce Experience).
I'm glad you reached out. The changes you made to the Intel PPMC value appear to have resolved the issue temporarily. There don't seem to be any major problems with that setting right now.
Using MemTest86 is recommended. You didn't apply any registry changes, and I wasn't sure where you found this information online.