Windows 10: BSOD error 0x000000d1

My PC has been having issues with various Bluescreen crashes.


The latest of which casued by: 0x000000d1 0x00000000000033a0, 0x0000000000000002, 0x0000000000000000, 0xfffff8071f9eed9e.


Not sure if related but crashes have also been caused by:

0x00000101 0x0000000000000018, 0x0000000000000000, 0xffffa28000e20180, 0x0000000000000001.
0x0000009c 0x0000000000000000, 0xffff810172557d40, 0x0000000000000000, 0x0000000000000000.

0x0000009c 0x0000000000000000, 0xfffff80207c7ab40, 0x0000000000000000, 0x0000000000000000.

0x0000009c 0x0000000000000000, 0xffff90007cc2bd40, 0x0000000000000000, 0x0000000000000000.

0x00000124 0x0000000000000007, 0xffff9204b4452038, 0x0000000000000000, 0x0000000000000000.


If anyone knows a resolution to this issue it would be greatly appreciated. I also have mini dump files available if need.


Thanks.

:)

 

BSOD random the day, error 0x000000d1, 0x0000000a


Attachment 30168
Help me detect error : 0x000000d1
My laptop something BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1

I install windows 10 Pro x64.

 

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.