Windows 10: Persistent BSOD with NPC_WATCHDOG_VIOLATION error

I keep blue screening with NPC_WATCHDOG_VIOLATION and have tried looking at the minidump files. I already tried updating my NVIDIA gpu drivers, but I'm honestly not too sure what is the issue. I play games and this never happens when I play. Only when I'm streaming video or listening to music. Since I predominantly use this PC for gaming, I feel like that might not be a coincidence, but I'm not sure. Any help would be appreciated.

:)

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

Persistent BSOD ntoskrnl.exe

Ok understood CW. Could it be possible that even though the memory used is in the QVL list for the motherboard that it would still cause BSODs? I don't really feel like futzing with Memtest so would next steps be updating to latest BIOS, installing all RAM and then retesting?