Windows 10: Constant BSOD, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 7e

Hello I just build my pc but it keeps restarting with the BSOD, but I am able to use my pc normally again each time, just that it keeps restarting.


I will also include the minidump Bugcheck Analysis here:




SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 7e

This 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.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff800581fd147, The address that the exception occurred atArg3: ffffbf0d1200d168, Exception Record AddressArg4: fffff8005d281920, Context Record AddressDebugging Details:------------------KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 4343 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on HENLO-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 5306 Key : Analysis.Memory.CommitPeak.Mb Value: 122 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: fffff800581fd147BUGCHECK_P3: ffffbf0d1200d168BUGCHECK_P4: fffff8005d281920EXCEPTION_RECORD: ffffbf0d1200d168 -- .exr 0xffffbf0d1200d168ExceptionAddress: fffff800581fd147 nt!ExpInterlockedPopEntrySListFault ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT: fffff8005d281920 -- .cxr 0xfffff8005d281920rax=0000004067f80000 rbx=0000000000000000 rcx=ffffad87af5156c0rdx=0001001000000038 rsi=ffffad87b2350cf0 rdi=ffffad87af5156c0rip=fffff800581fd147 rsp=ffffbf0d1200d3a0 rbp=ffffbf0d1200d400 r8=0001001000000030 r9=0000000000000000 r10=ffffad87af5156c0r11=ffffbf0d1200d320 r12=0000000000000000 r13=ffffad87af349420r14=ffffad87a91bccd0 r15=0000000000000000iopl=0 nv up ei pl nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206nt!ExpInterlockedPopEntrySListFault:fffff800`581fd147 498b08 mov rcx,qword ptr [r8] ds:002b:00010010`00000030=????????????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemREAD_ADDRESS: 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: fffff8005d2810e8STACK_TEXT: ffffbf0d`1200d3a0 fffff800`698f472f : fffff800`5c951a50 00000000`00000000 ffffad87`a91bccd0 ffffe680`86612ace : nt!ExpInterlockedPopEntrySListFaultffffbf0d`1200d3b0 fffff800`5c7e8cee : 00000000`00000000 ffffbf0d`1200d4c9 00000000`00000001 ffffbf0d`1200d5c8 : Ndu!NduInboundMacClassify+0x1ffffffbf0d`1200d460 fffff800`5cc514d5 : 00000000`00003c2c ffffad87`b0975900 ffffad87`aa7f5cf0 00000000`00000050 : NETIO!KfdClassify2+0x19effffbf0d`1200d530 fffff800`5cc51270 : ffffad87`b10cbbf0 fffff800`5c952bab 00000000`00000000 00000000`00000001 : wfplwfs!L2InspectNetBufferListsFast+0x165ffffbf0d`1200d640 fffff800`5c667ef0 : fffff800`0000000a ffffad87`aa7f5cf0 00000000`00000000 00000000`00000001 : wfplwfs!LwfLowerRecvNetBufferLists+0xd0ffffbf0d`1200d700 fffff800`5c69de4c : ffffad87`b1750040 ffffbf0d`1200d7d1 ffffbf0d`1200d798 ffffbf0d`1200d700 : ndis!ndisCallReceiveHandler+0x60ffffbf0d`1200d750 fffff800`5c664a94 : 00000000`0039c7b3 00000000`00000001 ffffad87`a96cb1a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x148ffffbf0d`1200d820 fffff800`69f861d8 : ffffad87`ae257000 ffffad87`ae257000 00000000`00000000 ffffad87`ae2575f0 : ndis!NdisMIndicateReceiveNetBufferLists+0x104ffffbf0d`1200d8b0 fffff800`69f725a8 : 00000000`00000000 00000000`00000001 00000000`0000000a ffffbf0d`1200da28 : rt640x64!MpHandleRecvIntPriVLanJumbo+0x2c4ffffbf0d`1200d9a0 fffff800`5c6c6ce8 : 5342a27a`00000000 ffffad87`b18ea4e0 2e8e971f`64897800 ffffad87`0000000a : rt640x64!MPHandleMessageInterrupt+0x398ffffbf0d`1200da10 fffff800`5c6c71dc : ffffad87`b18eabc8 00000000`0000000a 00000000`00000001 00000000`00000000 : ndis!ndisMiniportDpc+0xf0ffffbf0d`1200daa0 fffff800`5c6b7b0d : ffffad87`a3347c50 ffffad87`a3347c50 ffffbf0d`1200dba9 fffff800`5c696e00 : ndis!ndisQueuedMiniportDpcWorkItem+0x11cffffbf0d`1200db40 fffff800`580a29a5 : ffffad87`a335e040 ffffad87`a335e040 fffff800`5c696ed0 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x20c3dffffbf0d`1200dc10 fffff800`581fc868 : ffffe680`850a0180 ffffad87`a335e040 fffff800`580a2950 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffffbf0d`1200dc60 00000000`00000000 : ffffbf0d`1200e000 ffffbf0d`12008000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: Ndu!NduInboundMacClassify+1ffMODULE_NAME: NduIMAGE_NAME: Ndu.sysSTACK_COMMAND: .cxr 0xfffff8005d281920 ; kbBUCKET_ID_FUNC_OFFSET: 1ffFAILURE_BUCKET_ID: AV_STACKPTR_ERROR_Ndu!NduInboundMacClassifyOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {c49e05bd-de4e-95eb-1694-5b788d92a4c5}Followup: MachineOwner---------

:)

 

BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Hello Ethan,

We realize the inconvenience you are experiencing with BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on your system. We will certainly help you.

Blue screens (BSOD) is mostly occur due to hardware and sometimes due to incompatible software. In a lot of cases it is a corrupted driver or a driver conflict. The most common causes of blue screens are overheating, faulty RAM, video card problem
and BIOS.

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This bug check indicates that a system thread generated an exception that the error handler did not catch.

We suggest you to kindly follow the steps from the below article and check if it helps:

Troubleshoot blue screen errors

Let us know the status of the issue and the result of troubleshooting. We will be happy to assist you further.

Thank you.

 

Windows 10 BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

When I start my laptop. It's always restart and show BSOD : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

(Cl.dll). Please give me your suggestion.

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.