Windows 10: BSODs with various errors

Hi all, Last night I started experiencing BSODs with various error codes, detailed chronologically below. I had not made any changes to my system in recent times. sfc scannow, dism checks, and memtest came back clean. SYSTEM_SERVICE_EXCEPTION 3bAn exception happened while executing a system service routine.PROCESS_NAME: postgres.exe IMAGE_NAME: ntkrnlmp.exeChanges made: Uninstalled postgres.exeKMODE_EXCEPTION_NOT_HANDLED 1ePROCESS_NAME: SystemIMAGE_NAME: ntkrnlmp.exe

:)

 

Various BSOD Errors Help

Hey all,

I've received multiple BSOD errors the past 2 days after rebuilding my PC. I've been trying to figure out the issue.

These are the few BSOD messages I remember seeing:

• DPC_WATCHDOG_VIOLATION (multiple times)
• CRITICAL_PROCESS_DIED (one time)
• IRQL_NOT_LESS_OR_EQUAL (one time)
• WHEA_UNCORRECTABLE_ERROR (multiple times)

Here's a link to the dmp files and system information: WindowsIssue

Steps I've taken:

• fully updated drivers
• applied all Windows updates
• Removed unnecessary hardware
• Monitored CPU/GPU temps (log file on temps during last crash in share)

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.