Windows 10: Windows BSOD, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M, 0x1000007E

Hi, my dell E7440 laptop got blue screen with below message, please refer to minidump and dmp file link which uploaded to onedrive. Anyone can help for this error? Do I need to run chkdsk? I had done update driver using dell command update before this blue screen happen, because before this there is another blue screen IRQL NOT LESS OR EQUAL.



SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8072977DF90, 0xFFFF9286E8E52BE8, 0xFFFF9286E8E52430)

What failed: Ntfs.sys



minidump: https://1drv.ms/u/s!AplV82MRUO_Baw1c7-7nUSJz9P8?e=YgPiX4

full dump: https://1drv.ms/u/s!AplV82MRUO_BbD-Romtq8qm0SeY?e=jXdK3y



Laptop info:


Dell Latitude E7440

Win 10 Enterprise

:)

 

BSOD Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

I have been having several BSOD recently and have reinstalled windows a few times but have been getting the Error:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

I have a crash report of:

On Mon 8/7/2017 4:31:47 PM your computer crashed

crash dump file: C:\Windows\Minidump\080717-7781-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800A9B5B5D8, 0xFFFFBC8125F8AA28, 0xFFFFBC8125F8A270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 8/7/2017 4:31:47 PM your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800A9B5B5D8, 0xFFFFBC8125F8AA28, 0xFFFFBC8125F8A270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 8/7/2017 1:23:30 PM your computer crashed

crash dump file: C:\Windows\Minidump\080717-7906-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018394B5D8, 0xFFFFA500C6488A28, 0xFFFFA500C6488270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 8/3/2017 3:33:48 PM your computer crashed

crash dump file: C:\Windows\Minidump\080317-9781-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8012635B5D8, 0xFFFFCB0149BF5A28, 0xFFFFCB0149BF5270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Can anyone help me figure this out?

Thank you

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

Windows 10 | BSOD | bugcheck was: 0x1000007e (0xffffffffc0000005, 0xfffff80685a78d2a, 0xffffc7001c02

Atheros, smh they love dumping drivers suddenly.

Troubleshooting Windows STOP Messages

Scroll down further for what you have for

0x1000007e