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: fffff801caf2cbf0, The address that the exception occurred at
Arg3: ffffd00dbb4dc9f8, Exception Record Address
Arg4: ffffd00dbb4dc230, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2640
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 26782
Key : Analysis.Init.CPU.mSec
Value: 624
Key : Analysis.Init.Elapsed.mSec
Value: 5110
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
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: 121521-7921-01.dmp
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff801caf2cbf0
BUGCHECK_P3: ffffd00dbb4dc9f8
BUGCHECK_P4: ffffd00dbb4dc230
EXCEPTION_RECORD: ffffd00dbb4dc9f8 -- (.exr 0xffffd00dbb4dc9f8)
ExceptionAddress: fffff801caf2cbf0 (smrtkrnl64+0x000000000035cbf0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd00dbb4dc230 -- (.cxr 0xffffd00dbb4dc230)
rax=0000000000000078 rbx=ffffd00dbb4dce38 rcx=0000000000032d2e
rdx=00000000c738c303 rsi=0000000000000000 rdi=16073c2ffeaf605c
rip=fffff801caf2cbf0 rsp=ffffd00dbb4dcc30 rbp=00000001402d9035
r8=00000001402d9035 r9=fffff801caca6658 r10=fffff801caea9035
r11=fffff801caf2cbad r12=5541544157565340 r13=0000000000000000
r14=fffff801cabf88d0 r15=fffff801cabf8818
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
smrtkrnl64+0x35cbf0:
fffff801`caf2cbf0 0fbae03d bt eax,3Dh
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80176cfb390: 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
ffffffffffffffff
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: ffffffffffffffff
MISALIGNED_IP:
smrtkrnl64+35cbf0
fffff801`caf2cbf0 0fbae03d bt eax,3Dh
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffd00d`bb4dcc30 00000000`00040207 : 00000000`00000000 00000000`00000000 fffff5e8`06dda6e0 00000000`00040282 : smrtkrnl64+0x35cbf0
ffffd00d`bb4dcc38 00000000`00000000 : 00000000`00000000 fffff5e8`06dda6e0 00000000`00040282 00000000`00000000 : 0x40207
SYMBOL_NAME: smrtkrnl64+35cbf0
MODULE_NAME: hardware
IMAGE_NAME: hardware
STACK_COMMAND: .cxr 0xffffd00dbb4dc230 ; kb
FAILURE_BUCKET_ID: IP_MISALIGNED_smrtkrnl64.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {bae813ea-fe19-a695-b464-dde7821679ef}
Followup: MachineOwner
