Windows 10: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

My computer just crashed with a BSOD with an "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M" error message.


Would someone please help me decipher this bugcheck analysis so that I can fix this problem? This is a fresh install of Windows 10 less than one week old and I am hoping this only a driver related issue. Any help would be very much appreciated!


Debugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 5281 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on LAPTOP-RBKTKL6U Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 6195 Key : Analysis.Memory.CommitPeak.Mb Value: 87 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff80410aadb02BUGCHECK_P3: fffffb0f46b4eff8BUGCHECK_P4: fffffb0f46b4e840EXCEPTION_RECORD: fffffb0f46b4eff8 -- .exr 0xfffffb0f46b4eff8ExceptionAddress: fffff80410aadb02 nt!ExFreeHeapPool+0x00000000000000b2 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000001008000010Attempt to read from address 0000001008000010CONTEXT: fffffb0f46b4e840 -- .cxr 0xfffffb0f46b4e840rax=0000001008000000 rbx=fffffb0f46b4f478 rcx=0000000000000000rdx=fffff80410a00000 rsi=0000001008000001 rdi=a2e64eada2e64eadrip=fffff80410aadb02 rsp=fffffb0f46b4f230 rbp=0000000000000706 r8=ffffa6061842412e r9=000000000000003e r10=fffff80410d6f0a0r11=fffffb0f46b4f350 r12=ffff800000000000 r13=0000000000000000r14=ffffa6062d9e05a0 r15=0000000000000705iopl=0 nv up ei pl nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206nt!ExFreeHeapPool+0xb2:fffff804`10aadb02 488b5810 mov rbx,qword ptr [rax+10h] ds:002b:00000010`08000010=????????????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff80410f733b8: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80410e2a3c8: Unable to get Flags value from nt!KdVersionBlockfffff80410e2a3c8: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 0000001008000010 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: 0000001008000010EXCEPTION_STR: 0xc0000005STACK_TEXT: fffffb0f`46b4f230 fffff804`10d6f0a9 : ffffa606`2d9e0700 ffffa606`2d9e05a0 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0xb2fffffb0f`46b4f350 fffff804`16a8f2b7 : ffffa606`184425f0 fffffb0f`46b4f478 fffffb0f`46b4f7f0 00000000`00000000 : nt!ExFreePool+0x9fffffb0f`46b4f380 fffff804`16a8f632 : ffffa606`2d9e0700 fffff804`10aadda7 ffffa606`05a00340 ffffa606`000000ff : Ntfs!NtfsDeleteScb+0x737fffffb0f`46b4f410 fffff804`169b4225 : ffffa606`2d9e05e0 ffffa606`2d9e0700 ffffa606`2d9e05a0 ffffa606`2d9e0700 : Ntfs!NtfsRemoveScb+0xbafffffb0f`46b4f470 fffff804`16a8f370 : fffffb0f`46b4f7f0 fffff804`16ae5310 ffffa606`2d9e05a0 ffffa606`2d9e0900 : Ntfs!NtfsPrepareFcbForRemoval+0x75fffffb0f`46b4f4b0 fffff804`169b892a : fffffb0f`46b4f7f0 fffffb0f`46b4f5b1 ffffa606`2d9e09e8 fffffb0f`46b4f7f0 : Ntfs!NtfsTeardownStructures+0xa0fffffb0f`46b4f530 fffff804`16ab0bac : fffffb0f`46b4f601 ffffa606`00000000 fffffb0f`00000000 fffffb0f`46b4f7f0 : Ntfs!NtfsDecrementCloseCounts+0xaafffffb0f`46b4f570 fffff804`16aafaf1 : fffffb0f`46b4f7f0 ffffa606`2d9e0700 ffffa606`2d9e05a0 ffffcd82`86db2180 : Ntfs!NtfsCommonClose+0x45cfffffb0f`46b4f650 fffff804`16ae5398 : 00000000`0000001c fffff804`10f8f240 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x241fffffb0f`46b4f7b0 fffff804`10a83945 : ffffcd82`830b4c20 fffff804`00000000 ffffcd82`00000000 00000000`00000000 : Ntfs!NtfsFspClose+0x88fffffb0f`46b4fa70 fffff804`10b1e135 : ffffcd82`9bed3040 00000000`00000080 ffffcd82`830aa340 fffff804`10bcae70 : nt!ExpWorkerThread+0x105fffffb0f`46b4fb10 fffff804`10bc99a8 : ffffbd00`e2d81180 ffffcd82`9bed3040 fffff804`10b1e0e0 ffffa606`069b8170 : nt!PspSystemThreadStartup+0x55fffffb0f`46b4fb60 00000000`00000000 : fffffb0f`46b50000 fffffb0f`46b49000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nt!ExFreePool+9IMAGE_NAME: Pool_CorruptionIMAGE_VERSION: 10.0.18362.900MODULE_NAME: Pool_CorruptionSTACK_COMMAND: .cxr 0xfffffb0f46b4e840 ; kbBUCKET_ID_FUNC_OFFSET: 9FAILURE_BUCKET_ID: AV_nt!ExFreePoolOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {2ae0a97e-dcd7-47ef-dbfb-430f2cbf58a1}Followup: Pool_corruption---------

:)

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Hello, i have a problem with windows 10, and is that when i run sfc/scannow command, after 40% i get SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M, when i check what generate the problem it says something like this:

Crash dump directories:

C:\WINDOWS

C:\WINDOWS\Minidump

On Tue 25/09/2018 8:31:09 p. m. your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\092518-9578-01.dmp

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

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80005A7C1F6, 0xFFFFFD8247975418, 0xFFFFFD8247974C60)

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.

And after this i checked and updated the drivers and got this error:

On Tue 25/09/2018 8:31:09 p. m. your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP

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

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80005A7C1F6, 0xFFFFFD8247975418, 0xFFFFFD8247974C60)

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.

i would be glad if someone knows what´s happening.Thanks

 

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

 

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.