Code:
tuneuputilitiesapp64.exe c:\program files (x86)\tuneup utilities 2012\tuneuputilitiesapp64.exe 2628 8 200 1380 3/14/2012 8:51 PM 12.0.3010.5 1.29 MB (1,352,512 bytes) 2/9/2012 5:13 AM
tuneuputilitiesservice64.exe c:\program files (x86)\tuneup utilities 2012\tuneuputilitiesservice64.exe 2100 8 200 1380 3/14/2012 8:51 PM 12.0.3010.5 2.04 MB (2,143,552 bytes) 2/9/2012 5:13 AM
to "tune up" Windows 7?
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031412-37752-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8ce70
Debug session time: Wed Mar 14 21:48:26.108 2012 (UTC - 6:00)
System Uptime: 0 days 0:09:01.183
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000096, fffff80002cc66f3, fffff8800647e648, fffff8800647deb0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+6146a )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff80002cc66f3, The address that the exception occurred at
Arg3: fffff8800647e648, Exception Record Address
Arg4: fffff8800647deb0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
FAULTING_IP:
nt!SwapContext_PatchXSave+70
fffff800`02cc66f3 0f00d1 lldt cx
EXCEPTION_RECORD: fffff8800647e648 -- (.exr 0xfffff8800647e648)
ExceptionAddress: fffff80002cc66f3 (nt!SwapContext_PatchXSave+0x0000000000000070)
ExceptionCode: c0000096
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff8800647deb0 -- (.cxr 0xfffff8800647deb0)
rax=0000000000000001 rbx=fffff880009e8180 rcx=0000000000000070
rdx=0000000000000000 rsi=fffffa8005246b60 rdi=fffffa80038adb60
rip=fffff80002cc66f3 rsp=fffff8800647e880 rbp=fffff88009d1cdb0
r8=0000000000000000 r9=0000000000000001 r10=fffff80002c50000
r11=0000000000000000 r12=0000000000041eb0 r13=0000000000066979
r14=fffffa80033f7700 r15=000000000000013c
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!SwapContext_PatchXSave+0x70:
fffff800`02cc66f3 0f00d1 lldt cx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: STATUS_PRIVILEGED_INSTRUCTION
LAST_CONTROL_TRANSFER: from fffff80002cc635a to fffff80002cc66f3
STACK_TEXT:
fffff880`0647e880 fffff800`02cc635a : 00000000`00000000 ffffffff`fffffffd fffff880`009e8180 fffff800`02cc6722 : nt!SwapContext_PatchXSave+0x70
fffff880`0647e8c0 fffff800`02cc75c2 : fffffa80`05246b60 fffffa80`05246b60 fffffa80`0549a000 fffff880`00000001 : nt!KiSwapContext+0x7a
fffff880`0647ea00 fffff800`02cc9a8f : 00000000`00000005 fffff880`05126c84 fffffa80`00000083 00000001`3d98818f : nt!KiCommitThreadWait+0x1d2
fffff880`0647ea90 fffff880`0508a46a : fffffa80`0549ab00 00000000`00000000 fffffa80`0549a000 fffff880`0512c200 : nt!KeWaitForSingleObject+0x19f
fffff880`0647eb30 fffffa80`0549ab00 : 00000000`00000000 fffffa80`0549a000 fffff880`0512c200 fffff880`009e8180 : atikmdag+0x6146a
fffff880`0647eb38 00000000`00000000 : fffffa80`0549a000 fffff880`0512c200 fffff880`009e8180 00000000`00000200 : 0xfffffa80`0549ab00
FOLLOWUP_IP:
atikmdag+6146a
fffff880`0508a46a ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: atikmdag+6146a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f3b1dc8
STACK_COMMAND: .cxr 0xfffff8800647deb0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+6146a
BUCKET_ID: X64_0x7E_atikmdag+6146a
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031412-14554-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5ae70
Debug session time: Wed Mar 14 18:30:08.894 2012 (UTC - 6:00)
System Uptime: 0 days 3:02:09.032
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {8, 6, 6, fffffa8004cce000}
Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
Probably caused by : usbfilter.sys ( usbfilter+3c22 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit
Arg4: fffffa8004cce000, TimeoutContext - PortData
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff880051427fa to fffff80002c8e540
STACK_TEXT:
fffff880`08ec7718 fffff880`051427fa : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx
fffff880`08ec7720 fffff880`0514d5bd : fffffa80`04cce000 fffffa80`04cce1d8 fffffa80`04cce000 fffffa80`0485d050 : usbhub!UsbhWaitEventWithTimeoutEx+0x3aa
fffff880`08ec77d0 fffff880`0514cbd8 : 00000000`00000000 fffffa80`50447100 fffffa80`04cce000 00000000`00080000 : usbhub!Usbh_PCE_Disable_Action+0x4f1
fffff880`08ec7830 fffff880`05151f7c : fffffa80`0485d050 00000000`00000001 00000000`00000001 fffffa80`0485d708 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0x110
fffff880`08ec7870 fffff880`0514a744 : fffffa80`0485d050 fffffa80`04cce000 fffffa80`04cce000 00000000`00000000 : usbhub!UsbhPCE_Disable+0xb4
fffff880`08ec78c0 fffff880`05149a3c : 00000000`00000007 00000000`00000003 fffffa80`0485d050 fffffa80`0485d708 : usbhub!UsbhBusPause_Action+0x184
fffff880`08ec7910 fffff880`05149eb6 : fffffa80`0485d1a0 00000000`00000007 fffffa80`0485d050 00000000`00000000 : usbhub!Usbh_BS_BusRun+0x94
fffff880`08ec7950 fffff880`0514a92b : 00000000`00000003 fffffa80`0485d708 fffffa80`0485d050 00000000`00000000 : usbhub!UsbhDispatch_BusEvent+0x20e
fffff880`08ec79a0 fffff880`0515f362 : fffffa80`03de69e8 fffffa80`0520bec0 fffffa80`0520bec0 fffffa80`03de69e8 : usbhub!UsbhSyncBusPause+0x4f
fffff880`08ec79e0 fffff880`0515da92 : fffffa80`0485d050 fffffa80`0485d708 fffffa80`0485d708 00000000`00000004 : usbhub!UsbhFdoSetPowerDx_Action+0x9a
fffff880`08ec7a40 fffff880`0515c70b : fffffa80`03de69e8 fffffa80`0485d1a0 fffffa80`0485d050 fffffa80`03de67b0 : usbhub!UsbhFdoDevicePowerState+0x206
fffff880`08ec7a90 fffff880`0515b9c7 : fffffa80`03de67b0 00000000`00000000 fffffa80`0485d050 fffff800`02d90832 : usbhub!UsbhFdoPower_SetPower+0x93
fffff880`08ec7ad0 fffff880`05142fdf : fffffa80`03de67b0 fffffa80`04517040 fffffa80`0465ee20 fffff880`00dc2f3a : usbhub!UsbhFdoPower+0xaf
fffff880`08ec7b10 fffff800`02d908f2 : fffffa80`03de67b0 00000000`00000000 fffffa80`04517040 fffffa80`03de67b0 : usbhub!UsbhGenDispatch+0x7f
fffff880`08ec7b40 fffff880`04ccac22 : fffffa80`04517040 fffff880`04cc85cb fffffa80`03de67b0 fffff800`02d72e03 : nt!IopPoHandleIrp+0x32
fffff880`08ec7b70 fffffa80`04517040 : fffff880`04cc85cb fffffa80`03de67b0 fffff800`02d72e03 fffffa80`04517190 : usbfilter+0x3c22
fffff880`08ec7b78 fffff880`04cc85cb : fffffa80`03de67b0 fffff800`02d72e03 fffffa80`04517190 fffffa80`03de69e8 : 0xfffffa80`04517040
fffff880`08ec7b80 fffffa80`03de67b0 : fffff800`02d72e03 fffffa80`04517190 fffffa80`03de69e8 fffffa80`04517190 : usbfilter+0x15cb
fffff880`08ec7b88 fffff800`02d72e03 : fffffa80`04517190 fffffa80`03de69e8 fffffa80`04517190 00000000`00000000 : 0xfffffa80`03de67b0
fffff880`08ec7b90 fffff800`02d7387e : fffffa80`04517190 fffffa80`03de69e8 fffff880`00000000 fffffa80`05b34560 : nt!PopDiagTraceDeviceAcquireIrp+0xf3
fffff880`08ec7c60 fffff800`02da92c5 : fffffa80`04517040 fffffa80`03de67b0 00000000`00000001 fffffa80`03de6858 : nt!PoDeviceAcquireIrp+0x3e
fffff880`08ec7c90 fffff800`02f2d726 : ffffffff`fa0a1f00 fffffa80`0562ab60 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`08ec7d40 fffff800`02c6cac6 : fffff800`02e07e80 fffffa80`0562ab60 fffffa80`06502b60 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`08ec7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbfilter+3c22
fffff880`04ccac22 ?? ???
SYMBOL_STACK_INDEX: f
SYMBOL_NAME: usbfilter+3c22
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbfilter
IMAGE_NAME: usbfilter.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49d5f587
FAILURE_BUCKET_ID: X64_0xFE_usbfilter+3c22
BUCKET_ID: X64_0xFE_usbfilter+3c22
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031412-17035-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e70
Debug session time: Wed Mar 14 01:16:45.014 2012 (UTC - 6:00)
System Uptime: 0 days 2:54:19.089
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000123f63, fffff880075e60d0, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+73 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000123f63, Address of the instruction which caused the bugcheck
Arg3: fffff880075e60d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!TimersProc+73
fffff960`00123f63 8b5348 mov edx,dword ptr [rbx+48h]
CONTEXT: fffff880075e60d0 -- (.cxr 0xfffff880075e60d0)
rax=0000000009bc00cd rbx=0000000000001808 rcx=0000000009bc00dd
rdx=0000000000000000 rsi=0000000000000080 rdi=0000000000001820
rip=fffff96000123f63 rsp=fffff880075e6aa0 rbp=0000000000000010
r8=fffffa800501b5a8 r9=0000000000000000 r10=fffffffffffffffd
r11=00000000002f6b00 r12=0000000000000000 r13=fffff960003442c0
r14=0000000000000002 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207
win32k!TimersProc+0x73:
fffff960`00123f63 8b5348 mov edx,dword ptr [rbx+48h] ds:002b:00000000`00001850=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff96000124a64 to fffff96000123f63
STACK_TEXT:
fffff880`075e6aa0 fffff960`00124a64 : 00000000`00000000 fffff960`00344a90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x73
fffff880`075e6af0 fffff960`000b502c : fffffa80`0000003b 00000000`0000000f fffff880`00000001 ffffffff`80000100 : win32k!RawInputThread+0x9b4
fffff880`075e6bc0 fffff960`0013539a : fffffa80`00000002 fffff880`075d2f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`075e6bf0 fffff800`02c79813 : fffffa80`05089060 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`075e6c20 000007fe`fd693d5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`013bfad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd693d5a
FOLLOWUP_IP:
win32k!TimersProc+73
fffff960`00123f63 8b5348 mov edx,dword ptr [rbx+48h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!TimersProc+73
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f10fe35
STACK_COMMAND: .cxr 0xfffff880075e60d0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!TimersProc+73
BUCKET_ID: X64_0x3B_win32k!TimersProc+73
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031312-22120-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e59e70
Debug session time: Tue Mar 13 14:02:31.212 2012 (UTC - 6:00)
System Uptime: 0 days 9:02:04.835
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 1, fffff80000b96080}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80000b96080, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec40e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+3332333431616164
fffff800`00b96080 0000 add byte ptr [rax],al
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9cbb0 -- (.trap 0xfffff80000b9cbb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000b96080 rsp=fffff80000b9cd40 rbp=fffff80000b9cd40
r8=fffffa80033dc918 r9=0000000000000000 r10=fffffffffffffffe
r11=fffffa800562b168 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`00b96080 0000 add byte ptr [rax],al ds:1881:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8bb29 to fffff80002c8c5c0
STACK_TEXT:
fffff800`00b9ca68 fffff800`02c8bb29 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9ca70 fffff800`02c8a7a0 : 00000000`00000000 fffff800`02e06e80 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9cbb0 fffff800`00b96080 : fffffa80`033dc890 00000000`00000000 00000000`00000000 fffffa80`03ef96e0 : nt!KiPageFault+0x260
fffff800`00b9cd40 fffffa80`033dc890 : 00000000`00000000 00000000`00000000 fffffa80`03ef96e0 fffff800`02e14c40 : 0xfffff800`00b96080
fffff800`00b9cd48 00000000`00000000 : 00000000`00000000 fffffa80`03ef96e0 fffff800`02e14c40 00000000`00000001 : 0xfffffa80`033dc890
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02c8a7a0 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
FAILURE_BUCKET_ID: X64_0xD1_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_nt!KiPageFault+260
Followup: MachineOwner
---------