Windows 10: Hi, i am currently facing a lot of BSOD errors

the stop code is DPC WATCHDOG VIOLATION, attaching the dump file here https://1drv.ms/u/s!AgUM28rmVhcPgUzsVOeODWkqzV94?e=U06uGVhttps://1drv.ms/u/s!AgUM28rmVhcPgUtQMHqTBPcxSfe6?e=MVDiAl

:)

 

Lots of BSOD's

Hi everyone, over the past week or so I've been facing the nightmare of many blue screens of death. At first, the messages on the BSOD's were not consistent, always changing and it made it very difficult to pinpoint the issue. I've an SSD running my windows
and a HDD for games etc. Aswell as the BSOD's, I've been facing tons of application crashes, whether that be google chrome tabs going "Aw Snap!" or outright application crashes, typically games though even smaller applications like the messaging service discord.
It's important to note that some days I have a lot less application crashes and BSOD's than other which is confusing to me. Tuesday I only had 1 in the evening after work, whereas Wednesday I faced several and tons of application crashes.

The errors are not on startup, sometimes my PC can be fine for a few hours or even several hours before they begin.

I've done many different troubleshooting things, including:

• Ran a full scan with McAfee, also downloaded malwarebytes, run it and found no virus
• sfc /scanow which stated it fixed some issues but it did not fix my problem
• chkdsk on my C Drive (SSD) which contains windows and it stated there were no errors
• Used DDU to uninstall my nvidia drivers (i have a 1070) and then clean installed ones from early last year. I faced further BSOD's after this, so I repeated the process but instead installed nvidia drivers from December. The blue screens were not as common
  however were still occurring, so I repeated the same process and installed the newest NVIDIA drivers that came out this week, where it was fine for a day and then the following day I faced tons of BSOD's and application crashes - so much so it was almost impossible
  to do anything on my computer.
• I've reset windows twice, saving my files the first time, wiping them the second time.
• I've used CCleaner to fix any registry issues
• I've used windows memory diagnostic which reported back no errors at the time.
• I've done windows startup repair which stated it was unable to repair my PC - stating how it created a log file called "E\Windows\System32\Logfiles\Srt\SrtTrail.txt"

Some of the BSOD's I've faced include the errors:

• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (the most common error here)

• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgmms2.sys)
• KMODE_EXCEPTION_NOT_HANDLED
• KMODE_EXCEPTION_NOT_HANDLED (Ntfs.sys)
  
• PAGE_FAULT_IN_NONPAGED_AREA
• CRITICAL_STRUCTURE_CORRUPTION (haven't had one of these since last week)
• REGISTRY_ERROR (first one yesterday evening)

Checking windows event viewer, some of the applications crashing included:

• mmc.exe
• ntdll.dll
• Display driver nvlddmkm stopped responding and has successfully recovered

Any guidance or questions are greatly appreciated, many thanks in advance if anyone can help me fix this mess.

 

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.