this is what i get with the debugger:
********************************************************************** *********
* *
* Bugcheck Analysis *
* *
********************************************************************** *********
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 85b5902a, 8983dc80, 8983d97c}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
after 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: c0000005, The exception code that was not handled
Arg2: 85b5902a, The address that the exception occurred at
Arg3: 8983dc80, Exception Record Address
Arg4: 8983d97c, 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:
+ffffffff85b5902a
85b5902a 2011 and byte ptr [ecx],dl
EXCEPTION_RECORD: 8983dc80 -- (.exr ffffffff8983dc80)
ExceptionAddress: 85b5902a
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 524f4975
Attempt to write to address 524f4975
CONTEXT: 8983d97c -- (.cxr ffffffff8983d97c)
eax=96d5902b ebx=8580f9a0 ecx=524f4975 edx=00000000 esi=85dad828 edi=818fde00
eip=85b5902a esp=8983dd48 ebp=8983dd7c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
85b5902a 2011 and byte ptr [ecx],dl ds:0023:524f4975=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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.
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
Unable to read MiSystemVaType memory at 81911780
524f4975
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: STRING_DEREFERENCE
LAST_CONTROL_TRANSFER: from 81878e18 to 85b5902a
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8983dd44 81878e18 524f4975 00000000 85dad828 0x85b5902a
8983dd7c 81a254a8 524f4975 89836680 00000000 nt!ExpWorkerThread+0xfd
8983ddc0 8189145e 81878d1b 80000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x7E_ANALYSIS_INCONCLUSIVE
BUCKET_ID: 0x7E_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Facebook
Twitter