BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003. This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG. This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG. This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8026b63a319, The address that the exception occurred atArg3: ffffec8a368c71a8, Exception Record AddressArg4: ffffec8a368c69f0, Context Record AddressDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-DEQQ9CP Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 27 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff8026b63a319BUGCHECK_P3: ffffec8a368c71a8BUGCHECK_P4: ffffec8a368c69f0EXCEPTION_RECORD: ffffec8a368c71a8 -- .exr 0xffffec8a368c71a8ExceptionAddress: fffff8026b63a319 nt!FsRtlAcquireHeaderMutex+0x0000000000000039 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT: ffffec8a368c69f0 -- .cxr 0xffffec8a368c69f0rax=0000000000000001 rbx=ffffc8879b18e360 rcx=ffffc8879b18e040rdx=d05ca2f200109a00 rsi=0000000000000000 rdi=d05ca2f200109a00rip=fffff8026b63a319 rsp=ffffec8a368c73e0 rbp=fffff8026de05450 r8=ffffec8a368c73f8 r9=7fffc887940b74b0 r10=fffff8026b63a2e0r11=ffffec8a368c73e0 r12=0000000000000000 r13=0000000000000000r14=ffffec8a368c7501 r15=ffffd90878143a40iopl=0 nv up ei ng nz na pe nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282nt!FsRtlAcquireHeaderMutex+0x39:fffff802`6b63a319 f00fba3700 lock btr dword ptr [rdi],0 ds:002b:d05ca2f2`00109a00=????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff8026bb733b8: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8026ba2a3c8: Unable to get Flags value from nt!KdVersionBlockfffff8026ba2a3c8: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse ffffffffffffffff ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_CODE_STR: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: ffffffffffffffffEXCEPTION_STR: 0xc0000005STACK_TEXT: ffffec8a`368c73e0 fffff802`6dcd440a : ffffd908`7a266498 ffffd908`78143ad0 ffffd908`7a266050 ffffd908`000000ff : nt!FsRtlAcquireHeaderMutex+0x39ffffec8a`368c7410 fffff802`6ddaf4fe : ffffec8a`368c77f0 ffffc887`940b6180 ffffd908`7a266050 ffffd908`7a266498 : Ntfs!NtfsTeardownFromLcb+0x16affffec8a`368c74b0 fffff802`6dcd892a : ffffec8a`368c77f0 ffffec8a`368c75b1 ffffd908`7a266498 ffffec8a`368c77f0 : Ntfs!NtfsTeardownStructures+0xeeffffec8a`368c7530 fffff802`6ddd0cec : ffffec8a`368c7600 ffffd908`00000000 ffffec8a`00000000 ffffec8a`368c77f0 : Ntfs!NtfsDecrementCloseCounts+0xaaffffec8a`368c7570 fffff802`6ddcfc31 : ffffec8a`368c77f0 ffffd908`7a2661b0 ffffd908`7a266050 ffffc887`940b6180 : Ntfs!NtfsCommonClose+0x45cffffec8a`368c7650 fffff802`6de054d8 : 00000000`0000001c fffff802`6bb8f240 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x241ffffec8a`368c77b0 fffff802`6b6bd095 : ffffc887`8ec47970 ffffc887`9b18e000 fffff802`6b6f7800 ffffc887`8ec47970 : Ntfs!NtfsFspClose+0x88ffffec8a`368c7a70 fffff802`6b72a7a5 : ffffc887`9b18e040 00000000`00000080 ffffc887`8ec6c040 000024ef`b59bbfff : nt!ExpWorkerThread+0x105ffffec8a`368c7b10 fffff802`6b7c8b2a : fffff802`66e87180 ffffc887`9b18e040 fffff802`6b72a750 0006ef80`00000000 : nt!PspSystemThreadStartup+0x55ffffec8a`368c7b60 00000000`00000000 : ffffec8a`368c8000 ffffec8a`368c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2aSYMBOL_NAME: nt!FsRtlAcquireHeaderMutex+39MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.18362.535STACK_COMMAND: .cxr 0xffffec8a368c69f0 ; kbBUCKET_ID_FUNC_OFFSET: 39FAILURE_BUCKET_ID: AV_nt!FsRtlAcquireHeaderMutexOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {68e5700a-5d25-fc1f-47ba-91e2a2183ad1}Followup: MachineOwner---------

Weiterlesen...