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: c0000005, The exception code that was not handled
Arg2: 822fb4b1, The address that the exception occurred at
Arg3: 8f5947e8, Exception Record Address
Arg4: 8f5943c0, Context Record Address
Debugging Details:
------------------
FAULTING_MODULE: 82a50000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d372749
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
atikmdag+2d24b1
822fb4b1 8b8ae4010000 mov ecx,dword ptr [edx+1E4h]
EXCEPTION_RECORD: 8f5947e8 -- (.exr 0xffffffff8f5947e8)
ExceptionAddress: 822fb4b1 (atikmdag+0x002d24b1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 000001e4
Attempt to read from address 000001e4
CONTEXT: 8f5943c0 -- (.cxr 0xffffffff8f5943c0)
eax=00000003 ebx=8f594a54 ecx=00000000 edx=00000000 esi=00000000 edi=00000001
eip=822fb4b1 esp=8f5948b0 ebp=8f5948b0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
atikmdag+0x2d24b1:
822fb4b1 8b8ae4010000 mov ecx,dword ptr [edx+1E4h] ds:0023:000001e4=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82326fc7 to 822fb4b1
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8f5948b0 82326fc7 00000002 11058000 0000000f atikmdag+0x2d24b1
8f5948cc 820377d6 003f003f 00000002 11058000 atikmdag+0x2fdfc7
8f5949a0 94cef856 88059a90 ffffffff 82a1e6ee atikmdag+0xe7d6
8f5949f8 94d4c271 87bf9100 8f594a54 8805c000 atikmpag+0x5856
8f594a20 94d2a07e 8f594a54 8f594a3c 827b0171 dxgkrnl!DXGADAPTER::DdiBuildPagingBuffer+0x49
8f594a2c 827b0171 8803e000 8f594a54 8f594b74 dxgkrnl!DXGADAPTER_DdiBuildPagingBuffer+0x10
8f594a3c 827c8436 8f594a54 88061e58 ac7aec90 dxgmms1!DXGADAPTER::DdiBuildPagingBuffer+0x11
8f594b74 827caadd 00000000 ac7aec90 00000000 dxgmms1!VIDMM_GLOBAL::DiscardAllocationInternal+0xa4
8f594b88 827d7bc3 ac7aec90 3419aa16 87f9abe0 dxgmms1!VIDMM_GLOBAL::DiscardAllocation+0x1b
8f594c58 827ca7ff ac7aec90 00000000 885d9858 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x395
8f594cc4 827cae66 8f594ce0 00000000 8f594cf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x741
8f594cf0 827cc4c8 00000000 8f594d18 827e01df dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40
8f594cfc 827e01df 882f3ce0 885d9858 885d9858 dxgmms1!VidMmiProcessTerminationCommand+0x10
8f594d18 827e118f 8850f2c8 885f3a30 8f594d3c dxgmms1!VidSchiSubmitDeviceCommand+0x33
8f594d28 827e13de 885d9858 82a8c3f1 87dea008 dxgmms1!VidSchiSubmitQueueCommand+0xaf
8f594d3c 827e1485 87dea008 00000000 87fc7b48 dxgmms1!VidSchiRun_PriorityTable+0x24
8f594d50 82c5e66d 87dea008 b8b04ce4 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8f594d90 82b10189 827e1406 87dea008 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc0189
FOLLOWUP_IP:
atikmdag+2d24b1
822fb4b1 8b8ae4010000 mov ecx,dword ptr [edx+1E4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+2d24b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
STACK_COMMAND: .cxr 0xffffffff8f5943c0 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------