Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 4 for Windows7_BSOD_jcgriff2.zip\Windows7_BSOD_jcgriff2\072210-60627-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 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8283f000 PsLoadedModuleList = 0x8297e570
Debug session time: Thu Jul 22 12:20:56.469 2010 (GMT-4)
System Uptime: 0 days 0:40:57.454
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\ati2mtag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
*** ERROR: Module load completed but symbols could not be loaded for ati2mtag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8d902a85, 80f5f9e4, 0}
Unable to load image \SystemRoot\System32\ati2dvag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
Probably caused by : ati2mtag.sys ( ati2mtag+ba85 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8d902a85, The address that the exception occurred at
Arg3: 80f5f9e4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
TRAP_FRAME: 80f5f9e4 -- (.trap 0xffffffff80f5f9e4)
ErrCode = 00000000
eax=8524b480 ebx=851d20e8 ecx=00000002 edx=00000002 esi=85248000 edi=00000002
eip=8d902a85 esp=80f5fa58 ebp=80f5fa64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
ati2mtag+0xba85:
8d902a85 f6412210 test byte ptr [ecx+22h],10h ds:0023:00000024=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8d97a0c5 to 8d902a85
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80f5fa64 8d97a0c5 85248000 00000000 8d978630 ati2mtag+0xba85
80f5fa84 87f3a4be 851d2390 80f5faa0 00000000 ati2mtag+0x830c5
80f5fad0 8286df44 851d20e8 8458bb70 8458bb70 VIDEOPRT!pVideoPortDispatch+0x3b7
80f5fae8 950d0b4f 00000000 ffb79080 00000001 nt!IofCallDriver+0x63
80f5fb14 95228034 851d2030 00232110 00000000 win32k!GreDeviceIoControlEx+0x93
80f5fb3c 9538fcdb 851d2030 00232110 00000000 win32k!EngDeviceIoControl+0x21
80f5fb6c 9538fe19 ffb79080 00000000 00000000 ati2dvag+0x1fcdb
80f5fb8c 9538fe6b ffb79080 00000000 9517fe74 ati2dvag+0x1fe19
80f5fbd8 951a1ef0 ffb79080 00000000 87f5307e ati2dvag+0x1fe6b
80f5fc08 951a9ced ffb7a008 00000000 952993a8 win32k!DrvDisableDisplay+0x1ae
80f5fc30 951a9b6d 00000000 00000001 9516c295 win32k!DrvDisableMDEVChildren+0x88
80f5fc54 9518b8ce ffb9d0f8 00000001 9518b84c win32k!DrvDisableMDEV+0xfe
80f5fc60 9518b84c 00000000 00000001 9518bb1f win32k!SafeDisableMDEV+0x18
80f5fc6c 9518bb1f 9516c295 0000001e 859a8790 win32k!PowerOffGdi+0x1c
80f5fd00 950ec254 0086f814 00000000 859a8790 win32k!xxxUserPowerStateCalloutWorker+0x89
80f5fd18 9516c2b0 0000001e 0086f814 80f5fd34 win32k!xxxUserPowerCalloutWorker+0x34
80f5fd28 8287479a 0000001e 0086f820 77b464f4 win32k!NtUserCallNoParam+0x1b
80f5fd28 77b464f4 0000001e 0086f820 77b464f4 nt!KiFastCallEntry+0x12a
0086f820 00000000 00000000 00000000 00000000 0x77b464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati2mtag+ba85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3f39a3b3
FAILURE_BUCKET_ID: 0x8E_ati2mtag+ba85
BUCKET_ID: OLD_IMAGE_ati2mtag.sys
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8d902a85, The address that the exception occurred at
Arg3: 80f5f9e4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
TRAP_FRAME: 80f5f9e4 -- (.trap 0xffffffff80f5f9e4)
ErrCode = 00000000
eax=8524b480 ebx=851d20e8 ecx=00000002 edx=00000002 esi=85248000 edi=00000002
eip=8d902a85 esp=80f5fa58 ebp=80f5fa64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
ati2mtag+0xba85:
8d902a85 f6412210 test byte ptr [ecx+22h],10h ds:0023:00000024=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8d97a0c5 to 8d902a85
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80f5fa64 8d97a0c5 85248000 00000000 8d978630 ati2mtag+0xba85
80f5fa84 87f3a4be 851d2390 80f5faa0 00000000 ati2mtag+0x830c5
80f5fad0 8286df44 851d20e8 8458bb70 8458bb70 VIDEOPRT!pVideoPortDispatch+0x3b7
80f5fae8 950d0b4f 00000000 ffb79080 00000001 nt!IofCallDriver+0x63
80f5fb14 95228034 851d2030 00232110 00000000 win32k!GreDeviceIoControlEx+0x93
80f5fb3c 9538fcdb 851d2030 00232110 00000000 win32k!EngDeviceIoControl+0x21
80f5fb6c 9538fe19 ffb79080 00000000 00000000 ati2dvag+0x1fcdb
80f5fb8c 9538fe6b ffb79080 00000000 9517fe74 ati2dvag+0x1fe19
80f5fbd8 951a1ef0 ffb79080 00000000 87f5307e ati2dvag+0x1fe6b
80f5fc08 951a9ced ffb7a008 00000000 952993a8 win32k!DrvDisableDisplay+0x1ae
80f5fc30 951a9b6d 00000000 00000001 9516c295 win32k!DrvDisableMDEVChildren+0x88
80f5fc54 9518b8ce ffb9d0f8 00000001 9518b84c win32k!DrvDisableMDEV+0xfe
80f5fc60 9518b84c 00000000 00000001 9518bb1f win32k!SafeDisableMDEV+0x18
80f5fc6c 9518bb1f 9516c295 0000001e 859a8790 win32k!PowerOffGdi+0x1c
80f5fd00 950ec254 0086f814 00000000 859a8790 win32k!xxxUserPowerStateCalloutWorker+0x89
80f5fd18 9516c2b0 0000001e 0086f814 80f5fd34 win32k!xxxUserPowerCalloutWorker+0x34
80f5fd28 8287479a 0000001e 0086f820 77b464f4 win32k!NtUserCallNoParam+0x1b
80f5fd28 77b464f4 0000001e 0086f820 77b464f4 nt!KiFastCallEntry+0x12a
0086f820 00000000 00000000 00000000 00000000 0x77b464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati2mtag+ba85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3f39a3b3
FAILURE_BUCKET_ID: 0x8E_ati2mtag+ba85
BUCKET_ID: OLD_IMAGE_ati2mtag.sys
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8d902a85, The address that the exception occurred at
Arg3: 80f5f9e4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
TRAP_FRAME: 80f5f9e4 -- (.trap 0xffffffff80f5f9e4)
ErrCode = 00000000
eax=8524b480 ebx=851d20e8 ecx=00000002 edx=00000002 esi=85248000 edi=00000002
eip=8d902a85 esp=80f5fa58 ebp=80f5fa64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
ati2mtag+0xba85:
8d902a85 f6412210 test byte ptr [ecx+22h],10h ds:0023:00000024=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8d97a0c5 to 8d902a85
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80f5fa64 8d97a0c5 85248000 00000000 8d978630 ati2mtag+0xba85
80f5fa84 87f3a4be 851d2390 80f5faa0 00000000 ati2mtag+0x830c5
80f5fad0 8286df44 851d20e8 8458bb70 8458bb70 VIDEOPRT!pVideoPortDispatch+0x3b7
80f5fae8 950d0b4f 00000000 ffb79080 00000001 nt!IofCallDriver+0x63
80f5fb14 95228034 851d2030 00232110 00000000 win32k!GreDeviceIoControlEx+0x93
80f5fb3c 9538fcdb 851d2030 00232110 00000000 win32k!EngDeviceIoControl+0x21
80f5fb6c 9538fe19 ffb79080 00000000 00000000 ati2dvag+0x1fcdb
80f5fb8c 9538fe6b ffb79080 00000000 9517fe74 ati2dvag+0x1fe19
80f5fbd8 951a1ef0 ffb79080 00000000 87f5307e ati2dvag+0x1fe6b
80f5fc08 951a9ced ffb7a008 00000000 952993a8 win32k!DrvDisableDisplay+0x1ae
80f5fc30 951a9b6d 00000000 00000001 9516c295 win32k!DrvDisableMDEVChildren+0x88
80f5fc54 9518b8ce ffb9d0f8 00000001 9518b84c win32k!DrvDisableMDEV+0xfe
80f5fc60 9518b84c 00000000 00000001 9518bb1f win32k!SafeDisableMDEV+0x18
80f5fc6c 9518bb1f 9516c295 0000001e 859a8790 win32k!PowerOffGdi+0x1c
80f5fd00 950ec254 0086f814 00000000 859a8790 win32k!xxxUserPowerStateCalloutWorker+0x89
80f5fd18 9516c2b0 0000001e 0086f814 80f5fd34 win32k!xxxUserPowerCalloutWorker+0x34
80f5fd28 8287479a 0000001e 0086f820 77b464f4 win32k!NtUserCallNoParam+0x1b
80f5fd28 77b464f4 0000001e 0086f820 77b464f4 nt!KiFastCallEntry+0x12a
0086f820 00000000 00000000 00000000 00000000 0x77b464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati2mtag+ba85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3f39a3b3
FAILURE_BUCKET_ID: 0x8E_ati2mtag+ba85
BUCKET_ID: OLD_IMAGE_ati2mtag.sys
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8d902a85, The address that the exception occurred at
Arg3: 80f5f9e4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
TRAP_FRAME: 80f5f9e4 -- (.trap 0xffffffff80f5f9e4)
ErrCode = 00000000
eax=8524b480 ebx=851d20e8 ecx=00000002 edx=00000002 esi=85248000 edi=00000002
eip=8d902a85 esp=80f5fa58 ebp=80f5fa64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
ati2mtag+0xba85:
8d902a85 f6412210 test byte ptr [ecx+22h],10h ds:0023:00000024=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8d97a0c5 to 8d902a85
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80f5fa64 8d97a0c5 85248000 00000000 8d978630 ati2mtag+0xba85
80f5fa84 87f3a4be 851d2390 80f5faa0 00000000 ati2mtag+0x830c5
80f5fad0 8286df44 851d20e8 8458bb70 8458bb70 VIDEOPRT!pVideoPortDispatch+0x3b7
80f5fae8 950d0b4f 00000000 ffb79080 00000001 nt!IofCallDriver+0x63
80f5fb14 95228034 851d2030 00232110 00000000 win32k!GreDeviceIoControlEx+0x93
80f5fb3c 9538fcdb 851d2030 00232110 00000000 win32k!EngDeviceIoControl+0x21
80f5fb6c 9538fe19 ffb79080 00000000 00000000 ati2dvag+0x1fcdb
80f5fb8c 9538fe6b ffb79080 00000000 9517fe74 ati2dvag+0x1fe19
80f5fbd8 951a1ef0 ffb79080 00000000 87f5307e ati2dvag+0x1fe6b
80f5fc08 951a9ced ffb7a008 00000000 952993a8 win32k!DrvDisableDisplay+0x1ae
80f5fc30 951a9b6d 00000000 00000001 9516c295 win32k!DrvDisableMDEVChildren+0x88
80f5fc54 9518b8ce ffb9d0f8 00000001 9518b84c win32k!DrvDisableMDEV+0xfe
80f5fc60 9518b84c 00000000 00000001 9518bb1f win32k!SafeDisableMDEV+0x18
80f5fc6c 9518bb1f 9516c295 0000001e 859a8790 win32k!PowerOffGdi+0x1c
80f5fd00 950ec254 0086f814 00000000 859a8790 win32k!xxxUserPowerStateCalloutWorker+0x89
80f5fd18 9516c2b0 0000001e 0086f814 80f5fd34 win32k!xxxUserPowerCalloutWorker+0x34
80f5fd28 8287479a 0000001e 0086f820 77b464f4 win32k!NtUserCallNoParam+0x1b
80f5fd28 77b464f4 0000001e 0086f820 77b464f4 nt!KiFastCallEntry+0x12a
0086f820 00000000 00000000 00000000 00000000 0x77b464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
ati2mtag+ba85
8d902a85 f6412210 test byte ptr [ecx+22h],10h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati2mtag+ba85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3f39a3b3
FAILURE_BUCKET_ID: 0x8E_ati2mtag+ba85
BUCKET_ID: OLD_IMAGE_ati2mtag.sys
Followup: MachineOwner
---------
kd> lmvm ati2mtag
start end module name
8d8f7000 8d993000 ati2mtag T (no symbols)
Loaded symbol image file: ati2mtag.sys
Image path: \SystemRoot\system32\DRIVERS\ati2mtag.sys
Image name: ati2mtag.sys
Timestamp: Tue Aug 12 22:34:27 2003 (3F39A3B3)
CheckSum: 0009BD56
ImageSize: 0009C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4