Bugcheck:
*******************************************************************************
* *
* 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: 81cfa010, The address that the exception occurred at
Arg3: 88b57b78, Exception Record Address
Arg4: 88b57874, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExAllocatePoolWithTag+4ca
81cfa010 895804 mov dword ptr [eax+4],ebx
EXCEPTION_RECORD: 88b57b78 -- (.exr 0xffffffff88b57b78)
ExceptionAddress: 81cfa010 (nt!ExAllocatePoolWithTag+0x000004ca)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 76413d43
Attempt to write to address 76413d43
CONTEXT: 88b57874 -- (.cxr 0xffffffff88b57874)
eax=76413d3f ebx=84070978 ecx=84074124 edx=00000001 esi=84070034 edi=aecc36f0
eip=81cfa010 esp=88b57c40 ebp=88b57c8c iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!ExAllocatePoolWithTag+0x4ca:
81cfa010 895804 mov dword ptr [eax+4],ebx ds:0023:76413d43=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 76413d43
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d43868
Unable to read MiSystemVaType memory at 81d23420
76413d43
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+4ca
81cfa010 895804 mov dword ptr [eax+4],ebx
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 81dee583 to 81cfa010
STACK_TEXT:
88b57c8c 81dee583 00000001 00000900 20204d43 nt!ExAllocatePoolWithTag+0x4ca
88b57cd4 81dee161 fffffe00 88826900 888268e0 nt!HvpWriteLog+0x2e6
88b57cf8 81defd43 81d0be10 81d41ec8 00000000 nt!HvSyncHive+0x97
88b57d14 81defbb9 81d0e101 88b57d36 88b57d3c nt!CmpDoFlushNextHive+0xdc
88b57d44 81cb1e22 00000000 00000000 840c1828 nt!CmpLazyFlushWorker+0x9a
88b57d7c 81de1c42 00000000 32df37ab 00000000 nt!ExpWorkerThread+0xfd
88b57dc0 81c4aefe 81cb1d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExAllocatePoolWithTag+4ca
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
STACK_COMMAND: .cxr 0xffffffff88b57874 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+4ca
BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+4ca
Followup: MachineOwner
---------
If the memory couldn't be referenced run the memory diagnostic as well as looking at your hard drive for errors with chkdsk. Also, update your video and sound drivers.