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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f086ad, The address that the exception occurred at
Arg3: fffff880033168c8, Exception Record Address
Arg4: fffff88003316120, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+4d8b5
fffff800`02f086ad 488b00 mov rax,qword ptr [rax]
EXCEPTION_RECORD: fffff880033168c8 -- (.exr 0xfffff880033168c8)
ExceptionAddress: fffff80002f086ad (nt! ?? ::FNODOBFM::`string'+0x000000000004d8b5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003316120 -- (.cxr 0xfffff88003316120)
rax=310102d93100af7e rbx=0000000000000000 rcx=310102d93100af7e
rdx=fffffa8009e5f000 rsi=fffff88002f647f0 rdi=fffffa800a1b63f8
rip=fffff80002f086ad rsp=fffff88003316b00 rbp=0000000000000002
r8=fffff80002ffdca0 r9=fffffa800a1b63f8 r10=fffff880033168d0
r11=fffff80002e9ef20 r12=0000000000000001 r13=fffff88003316ba0
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt! ?? ::FNODOBFM::`string'+0x4d8b5:
fffff800`02f086ad 488b00 mov rax,qword ptr [rax] ds:002b:310102d9`3100af7e=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c00e8
ffffffffffffffff
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4d8b5
fffff800`02f086ad 488b00 mov rax,qword ptr [rax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002e7a206 to fffff80002f086ad
STACK_TEXT:
fffff880`03316b00 fffff800`02e7a206 : 00000000`00000072 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x4d8b5
fffff880`03316b80 fffff800`02e7a6c3 : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`0312ccce : fffffa80`06b86680 00000000`00000080 fffffa80`06a979e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02e80fe6 : fffff880`02f64180 fffffa80`06b86680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316700 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4d8b5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
STACK_COMMAND: .cxr 0xfffff88003316120 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+4d8b5
BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+4d8b5
Followup: MachineOwner
---------
)
