System_thread_exception_not_handled 0x1000007e

This tutorial includes instructions to resolve the BSOD error 0x1000007e: "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED", led to by the "smbdirect.sys" driver, on a HP ProLiant ML350 Gen10 Server running Windows Server 2016 or Server 2012 R2.

The complying with trouble occurs on an HP Proliant ML350 server running Windows Server 2016: The server randomly and without an noticeable factor crashes via a blue display that reports the complying with error:

"A problem has been detected and also Windows has been shut down to proccasion damageto your computer system.The trouble seems to be brought about by the complying with file: smbdirect.sysSYSTEM_THREAD_EXCEPTION_NOT_HANDLEDTechnical Information:*** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff803804fa7a0, 0xffffa780867fb1e8,0xffffa780867faa30)|*** smbdirect.sys – Address 0xfffff803804fa7a0 base at 0xfffff803804e0000 DateStamp0x57dacc39"


How to FIX the BSOD Error 0x1000007e: SYSTEM THREADVERTISEMENT EXCEPTION NOT HANDLED, on HP Proliant Server Gen 10 with Windows Server 2012 or 2016.

You watching: System_thread_exception_not_handled 0x1000007e

Method 1. Update Network Adapters Drivers.

After looking a lot around this problem, I found that according to Hewlett Packard Enterpclimb Support Center the BSOD error 0x1000007e (0x7E), resulted in in the time of the file copy on ProLiant Gen10 Servers Running Microsoft Windows Server 2012 R2 or Microsoft Windows Server 2016.

More especially the blue display error (0x7E) "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" can show up on any kind of HPE ProLiant Gen10 Server which configured via any type of of the following network-related adapters via HPE Intel i40eb Driver for Windows Server 2016/Windows Server 2012 R2 Version

HPE Ethernet 10Gb 2-port 568i AdapterHPE Ethernet 1Gb 2-port 368i AdapterHPE Ethernet 1Gb 4-port 369i AdapterHPE Ethernet 1Gb 2-port 368FLR-MMT AdapterHPE Ethernet 10Gb 2-port568FLR-MMT AdapterHPE Ethernet 10Gb 2-port 568FLR-MMSFP+ Adapter

So, if you "re running on this instance, continue and also install the latest driver for the netjob-related adapter according the set up Windows Server version: *

* Notes:1. HP additionally recommends to install additionally the latest variation of HPE Intel Online Firmware Upgrade Utility for Windows Server x64 Editions version If after installing the network driver, the BSOD problem persists, then inspect the original post on HPE Support Center for updates or proceed analysis listed below and apply the following solution.

Method 2. Disable the SMB Direct Driver (smsstraight.sys) .

See more: How To Fix Windows Update Error 643 Windows Update Windows 7

After investigating the BSOD error 0x1000007e (0x7E) through the BlueScreenView utility, I found that the crash is brought about by the SMB Network-related Direct Driver (smsstraight.sys).


The SMB Direct, is a feature that included in Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 versions, which supports the use of netjob-related adapters that have actually Remote Direct Memory Access (RDMA) capability. Network adapters that have actually RDMA can attribute at full rate via exceptionally low latency, while utilizing exceptionally bit CPU. For workloads such as Hyper-V or Microsoft SQL Server, this allows a remote file server to resemble regional storage.

So, the following strategy, to fix the BSOD error 0x1000007e, is to disable the SMB Direct attribute. To execute that:

1. Open PowerCovering and also provide the complying with command:


2. After disabling the SMB Direct, the 0x1000007e bsod problem have to be readdressed.

See more: Paypal: "Sorry, Something Went Wrong On Our End Paypal Error

* Note: If you want to re-allow the SMB Direct in the future, provide the complying with command also in powershell:

Set-NetOffloadGlobalSetting -NetworkDirect Enabled

That"s it! Let me recognize if this overview has actually assisted you by leaving your comment around your suffer. Please choose and also share this overview to help others.