New
#41
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\DJJay\032812-25350-01\032812-25350-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0x82a13000 PsLoadedModuleList = 0x82b5c4d0 Debug session time: Wed Mar 28 10:57:00.970 2012 (UTC - 6:00) System Uptime: 0 days 4:32:34.640 Loading Kernel Symbols ............................................................... ................................................................ ............................................. Loading User Symbols Loading unloaded module list ........... 0: kd> !analyze -v ******************************************************************************* * * * 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: 00000020, lock type that was held (value 1,2,3, or PTE address) Arg2: c000009d, error status (normally i/o status code) Arg3: 8671c9d4, current process (virtual address for lock type 3, or PTE) Arg4: 00000000, 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 82a47abb to 82a87b5c STACK_TEXT: 8b143c04 82a47abb 8671c998 8671c9a0 00000000 nt!MiWriteComplete+0x22d 8b143c24 82ac4746 858d6e68 8b143c50 8b143c5c nt!IopCompletePageWrite+0x4d 8b143c74 82a91685 00000000 00000000 00000000 nt!KiDeliverApc+0x111 8b143cb8 82a904c7 84cd50e0 84cd5020 82b5ba30 nt!KiSwapThread+0x24e 8b143ce0 82abc27b 84cd5020 84cd50e0 00000000 nt!KiCommitThreadWait+0x1df 8b143d24 82a45f03 00000000 00000000 84cd5020 nt!KeWaitForGate+0x158 8b143d50 82c1c022 00000000 ae3abc2a 00000000 nt!MiModifiedPageWriter+0x39 8b143d90 82ac4219 82a45eca 00000000 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiWriteComplete+22d 82a87b5c cc int 3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiWriteComplete+22d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79850 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x7a_c000009d_nt!MiWriteComplete+22d BUCKET_ID: 0x7a_c000009d_nt!MiWriteComplete+22d Followup: MachineOwner ---------from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
Please fill out your system specs by following System Info - See Your System Specs