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: fffff8011d092fc9, The address that the exception occurred at
Arg3: ffffc48aa09aa768, Exception Record Address
Arg4: ffffc48aa09a9fa0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for lvrs64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2843
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 25773
Key : Analysis.Init.CPU.mSec
Value: 640
Key : Analysis.Init.Elapsed.mSec
Value: 2788
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 112421-6250-01.dmp
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8011d092fc9
BUGCHECK_P3: ffffc48aa09aa768
BUGCHECK_P4: ffffc48aa09a9fa0
EXCEPTION_RECORD: ffffc48aa09aa768 -- (.exr 0xffffc48aa09aa768)
ExceptionAddress: fffff8011d092fc9 (lvrs64+0x0000000000002fc9)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000001f46952cb74
Attempt to read from address 000001f46952cb74
CONTEXT: ffffc48aa09a9fa0 -- (.cxr 0xffffc48aa09a9fa0)
rax=0000000000000000 rbx=ffffd68e34d70ce0 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8011d092fc9 rsp=ffffc48aa09aa9a0 rbp=000001f46952cb50
r8=0000000000000000 r9=000001f46952cb50 r10=0000000000000002
r11=000001f46952cb50 r12=ffffd68e34d77ce0 r13=0000000000000000
r14=000001f46952cb50 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00250246
lvrs64+0x2fc9:
fffff801`1d092fc9 45396924 cmp dword ptr [r9+24h],r13d ds:002b:000001f4`6952cb74=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff8010defb390: 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
000001f46952cb74
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000001f46952cb74
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffc48a`a09aa9a0 00000000`00000000 : ffff8101`b4d00180 ffffd68e`3a30c040 fffff801`0d485d0e 00000000`00000000 : lvrs64+0x2fc9
SYMBOL_NAME: lvrs64+2fc9
MODULE_NAME: lvrs64
IMAGE_NAME: lvrs64.sys
STACK_COMMAND: .cxr 0xffffc48aa09a9fa0 ; kb
BUCKET_ID_FUNC_OFFSET: 2fc9
FAILURE_BUCKET_ID: AV_lvrs64!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {456b553a-a332-622e-ed6e-0ef1efb881db}
Followup: MachineOwner