A recent crash resulted in the following crash dump Is this a intermittent disk problem ?
thanks for your help
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\New folder\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c4f650
Debug session time: Sat May 28 13:01:54.963 2011 (UTC + 1:00)
System Uptime: 0 days 5:28:30.227
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000006, fffff8800125e9e3, fffff8800c17b898, fffff8800c17b0f0}
*** ERROR: Module load completed but symbols could not be loaded for PCTSD64.sys
Probably caused by : hardware_disk
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff8800125e9e3, The address that the exception occurred at
Arg3: fffff8800c17b898, Exception Record Address
Arg4: fffff8800c17b0f0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAULTING_IP:
PCTSD64+79e3
fffff880`0125e9e3 488b5500 mov rdx,qword ptr [rbp]
EXCEPTION_RECORD: fffff8800c17b898 -- (.exr 0xfffff8800c17b898)
ExceptionAddress: fffff8800125e9e3 (PCTSD64+0x00000000000079e3)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000090000
Parameter[2]: 00000000c000000e
Inpage operation failed at 0000000000090000, due to I/O error 00000000c000000e
CONTEXT: fffff8800c17b0f0 -- (.cxr 0xfffff8800c17b0f0)
rax=0000000000000000 rbx=fffffa8006a2992e rcx=fffffa800366eb30
rdx=0000000000000000 rsi=0000000000000000 rdi=000000000013476b
rip=fffff8800125e9e3 rsp=fffff8800c17bad0 rbp=0000000000090000
r8=fffffa8006445db0 r9=fffff8a00d201800 r10=fffffa80036698e0
r11=0000000000000000 r12=fffff78000000320 r13=fffff880012956e4
r14=0000000000000000 r15=fffffa8006a29900
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
PCTSD64+0x79e3:
fffff880`0125e9e3 488b5500 mov rdx,qword ptr [rbp] ss:0018:00000000`00090000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000090000
EXCEPTION_PARAMETER3: 00000000c000000e
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0xc0000006_c000000e
FOLLOWUP_IP:
+79e3
00000000`00090000 ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
Followup: MachineOwner
---------
thanks for your help
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\New folder\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c4f650
Debug session time: Sat May 28 13:01:54.963 2011 (UTC + 1:00)
System Uptime: 0 days 5:28:30.227
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000006, fffff8800125e9e3, fffff8800c17b898, fffff8800c17b0f0}
*** ERROR: Module load completed but symbols could not be loaded for PCTSD64.sys
Probably caused by : hardware_disk
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff8800125e9e3, The address that the exception occurred at
Arg3: fffff8800c17b898, Exception Record Address
Arg4: fffff8800c17b0f0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAULTING_IP:
PCTSD64+79e3
fffff880`0125e9e3 488b5500 mov rdx,qword ptr [rbp]
EXCEPTION_RECORD: fffff8800c17b898 -- (.exr 0xfffff8800c17b898)
ExceptionAddress: fffff8800125e9e3 (PCTSD64+0x00000000000079e3)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000090000
Parameter[2]: 00000000c000000e
Inpage operation failed at 0000000000090000, due to I/O error 00000000c000000e
CONTEXT: fffff8800c17b0f0 -- (.cxr 0xfffff8800c17b0f0)
rax=0000000000000000 rbx=fffffa8006a2992e rcx=fffffa800366eb30
rdx=0000000000000000 rsi=0000000000000000 rdi=000000000013476b
rip=fffff8800125e9e3 rsp=fffff8800c17bad0 rbp=0000000000090000
r8=fffffa8006445db0 r9=fffff8a00d201800 r10=fffffa80036698e0
r11=0000000000000000 r12=fffff78000000320 r13=fffff880012956e4
r14=0000000000000000 r15=fffffa8006a29900
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
PCTSD64+0x79e3:
fffff880`0125e9e3 488b5500 mov rdx,qword ptr [rbp] ss:0018:00000000`00090000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000090000
EXCEPTION_PARAMETER3: 00000000c000000e
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0xc0000006_c000000e
FOLLOWUP_IP:
+79e3
00000000`00090000 ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
Followup: MachineOwner
---------
My Computer
- OS
- windows 7 profesional
