B
blake.boman
Hello,
I have been having random BSODs ever since upgrading to Windows 10 build 2004 a little over a month ago. The specific bug check is 0x133, DPC_WATCHDOG_VIOLATION. I've loaded the minidump in BlueScreenView, and it shows the culprit is ntoskrnl.exe. I've attempted running "sfc /scannow" and "dism /online /cleanup-image /restorehealth" -- both succeed with no corrupt files found. I've also run chkdsk and it did not find any issues either. Are there any known issues with this build of Windows 10 that could cause this error? From what I've read, this BSOD is typically caused by drivers. If so, what additional steps can I take to determine which one is causing it? The guides I've seen all reference BlueScreenView should inform me of that, but it doesn't show anything more than ntoskrnl.exe.
Thanks for any help you can provide!
Continue reading...
I have been having random BSODs ever since upgrading to Windows 10 build 2004 a little over a month ago. The specific bug check is 0x133, DPC_WATCHDOG_VIOLATION. I've loaded the minidump in BlueScreenView, and it shows the culprit is ntoskrnl.exe. I've attempted running "sfc /scannow" and "dism /online /cleanup-image /restorehealth" -- both succeed with no corrupt files found. I've also run chkdsk and it did not find any issues either. Are there any known issues with this build of Windows 10 that could cause this error? From what I've read, this BSOD is typically caused by drivers. If so, what additional steps can I take to determine which one is causing it? The guides I've seen all reference BlueScreenView should inform me of that, but it doesn't show anything more than ntoskrnl.exe.
Thanks for any help you can provide!
Continue reading...