*******************************************************************************
* *
* 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: c0000005, The exception code that was not handled
Arg2: 8fd108ee, The address that the exception occurred at
Arg3: 8c6e5bc0, Exception Record Address
Arg4: 8c6e57a0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 3312
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ISTN23064
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 14401
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: win7sp1_rtm
Key : WER.OS.Timestamp
Value: 2010-11-19T18:50:00Z
Key : WER.OS.Version
Value: 7.1.7601.17514
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: ffffffff8fd108ee
BUGCHECK_P3: ffffffff8c6e5bc0
BUGCHECK_P4: ffffffff8c6e57a0
EXCEPTION_RECORD: 8c6e5bc0 -- (.exr 0xffffffff8c6e5bc0)
ExceptionAddress: 8fd108ee (dxgmms1!VidSchiCheckHwProgress+0x00000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 1f87330b
Attempt to write to address 1f87330b
CONTEXT: 8c6e57a0 -- (.cxr 0xffffffff8c6e57a0)
eax=8fc399b5 ebx=860a4008 ecx=00000000 edx=00000001 esi=00000000 edi=00000002
eip=8fd108ee esp=8c6e5c88 ebp=8c6e5d28 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
dxgmms1!VidSchiCheckHwProgress+0x12:
8fd108ee c07425a1fc sal byte ptr [ebp-5Fh],0FCh ss:0010:8c6e5cc9=00
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: 82b6ec00: Unable to get Flags value from nt!KdVersionBlock
82b6ec00: Unable to get Flags value from nt!KdVersionBlock
82b6ec00: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from 82bae128
GetUlongPtrFromAddress: unable to read from 82bae5d0
Unable to get NonPagedPoolStart
Unable to get PagedPoolStart
1f87330b
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 1f87330b
MISALIGNED_IP:
dxgmms1!VidSchiCheckHwProgress+12
8fd108ee c07425a1fc sal byte ptr [ebp-5Fh],0FCh
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
8c6e5d28 8fd123c9 00000000 82a7b50e 860a4008 dxgmms1!VidSchiCheckHwProgress+0x12
8c6e5d3c 8fd12485 860a4008 00000000 8609f310 dxgmms1!VidSchiRun_PriorityTable+0xf
8c6e5d50 82c4df5e 860a4008 af5aceac 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8c6e5d90 82af5219 8fd12406 860a4008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_NAME: dxgmms1!VidSchiCheckHwProgress+12
IMAGE_NAME: hardware
IMAGE_VERSION: 6.1.7601.17514
STACK_COMMAND: .cxr 0xffffffff8c6e57a0 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_dxgmms1.sys
OS_VERSION: 7.1.7601.17514
BUILDLAB_STR: win7sp1_rtm
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
FAILURE_ID_HASH: {423f1b08-05ad-fd05-8220-5e76070ffa4a}
Followup: MachineOwner
drive.google.com
.
