Windows 10: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e

******************************************************************************* ** Bugcheck Analysis ** ********************************************************************************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: fffff806245fc4d7, The address that the exception occurred atArg3: fffffd040856ed68, Exception Record AddressArg4: ffff800109059920, Context Record AddressDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 3687 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RED-DP Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 37530 Key : Analysis.Memory.CommitPeak.Mb Value: 94 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff806245fc4d7BUGCHECK_P3: fffffd040856ed68BUGCHECK_P4: ffff800109059920EXCEPTION_RECORD: fffffd040856ed68 -- .exr 0xfffffd040856ed68ExceptionAddress: fffff806245fc4d7 nt!ExpInterlockedPopEntrySListFault ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT: ffff800109059920 -- .cxr 0xffff800109059920rax=00000008c7b60008 rbx=ffffcd8d0eb9fa80 rcx=ffffcd8d0eb9fa80rdx=0006008001000000 rsi=fffffd040856f070 rdi=0000000000000000rip=fffff806245fc4d7 rsp=fffffd040856efa0 rbp=00000000c0000225 r8=0006008001000000 r9=ffffcd8d0eb9ecc0 r10=ffffcd8d0eb9fa80r11=fffffd040856f0e8 r12=0000000000000002 r13=ffffcd8d0e24af60r14=ffffcd8d141969e0 r15=ffffcd8d0eccdef0iopl=0 nv up ei pl nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206nt!ExpInterlockedPopEntrySListFault:fffff806`245fc4d7 498b08 mov rcx,qword ptr [r8] ds:002b:00060080`01000000=????????????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff80624efb390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80624e0f340: Unable to get Flags value from nt!KdVersionBlockfffff80624e0f340: 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: 0xc0000005BAD_STACK_POINTER: ffff8001090590e8STACK_TEXT: fffffd04`0856efa0 fffff806`41466d7c : ffffcd8d`0e24af60 00000000`00000002 ffffcd8d`163724d0 fffff806`276514ac : nt!ExpInterlockedPopEntrySListFaultfffffd04`0856efb0 fffff806`41464b50 : 00000000`00000030 00000000`00000000 00000000`00000000 00000000`00000000 : Ndu!PplGenericAllocateFunction+0x1cfffffd04`0856eff0 fffff806`414633c9 : 00000000`00000000 00060080`01000000 ffffcd8d`141969e0 ffffcd8d`08bcc1a0 : Ndu!NduCreateNblContext+0x78fffffd04`0856f030 fffff806`41463251 : 00000000`00000000 00060080`01000000 ffffcd8d`08645300 ffffcd8d`00000190 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0x149fffffd04`0856f0b0 fffff806`27298c5f : fffffd04`0856f298 00000000`00000002 fffff806`00000004 ffffcd8d`08263bf0 : Ndu!NduOutboundMacClassify+0x151fffffd04`0856f130 fffff806`276d14d5 : ffffcd8d`00000000 00000000`00000000 ffffcd8d`141969e0 00000000`00000051 : NETIO!KfdClassify2+0x19ffffffd04`0856f200 fffff806`276d10ce : 00000000`00000000 00000000`00000fff 00000000`00000000 00000000`00000000 : wfplwfs!L2InspectNetBufferListsFast+0x165fffffd04`0856f310 fffff806`271158e9 : 00000000`00000001 ffffcd8d`141969e0 00000000`000005b4 fffff806`24449799 : wfplwfs!LwfLowerSendNetBufferLists+0xbefffffd04`0856f3c0 fffff806`27152339 : 00000000`00000000 fffffd04`0856f489 ffffcd8d`0ab84460 fffffa7d`3e9f4cd8 : ndis!ndisCallSendHandler+0x59fffffd04`0856f410 fffff806`27115afb : ffffcd8d`14196900 00000000`0000000b 00000000`3fffffff 00000000`000005ea : ndis!ndisFilterSendNetBufferLists+0x3cee9fffffd04`0856f4f0 fffff806`3b42bf11 : ffffcd8d`10377000 ffffcd8d`10377030 ffffcd8d`00000000 ffffcd8d`00000008 : ndis!NdisFSendNetBufferLists+0x5bfffffd04`0856f5a0 ffffcd8d`10377000 : ffffcd8d`10377030 ffffcd8d`00000000 ffffcd8d`00000008 ffffcd8d`10377110 : cfosspeed6+0x3bf11fffffd04`0856f5a8 ffffcd8d`10377030 : ffffcd8d`00000000 ffffcd8d`00000008 ffffcd8d`10377110 fffff806`3b4e2def : 0xffffcd8d`10377000fffffd04`0856f5b0 ffffcd8d`00000000 : ffffcd8d`00000008 ffffcd8d`10377110 fffff806`3b4e2def ffffcd8d`10377110 : 0xffffcd8d`10377030fffffd04`0856f5b8 ffffcd8d`00000008 : ffffcd8d`10377110 fffff806`3b4e2def ffffcd8d`10377110 55555555`55555555 : 0xffffcd8d`00000000fffffd04`0856f5c0 ffffcd8d`10377110 : fffff806`3b4e2def ffffcd8d`10377110 55555555`55555555 ffff8001`08900100 : 0xffffcd8d`00000008fffffd04`0856f5c8 fffff806`3b4e2def : ffffcd8d`10377110 55555555`55555555 ffff8001`08900100 ffff93bd`41f86c48 : 0xffffcd8d`10377110fffffd04`0856f5d0 ffffcd8d`10377110 : 55555555`55555555 ffff8001`08900100 ffff93bd`41f86c48 ffffcd8d`0ec65180 : cfosspeed6+0xf2deffffffd04`0856f5d8 55555555`55555555 : ffff8001`08900100 ffff93bd`41f86c48 ffffcd8d`0ec65180 ffffcd8d`108f6e08 : 0xffffcd8d`10377110fffffd04`0856f5e0 ffff8001`08900100 : ffff93bd`41f86c48 ffffcd8d`0ec65180 ffffcd8d`108f6e08 00000000`00000000 : 0x55555555`55555555fffffd04`0856f5e8 ffff93bd`41f86c48 : ffffcd8d`0ec65180 ffffcd8d`108f6e08 00000000`00000000 00000000`3fffffff : 0xffff8001`08900100fffffd04`0856f5f0 ffffcd8d`0ec65180 : ffffcd8d`108f6e08 00000000`00000000 00000000`3fffffff ffffcd8d`10377110 : 0xffff93bd`41f86c48fffffd04`0856f5f8 ffffcd8d`108f6e08 : 00000000`00000000 00000000`3fffffff ffffcd8d`10377110 ffffcd8d`10377030 : 0xffffcd8d`0ec65180fffffd04`0856f600 00000000`00000000 : 00000000`3fffffff ffffcd8d`10377110 ffffcd8d`10377030 ffffcd8d`0e937330 : 0xffffcd8d`108f6e08SYMBOL_NAME: Ndu!PplGenericAllocateFunction+1cMODULE_NAME: NduIMAGE_NAME: Ndu.sysIMAGE_VERSION: 10.0.19041.1030STACK_COMMAND: .cxr 0xffff800109059920 ; kbBUCKET_ID_FUNC_OFFSET: 1cFAILURE_BUCKET_ID: AV_STACKPTR_ERROR_Ndu!PplGenericAllocateFunctionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {5c9d4d25-923f-a327-f4cb-5835435797c1}Followup: MachineOwner---------

:)

 

BSOD :- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

I am Experiencing Blue Screen Error of death with code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e). Reinstalled Windows 10 recently.

Minidump file- https://1drv.ms/u/s!AnD5nzk6qZ69kgHUhWOI0dNCcA3v?e=nj2FhT

System Info- Speccy-https://1drv.ms/b/s!AnD5nzk6qZ69kgMxzpTjbKrn0jeb?e=yqToou

CPU-Z- https://1drv.ms/u/s!AnD5nzk6qZ69kgL1220LOaTO4FkY?e=olhO7M

System info- Notebook PC- ASUS X553MA

OS- Windows 10 2004

Processor- Intel Baytrail N3540

RAM- 4GB

HDD- 500 GB

 

BSOD Ntoskernel, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

Hello
My first post

AMD CPU FX8350
Sabertooth 990FX R2.0
Corsair LP1600Mhz
R9 290x

This error SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

I dont know what it can be, even after reading from windbg, so i need a little help from you.

Here is the Windbg full analyze

https://1drv.ms/u/s!AsAbBkMFzh4ehagF90xXglVFO9Gl3g

Thanks in advance.

 

BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

*******************************************************************************
* *
* 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: fffff803252d1e40, The address that the exception occurred at
Arg3: ffff928abbbff698, Exception Record Address
Arg4: ffff928abbbfeed0, Context Record Address

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 8

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on SLD-LT212

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 25

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff803252d1e40

BUGCHECK_P3: ffff928abbbff698

BUGCHECK_P4: ffff928abbbfeed0

EXCEPTION_RECORD: ffff928abbbff698 -- (.exr 0xffff928abbbff698)
ExceptionAddress: fffff803252d1e40 (nt!IoGetRelatedDeviceObject)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010

CONTEXT: ffff928abbbfeed0 -- (.cxr 0xffff928abbbfeed0)
rax=0000000000000000 rbx=ffff96892e1e4010 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff928abbbff940
rip=fffff803252d1e40 rsp=ffff928abbbff8d8 rbp=ffff928abbbff9c9
r8=ffff928abbbff940 r9=0000000000000000 r10=fffff803252d1e40
r11=0000000000000000 r12=0000000000000000 r13=ffff928abbbffa70
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nt!IoGetRelatedDeviceObject:
fffff803`252d1e40 488b4110 mov rax,qword ptr [rcx+10h] ds:002b:00000000`00000010=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80325cfa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80325c0f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff80325c0f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000010

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: 0000000000000010

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff928a`bbbff8d8 fffff803`265590d0 : ffff9689`42146b00 fffff803`25296134 00000000`00000000 00000000`00000000 : nt!IoGetRelatedDeviceObject
ffff928a`bbbff8e0 fffff803`27cdcf10 : ffff928a`bbbff988 00000000`00000000 00000000`00000001 ffffd600`b26c0180 : FLTMGR!FltGetVolumeFromFileObject+0x20
ffff928a`bbbff910 fffff803`27cdccd2 : ffff9689`586ef760 00000000`00000000 ffffffff`00000000 00000000`00000000 : fileinfo!FIPfGetFileInfoRelatedObjectsFromFileObject+0x40
ffff928a`bbbff960 fffff803`25296ac8 : ffff9689`58a52080 ffff9689`586ef760 ffff9689`586ef9a0 00000000`00000000 : fileinfo!FIPfInterfaceQueryFile+0x62
ffff928a`bbbffa30 fffff803`252c1f15 : 00000000`00000000 ffff9689`4fa91040 fffff803`25296a40 ffff9689`00000000 : nt!PfSnNameQueryWorker+0x88
ffff928a`bbbffa70 fffff803`25266dd5 : ffff9689`4fa91040 00000000`00000080 ffff9689`2b102080 00000000`00000001 : nt!ExpWorkerThread+0x105
ffff928a`bbbffb10 fffff803`253fb4f8 : ffffd600`b23c0180 ffff9689`4fa91040 fffff803`25266d80 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff928a`bbbffb60 00000000`00000000 : ffff928a`bbc00000 ffff928a`bbbf9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: fileinfo!FIPfGetFileInfoRelatedObjectsFromFileObject+40

MODULE_NAME: fileinfo

IMAGE_NAME: fileinfo.sys

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .cxr 0xffff928abbbfeed0 ; kb

BUCKET_ID_FUNC_OFFSET: 40

FAILURE_BUCKET_ID: AV_fileinfo!FIPfGetFileInfoRelatedObjectsFromFileObject

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {cf0575a6-bbbf-2a29-9ea3-086e03ab7b76}

Followup: MachineOwner
---------