Code:
*******************************************************************************
* *
* 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa80058d67c8, 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 fffff8000308737c to fffff80003092640
STACK_TEXT:
fffff880`03308818 fffff800`0308737c : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`058d67c8 : nt!KeBugCheckEx
fffff880`03308820 fffff800`0307c297 : fffffa80`058d6760 00000000`c000009d 00000000`00000000 fffffa80`058d67f8 : nt! ?? ::FNODOBFM::`string'+0x51140
fffff880`033088e0 fffff800`03085cf7 : fffffa80`039f2040 fffffa80`039f2090 00000000`10000004 fffff880`01614fe7 : nt!IopCompletePageWrite+0x57
fffff880`03308910 fffff800`03097b9d : fffffa80`039f2040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`03308990 fffff800`03096eaa : fffff880`03308b00 00000000`00000000 fffffa80`00000000 fffffa80`07064470 : nt!KiCommitThreadWait+0x3dd
fffff880`03308a20 fffff800`030222ff : fffffa80`00000002 fffff880`03308d20 fffffa80`00000001 00000000`00000013 : nt!KeWaitForMultipleObjects+0x272
fffff880`03308ce0 fffff800`0332fcce : fffffa80`039f2040 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d40 fffff800`03083fe6 : fffff880`02f63180 fffffa80`039f2040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+51140
fffff800`0308737c cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+51140
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+51140
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+51140
Followup: MachineOwner
---------
It appears you may have a hard drive issue. Have you checked your disk for errors? If not, open up a command prompt (hit the Win key and type cmd) and type the following:
chkdsk /r
That will scan your drive for errors and attempt to fix them.