Help with bugcheck analysis KERNEL_DATA_INPAGE_ERROR

[Surfdude1982]

I often get the BSOD KERNEL_DATA_INPAGE_ERROR on my new self-assembled pc.
Could you help me analyzing the debugging details? Do I have a hardware problem?

Thx for your help!

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6e00063fa58, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000003f, error status (normally i/o status code)
Arg3: 000000023a328880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffc000c7f4b7e2, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000003f - {Ongeldige CRC} Fout in een controlesom van de cyclische redundantiecontrole (CRC).

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.The data read from storage does not match the original data written.This indicates the data was corrupted by the storage stack, or device hardware.

BUGCHECK_STR: 0x7a_c000003f

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: GROOVE.EXE

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

TRAP_FRAME: ffffd000229f04e0 -- (.trap 0xffffd000229f04e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000202c7000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000eda0b20 rsp=ffffd000229f0670 rbp=000000000bdb0000
r8=ffffc000c7f4b7e2 r9=0000000000000fff r10=0000000000000003
r11=ffffc000c7f4b7e2 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiRelocateImagePfn+0x2a0:
fffff800`0eda0b20 410fb613 movzx edx,byte ptr [r11] ds:ffffc000`c7f4b7e2=00
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000eb809db to fffff8000eb57ca0

STACK_TEXT:
ffffd000`229f0168 fffff800`0eb809db : 00000000`0000007a fffff6e0`0063fa58 ffffffff`c000003f 00000002`3a328880 : nt!KeBugCheckEx
ffffd000`229f0170 fffff800`0ea6d9e0 : 00000000`00000002 ffffd000`229f02d8 fffff800`0ed62dc0 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1881b
ffffd000`229f0260 fffff800`0ea5a68a : fffff800`0ed62dc0 ffffe000`38b61880 00000000`00000000 00000001`00000000 : nt!MiIssueHardFault+0x184
ffffd000`229f0320 fffff800`0eb61f2f : 00000000`00000000 00000000`00000004 00000000`00000000 00000007`00000000 : nt!MmAccessFault+0x5ba
ffffd000`229f04e0 fffff800`0eda0b20 : 00000000`0bdb0000 00000000`6eab2000 ffffc000`c7f4a000 00000000`00000000 : nt!KiPageFault+0x12f
ffffd000`229f0670 fffff800`0ea40d0b : 00000000`00000ff8 ffffe000`3b3490e0 00000000`00000003 ffffc000`10000000 : nt!MiRelocateImagePfn+0x2a0
ffffd000`229f0710 fffff800`0ea6bc87 : ffffe000`36d4e750 ffffe000`38b238c0 ffffe000`3b349150 ffffe000`36d4e918 : nt!MiValidateInPage+0x1fb
ffffd000`229f0790 fffff800`0ea6d9e0 : 00000000`00000003 ffffd000`229f08f8 ffffe000`38b23d98 ffffd000`00000000 : nt!MiWaitForInPageComplete+0x29f
ffffd000`229f0880 fffff800`0ea5a68a : ffffe000`38b23d98 ffffe000`38b61880 00000000`00000008 00000000`00003dff : nt!MiIssueHardFault+0x184
ffffd000`229f0940 fffff800`0eb61f2f : 00000000`00000008 00000000`00000000 00000000`7f768001 ffffe000`38b5e170 : nt!MmAccessFault+0x5ba
ffffd000`229f0b00 00000000`775f4100 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
00000000`0400f6ec 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775f4100


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1881b
fffff800`0eb809db cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1881b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6

IMAGE_VERSION: 6.3.9600.17736

BUCKET_ID_FUNC_OFFSET: 1881b

FAILURE_BUCKET_ID: 0x7a_c000003f_nt!_??_::FNODOBFM::_string_

BUCKET_ID: 0x7a_c000003f_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7a_c000003f_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH: {35f7dc2f-9d4e-79ab-5aab-b1994d114d0f}

Followup: MachineOwner

 

[johnbl]

system tried to read data from a drive bug kept getting a error returned
cyclic redundancy check (CRC) checksum error occurred

since it could not get a clean read of the data from the drive it called a bugcheck to shutdown the system.

for this type of problem, I would make sure the data cables had a good contact with the drive and the SATA controller. I might change the connection to another sata port, I might move the data connection to the primary SATA controller if I have two.

if the drive is a SSD drive, I would boot into BIOS and leave the drive idle for a few hours. This will let the drives firmware to do cleanup of the drive.
I might delete the pagefile.sys and make another one or run without one for a short time. (windows will create a pagefile in your ram in that case)


if it is a older spinning hard drive and you have windows 7, you might end up having to do a FULL format of the drive to get bad/weak sectors marked as bad.
With windows 8, it will attempt to move data from weak sectors and mark the sector as bad automatically when the system is idle. it won't do this if the drive is asleep, so you would change the system settings to high performance and leave the system running idle overnight for the best chance to let the system repair the file.

Also, empty the recycle bin and clean up/remove files you don't need, ie empty your browser cache. Fewer files to repair and more free space on the drive to move things around during the repair process.