*******************************************************************************
* *
* 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80547226f9f, The address that the exception occurred at
Arg3: ffffbe87085c7178, Exception Record Address
Arg4: ffffbe87085c6990, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 4765
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 42636
Key : Analysis.IO.Other.Mb
Value: 10
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 11
Key : Analysis.Init.CPU.mSec
Value: 389
Key : Analysis.Init.Elapsed.mSec
Value: 2327
Key : Analysis.Memory.CommitPeak.Mb
Value: 113
Key : Bugcheck.Code.DumpHeader
Value: 0x1000007e
Key : Bugcheck.Code.Register
Value: 0x7e
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z
Key : WER.OS.Version
Value: 10.0.22621.1
FILE_IN_CAB: 041823-58781-01.dmp
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80547226f9f
BUGCHECK_P3: ffffbe87085c7178
BUGCHECK_P4: ffffbe87085c6990
EXCEPTION_RECORD: ffffbe87085c7178 -- (.exr 0xffffbe87085c7178)
ExceptionAddress: fffff80547226f9f (Ntfs!NtfsReleaseFcbEx+0x000000000000007f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000004000008
Attempt to read from address 0000000004000008
CONTEXT: ffffbe87085c6990 -- (.cxr 0xffffbe87085c6990)
rax=ffffc08b1d6368f0 rbx=ffffc08b1d6368a0 rcx=ffffbe87085c76a0
rdx=0000000004000000 rsi=ffffbe87085c7728 rdi=ffffbe87085c76a0
rip=fffff80547226f9f rsp=ffffbe87085c73b0 rbp=ffffbe87085c7b00
r8=0000000000000000 r9=ffffbe87085c77b0 r10=fffff8054274de20
r11=ffffc08b1d6368a4 r12=0000000000000000 r13=0000000000000000
r14=ffffc08b1d636a01 r15=ffffc08b1d636a00
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
Ntfs!NtfsReleaseFcbEx+0x7f:
fffff805`47226f9f 48394208 cmp qword ptr [rdx+8],rax ds:002b:00000000`04000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff8054311c468: 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
0000000004000008
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: 0000000004000008
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffbe87`085c73b0 fffff805`4731ed49 : ffffc08b`1d636a00 ffffbe87`085c7b00 ffffbe87`085c7728 ffffbe87`085c76a0 : Ntfs!NtfsReleaseFcbEx+0x7f
ffffbe87`085c7400 fffff805`47249dad : ffffbe87`085c76a0 ffffc08b`1d636a00 00000000`00000000 ffffbe87`00000001 : Ntfs!NtfsFlushUserStream+0x101
ffffbe87`085c74a0 fffff805`47248e3f : ffffbe87`085c76a0 ffffe584`564da1b0 ffffc08b`1d6368a0 ffffbe87`085c7628 : Ntfs!NtfsFlushVolumeFlushSingleFcb+0x239
ffffbe87`085c75f0 fffff805`426162c5 : ffffe584`52ad5cb0 ffffe584`5d492040 ffffe584`52ad5cb0 fffff805`00000000 : Ntfs!NtfsFlushVolumeMultiThreadFcbWalkerWorker+0x2ef
ffffbe87`085c7a00 fffff805`4260dc67 : ffffe584`5d492040 00000000`0000007e ffffe584`5d492040 fffff805`42616170 : nt!ExpWorkerThread+0x155
ffffbe87`085c7bf0 fffff805`4282e304 : ffffac01`43931180 ffffe584`5d492040 fffff805`4260dc10 00000000`00000246 : nt!PspSystemThreadStartup+0x57
ffffbe87`085c7c40 00000000`00000000 : ffffbe87`085c8000 ffffbe87`085c2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: Ntfs!NtfsReleaseFcbEx+7f
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
IMAGE_VERSION: 10.0.23440.1000
STACK_COMMAND: .cxr 0xffffbe87085c6990 ; kb
BUCKET_ID_FUNC_OFFSET: 7f
FAILURE_BUCKET_ID: AV_Ntfs!NtfsReleaseFcbEx
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a4b35a2d-db2f-5fd5-7a62-a50af78285c0}
Followup: MachineOwner