Windows 10: Periodic BSOD with kernel_data_inpage error

Here are my minidumps.


https://1drv.ms/u/s!AvV603ywPTGaao_Vkktj6sjZKzU?e=wYRJDB


I've done nothing so far that would be concrete to fix this because i don't know how to approach the problem, or what works in full.


The crashes started periodically on December 2020 and has lessened in frequency, but still occur to this day, the latest one being hours ago from posting this thread. I have tried some diagnostic tools and methods that i have stumbled upon. Namely: Bluescreenview, pointing the errors to "caused by driver: ntoskrnl.exe"; and i've also tried stressing my drivers with driver verifier in windows, which led to a loop of failed fixing caused by "iastora.sys". I've gotten away from the reboot loop eventually by booting in safe mode and cancelling the driver verifier.


I've done system checks and memory checks: sfc/scannow, memtest, and checkdisk. none displaying errors.

i've also right clicked my hard drives to used the 'check' in the 'tools' tab. at times it says that there's nothing wrong with the drive, and at times it says "unable to repair drive". this only occurs in drive D: and never on C:.


i need help to fix this as the random BSODs are a pain to encounter in the middle of the work I'm doing on my computer.

:)

 

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.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile