Windows 10: BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

Hello All,

Laptop has occasional BSODs. They seem fairly random, every 1-2 days. I think they are related to the intel drivers. I have tried various versions, both from intel and from dell. None seem to fix the issue. Every other driver is updated, as recommended by dell's standards.

This laptop has an oddity in an intel optane drive, which does smart auto caching(no perceptible difference, I think).

I have a 4k monitor attached via HDMI to my 4k laptop screen. I also have a usbc hub with hdmi (important? driver issues with this?? dont think so).

Win10 version is 20H2 19042.867

Dell's hardware scanner is finding no issues, but I don't know how good these are.

Thanks for your help.

Here is a link to the logs: Box

:)

 

BSOD :- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

I am Experiencing Blue Screen Error of death with code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e). Reinstalled Windows 10 recently.

Minidump file- https://1drv.ms/u/s!AnD5nzk6qZ69kgHUhWOI0dNCcA3v?e=nj2FhT

System Info- Speccy-https://1drv.ms/b/s!AnD5nzk6qZ69kgMxzpTjbKrn0jeb?e=yqToou

CPU-Z- https://1drv.ms/u/s!AnD5nzk6qZ69kgL1220LOaTO4FkY?e=olhO7M

System info- Notebook PC- ASUS X553MA

OS- Windows 10 2004

Processor- Intel Baytrail N3540

RAM- 4GB

HDD- 500 GB

 

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.

 

BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803252d1e40, The address that the exception occurred at
Arg3: ffff928abbbff698, Exception Record Address
Arg4: ffff928abbbfeed0, Context Record Address

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 8

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on SLD-LT212

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 25

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff803252d1e40

BUGCHECK_P3: ffff928abbbff698

BUGCHECK_P4: ffff928abbbfeed0

EXCEPTION_RECORD: ffff928abbbff698 -- (.exr 0xffff928abbbff698)
ExceptionAddress: fffff803252d1e40 (nt!IoGetRelatedDeviceObject)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010

CONTEXT: ffff928abbbfeed0 -- (.cxr 0xffff928abbbfeed0)
rax=0000000000000000 rbx=ffff96892e1e4010 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff928abbbff940
rip=fffff803252d1e40 rsp=ffff928abbbff8d8 rbp=ffff928abbbff9c9
r8=ffff928abbbff940 r9=0000000000000000 r10=fffff803252d1e40
r11=0000000000000000 r12=0000000000000000 r13=ffff928abbbffa70
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nt!IoGetRelatedDeviceObject:
fffff803`252d1e40 488b4110 mov rax,qword ptr [rcx+10h] ds:002b:00000000`00000010=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80325cfa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80325c0f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff80325c0f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000010

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000010

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff928a`bbbff8d8 fffff803`265590d0 : ffff9689`42146b00 fffff803`25296134 00000000`00000000 00000000`00000000 : nt!IoGetRelatedDeviceObject
ffff928a`bbbff8e0 fffff803`27cdcf10 : ffff928a`bbbff988 00000000`00000000 00000000`00000001 ffffd600`b26c0180 : FLTMGR!FltGetVolumeFromFileObject+0x20
ffff928a`bbbff910 fffff803`27cdccd2 : ffff9689`586ef760 00000000`00000000 ffffffff`00000000 00000000`00000000 : fileinfo!FIPfGetFileInfoRelatedObjectsFromFileObject+0x40
ffff928a`bbbff960 fffff803`25296ac8 : ffff9689`58a52080 ffff9689`586ef760 ffff9689`586ef9a0 00000000`00000000 : fileinfo!FIPfInterfaceQueryFile+0x62
ffff928a`bbbffa30 fffff803`252c1f15 : 00000000`00000000 ffff9689`4fa91040 fffff803`25296a40 ffff9689`00000000 : nt!PfSnNameQueryWorker+0x88
ffff928a`bbbffa70 fffff803`25266dd5 : ffff9689`4fa91040 00000000`00000080 ffff9689`2b102080 00000000`00000001 : nt!ExpWorkerThread+0x105
ffff928a`bbbffb10 fffff803`253fb4f8 : ffffd600`b23c0180 ffff9689`4fa91040 fffff803`25266d80 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff928a`bbbffb60 00000000`00000000 : ffff928a`bbc00000 ffff928a`bbbf9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: fileinfo!FIPfGetFileInfoRelatedObjectsFromFileObject+40

MODULE_NAME: fileinfo

IMAGE_NAME: fileinfo.sys

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .cxr 0xffff928abbbfeed0 ; kb

BUCKET_ID_FUNC_OFFSET: 40

FAILURE_BUCKET_ID: AV_fileinfo!FIPfGetFileInfoRelatedObjectsFromFileObject

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {cf0575a6-bbbf-2a29-9ea3-086e03ab7b76}

Followup: MachineOwner
---------