okay pretty new to reading .dmp files so bare with me, So i just built a new system and after I transferred my old hard drive data to my new system I keep getting BSOD almost everytime i leave my comp idle, but for the first time it BSOD on me while
i was at my PC please help me out.
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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa800a04e7c8, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff8000307b2ac to fffff800030871c0
STACK_TEXT:
fffff880`037086d8 fffff800`0307b2ac : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`0a04e7c8 : nt!KeBugCheckEx
fffff880`037086e0 fffff800`030701a7 : fffffa80`0a04e760 00000000`c000009d 00000000`00000000 fffffa80`0a04e7f8 : nt! ?? ::FNODOBFM::`string'+0x505d0
fffff880`037087a0 fffff800`03079c17 : fffffa80`06a01510 fffffa80`06a01560 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`037087d0 fffff800`0307ce1d : fffffa80`06a01510 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`03708850 fffff800`030896ea : 00000000`00000000 00000000`00000000 00000103`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
fffff880`037088e0 fffff800`03014a5f : fffffa80`00000002 fffff880`03708be0 fffffa80`00000001 00000000`00000013 : nt!KeWaitForMultipleObjects+0x272
fffff880`03708ba0 fffff800`0331de6a : fffffa80`06a01510 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03708c00 fffff800`03077f06 : fffff880`03365180 fffffa80`06a01510 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03708c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+505d0
fffff800`0307b2ac cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+505d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+505d0
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+505d0
Followup: MachineOwner
---------