Windows 10: BSOD- System Thread Exception Not Handled 1000007e

I've got a brand new HP Envy that can't share my desktop while running in MS Teams, which I need for work.


I've run all the updates, even took it back to the Microsoft store and they did a factory reboot. A month later, and I am still crashing. I need help looking at minidump files. The most recent minidump info is below:





Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Owner\OneDrive\Documents\Minidump files\032420-8906-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS Personal18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`81400000 PsLoadedModuleList = 0xfffff801`81848150Debug session time: Tue Mar 24 17:05:14.737 2020 UTC - 5:00System Uptime: 0 days 20:56:01.453Loading Kernel Symbols...............................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`815c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff504`b28f1f20=000000000000007e0: kd> !analyze -v******************************************************************************** ** 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: ffffffff80000003, The exception code that was not handledArg2: fffff8018145a1c8, The address that the exception occurred atArg3: fffff504b28f2f38, Exception Record AddressArg4: fffff504b28f2780, Context Record AddressDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 6 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-AVRL4AI Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 34 Key : Analysis.Memory.CommitPeak.Mb Value: 70 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffff80000003BUGCHECK_P2: fffff8018145a1c8BUGCHECK_P3: fffff504b28f2f38BUGCHECK_P4: fffff504b28f2780EXCEPTION_RECORD: fffff504b28f2f38 -- .exr 0xfffff504b28f2f38ExceptionAddress: fffff8018145a1c8 nt!KeCheckStackAndTargetAddress+0x0000000000000048 ExceptionCode: 80000003 Break instruction exception ExceptionFlags: 00000010NumberParameters: 1 Parameter[0]: 0000000000000000CONTEXT: fffff504b28f2780 -- .cxr 0xfffff504b28f2780rax=fffff504b28f3198 rbx=fffff504b28f43b8 rcx=0000000000000000rdx=fffff504b28f43b8 rsi=fffff504b28f39c0 rdi=0000000000000000rip=fffff8018145a1c8 rsp=fffff504b28f3170 rbp=fffff504b28f3780 r8=fffff504b28f39c0 r9=fffff504b28f3800 r10=0000fffff8018159r11=fffff504b28f3208 r12=fffff504b28f4c10 r13=fffff504b28f4178r14=fffff504b28f3800 r15=fffff80181916d84iopl=0 nv up ei pl zr na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040246nt!KeCheckStackAndTargetAddress+0x48:fffff801`8145a1c8 cc int 3Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemERROR_CODE: NTSTATUS 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.EXCEPTION_CODE_STR: 80000003EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_STR: 0x80000003TRAP_FRAME: fffff80181361e70 -- .trap 0xfffff80181361e70NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=cccccccccccccccc rsp=ccccccc310423101 rbp=cccccccccccccccc r8=0000000000000000 r9=0000000000000000 r10=0000000000000000r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=1 vif nv up ei pl zr na po nc418b:cccccccc`cccccccc ?? ???Resetting default scopeBAD_STACK_POINTER: ccccccc310423101UNALIGNED_STACK_POINTER: ccccccc310423101STACK_TEXT: fffff504`b28f3170 fffff801`8159d305 : 00000000`00000000 fffff504`b28f4c10 fffff801`931c3efc fffff504`b28f3790 : nt!KeCheckStackAndTargetAddress+0x48fffff504`b28f31a0 fffff801`815cb1b2 : fffff504`b28f4c10 fffff504`b28f3780 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0x45fffff504`b28f3210 fffff801`814fa2d5 : 00000000`000000ca 00000000`00000000 fffff504`b28f3780 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12fffff504`b28f3240 fffff801`814fe86e : fffff504`b28f4178 fffff504`b28f3ec0 fffff504`b28f4178 ffffcd0e`c1d5d600 : nt!RtlDispatchException+0x4a5fffff504`b28f3990 fffff801`815d431d : fffffe7f`3f9fc000 fffff504`b28f4220 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x16efffff504`b28f4040 fffff801`815d0505 : ffffcd0e`00000000 00000000`00000001 fffff504`b28f4a10 ffffcd0e`b963c000 : nt!KiExceptionDispatch+0x11dfffff504`b28f4220 00000000`00000000 : fffff801`95cb53a8 ffffcd0e`c1c15cc0 fffff801`95ca315f 00000000`00000001 : nt!KiPageFault+0x445SYMBOL_NAME: nt!KeCheckStackAndTargetAddress+48MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.18362.720STACK_COMMAND: .cxr 0xfffff504b28f2780 ; kbBUCKET_ID_FUNC_OFFSET: 48FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!KeCheckStackAndTargetAddressOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {a7fbb798-1fbb-fe00-60e7-70b4789edf37}Followup: MachineOwner---------


Any pointers? What do I do next?

:)

 

System Thread Exception Not Handled?

Hi,

Thank you for posting your query on Microsoft Community.

I understand your inconvenience. We will assist you to resolve this issue.

The System Thread Exception Not Handled error in Windows mostly occur due to incompatible or old graphics card drivers. System Thread Exception Not Handled error is often displayed along with the Blue Screen of Death

I suggest you to boot into Safe Mode environment and update your graphic drivers.

Method 1: Update drivers.

I suggest you to update graphic drivers and check if it helps. Follow the steps given below.

• Press Windows key + X key and click on
  Device manager.
• Search for Display Adapters.
• Right-click on the graphics
  card and click on Update driver software.

You may also download the latest graphic drivers from the manufacturer’s website and install them on your computer.

If the issue still persist, I suggest you to install the drivers in compatibility mode and check.



Method 2:



Follow the steps to install the drivers in compatibility mode.

• Download the drivers from the manufacturer’s website.
• Right-click on the installer and click on "Properties".
• Click on the ‘compatibility’ tab and check the box "Run this program in compatibility mode for” and select previous Operating System from the drop down.
• Click on ‘Apply’ and click ‘OK’ and run the file to install it.

Hope it helps. Do let us know if your issue is resolved. For any further information, feel free to contact us.

Thank you.

 

system thread exception not handled / ntfs.sys

Hey, thanks again for the reply!

Please check my 2nd bullet point, with the 2 notes.

-----------

• W10 1809 media creation tool - boots but results in the same error.

1. Note 1: if I disconnect SSD1, HDD1 (W10 drive systems) the W10 USB can boot!
2. Note 2: while using W10 USB, If I attempt to reconnect either drive I get BSOD (system thread exception not handled - ntfs.sys)

 

BSOD SYSTEM THREAD EXCEPTION NOT HANDLED (ndis.sys)

Hello. Thanks for your answer. I've tried updating the drivers you listed and deleted software related to nipixibaf.sys but while trying to updated window I got the same SYSTEM THREAD
EXCEPTION NOT HANDLED (ndis.sys) error.