Antivirus Software:
Code:
smc.exe c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin64\smc.exe 2328 8 1024 8192 3/11/2012 2:36 PM 12.1.671.4971 2.47 MB (2,591,232 bytes) 6/17/2011 5:32 PM
ccsvchst.exe c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin\ccsvchst.exe 1656 8 1024 16384 3/11/2012 2:36 PM 10.1.2.14 134.01 KB (137,224 bytes) 6/17/2011 5:32 PM
ccsvchst.exe c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin\ccsvchst.exe 1344 8 1024 3072 3/11/2012 2:38 PM 10.1.2.14 134.01 KB (137,224 bytes) 6/17/2011 5:32 PM
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\chapmunger\Windows_NT6_BSOD_jcgriff2\031112-15210-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e9f670
Debug session time: Sun Mar 11 00:13:13.124 2012 (UTC - 6:00)
System Uptime: 0 days 0:04:46.289
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff88001308c08, 2, 8, fffff88001308c08}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+2bf0 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88001308c08, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff88001308c08, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f09100
fffff88001308c08
CURRENT_IRQL: 2
FAULTING_IP:
Ntfs! ?? ::NNGAKEGL::`string'+2bf0
fffff880`01308c08 55 push rbp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: explorer.exe
TRAP_FRAME: fffff8800a580fb0 -- (.trap 0xfffff8800a580fb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001308c08 rbx=0000000000000000 rcx=fffff8800a581180
rdx=fffff8800a582770 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001308c08 rsp=fffff8800a581148 rbp=fffff8800a581280
r8=fffff8800a581900 r9=fffff8800a581280 r10=fffff8800a582970
r11=fffff8800a5811b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
Ntfs! ?? ::NNGAKEGL::`string'+0x2bf0:
fffff880`01308c08 55 push rbp
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cd61e9 to fffff80002cd6c40
FAILED_INSTRUCTION_ADDRESS:
Ntfs! ?? ::NNGAKEGL::`string'+2bf0
fffff880`01308c08 55 push rbp
STACK_TEXT:
fffff880`0a580e68 fffff800`02cd61e9 : 00000000`0000000a fffff880`01308c08 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a580e70 fffff800`02cd4e60 : 00000000`000000e9 00000000`00000000 fffff800`02ce1845 fffff880`01269840 : nt!KiBugCheckDispatch+0x69
fffff880`0a580fb0 fffff880`01308c08 : fffff800`02d02a7c 00000000`00000001 fffffa80`09667000 fffffa80`08c92d01 : nt!KiPageFault+0x260
fffff880`0a581148 fffff800`02d02a7c : 00000000`00000001 fffffa80`09667000 fffffa80`08c92d01 fffffa80`08d1aea0 : Ntfs! ?? ::NNGAKEGL::`string'+0x2bf0
fffff880`0a581150 fffff800`02d024fd : fffff880`01269834 fffff880`0a582770 00000000`00000000 fffff880`01219000 : nt!_C_specific_handler+0x8c
fffff880`0a5811c0 fffff800`02d012d5 : fffff880`01269834 fffff880`0a581238 fffff880`0a5820a8 fffff880`01219000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a5811f0 fffff800`02d12361 : fffff880`0a5820a8 fffff880`0a581900 fffff880`00000000 ffff5fff`ffffffff : nt!RtlDispatchException+0x415
fffff880`0a5818d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x135
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs! ?? ::NNGAKEGL::`string'+2bf0
fffff880`01308c08 55 push rbp
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Ntfs! ?? ::NNGAKEGL::`string'+2bf0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2bf0
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2bf0
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\chapmunger\Windows_NT6_BSOD_jcgriff2\031012-22963-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0285a000 PsLoadedModuleList = 0xfffff800`02a97e70
Debug session time: Sat Mar 10 22:15:14.047 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:55.014
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8009348b30, fffffa8009348e10, fffff80002bd2300}
Probably caused by : hardware_disk
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8009348b30, Terminating object
Arg3: fffffa8009348e10, Process image file name
Arg4: fffff80002bd2300, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa8009348b30
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_RECORD: fffff88001ed8b78 -- (.exr 0xfffff88001ed8b78)
ExceptionAddress: 0000000077514e8f
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000007fefd47d8a8
Parameter[2]: 00000000c000000e
Inpage operation failed at 000007fefd47d8a8, due to I/O error 00000000c000000e
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.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: 000007fefd47d8a8
EXCEPTION_PARAMETER3: 00000000c000000e
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
EXCEPTION_STR: 0xc0000006_c000000e
FAULTING_IP:
+23a
00000000`77514e8f ?? ???
BUGCHECK_STR: 0xF4_IOERR_C000000E
FOLLOWUP_IP:
+23a
000007fe`fd47d8a8 ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Followup: MachineOwner
---------
These are pointing to your hard disks. Is your SSD firmware and are your SSD controllers all up to date for both drives?