Windows 10: Occurrence of BSOD errors

HiI had never gotten a BSOD error on my 4 year old laptop, but for some reason this has happened twice in the span of a week now. Both of these times was while I was working on something - one time during a zoom call while working on Photoshop, the otherwhile I was just listening to an audiobook and playing microsoft games. I don't know the reason for the sudden problems.I have not really tried anything except for the standard BSOD troubleshooter which didn't help. I saw a few threads online and am sharing a OneDrive link with the minidumps attached. I tried to see if I could figure out some

:)

 

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.

 

Weird occurrence - desktop won't load, spinning wheel etc

Ok here is the MR steps to be sure I am completing this properly - same error thought.
Step 1



Step 2



Step 3



Step 4



step 5



Step 6 - Error




- - - Updated - - -

EDIT : I did what you said and tried without G (second time, didn't take screen shots), same error. I did notice that NTFS Primary 3 (NONE) doesn't have a drive letter associated with it?

 

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.