cancel
Showing results for 
Search instead for 
Did you mean: 

Gl702vm: Dpc_watchdog_violation

Matt2097
Level 8
Just got my 2nd blue screen with "DPC_WATCHDOG_VIOLATION" cited as the cause.

A quick Google suggests that it might be a rogue driver, but wondered if anyone else had had this issue, & if so whether they managed to solve it.
2,547 Views
3 REPLIES 3

Matt2097
Level 8
So, a little more digging indicated that this error can be caused by any driver issue.

The dump file told me:
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

I'm updating the Nvidia drivers to the latest version in the hope that it will resolve my problems. If anyone has any other thoughts, please let me know.

May also want to run SFC /Scannow seems win32k.sys might be corrupt.

Matt2097
Level 8
In case anyone visits this thread in the future, suffering the same issues - driver update seems to have resolved the issue.

I'm assuming the win32k in the log was just due to the nvidia driver causing issues.