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: fffff80007c96c80, The address that the exception occurred at
Arg3: ffff948d528bcf58, Exception Record Address
Arg4: ffff948d528bc790, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1343
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1375
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 7434
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
FILE_IN_CAB: 032322-6140-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80007c96c80
BUGCHECK_P3: ffff948d528bcf58
BUGCHECK_P4: ffff948d528bc790
EXCEPTION_RECORD: ffff948d528bcf58 -- (.exr 0xffff948d528bcf58)
ExceptionAddress: fffff80007c96c80 (nt!IoThreadToProcess)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000220
Attempt to read from address 0000000000000220
CONTEXT: ffff948d528bc790 -- (.cxr 0xffff948d528bc790)
rax=fffff80017afd7e0 rbx=ffff9881131f35e0 rcx=0000000000000000
rdx=ffff948d528bd2b8 rsi=ffff9881131f36c8 rdi=ffff9881131f36c8
rip=fffff80007c96c80 rsp=ffff948d528bd198 rbp=ffff948d528bd1f0
r8=ffff948d528bd290 r9=000000000000003e r10=ffff98810c9bd010
r11=ffff9881086b2080 r12=0000000000000000 r13=ffff948d528bd440
r14=ffff98810c9bd2d0 r15=ffff948d528bd2b8
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!IoThreadToProcess:
fffff800`07c96c80 488b8120020000 mov rax,qword ptr [rcx+220h] ds:002b:00000000`00000220=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff800086fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000220
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: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000220
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff948d`528bd198 fffff800`17afd815 : ffff9881`117b16a0 ffff9881`08571520 00000000`00000000 ffff9881`117b16a0 : nt!IoThreadToProcess
ffff948d`528bd1a0 ffff9881`117b16a0 : ffff9881`08571520 00000000`00000000 ffff9881`117b16a0 00000000`00000000 : avgntflt+0x2d815
ffff948d`528bd1a8 ffff9881`08571520 : 00000000`00000000 ffff9881`117b16a0 00000000`00000000 fffff800`07c07805 : 0xffff9881`117b16a0
ffff948d`528bd1b0 00000000`00000000 : ffff9881`117b16a0 00000000`00000000 fffff800`07c07805 ffff9881`086b2080 : 0xffff9881`08571520
SYMBOL_NAME: avgntflt+2d815
MODULE_NAME: avgntflt
IMAGE_NAME: avgntflt.sys
STACK_COMMAND: .cxr 0xffff948d528bc790 ; kb
BUCKET_ID_FUNC_OFFSET: 2d815
FAILURE_BUCKET_ID: AV_avgntflt!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0f00ec50-a062-7277-c951-7987b1cbd0df}
Followup: MachineOwner
---------