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

Hello zebal!

I tried running the dell disk test, it passed.

Disk partition manager says that disk 2 is on my usb-c hub. It however has no disks, so has probably something to do with cheap chineese drivers I would guess.

- - - Updated - - -

Also this is the output from the minidump. This is why I think it is graphics driver related.


Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031621-16015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`48000000 PsLoadedModuleList = 0xfffff800`48c2a490
Debug session time: Tue Mar 16 04:27:44.823 2021 (UTC - 4:00)
System Uptime: 1 days 11:50:11.503
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
Unable to load image igdkmdnd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmdnd64.sys
igdkmdnd64+0x497bf5:
fffff800`64d07bf5 488919 mov qword ptr [rcx],rbx ds:002b:5a0a967e`02961000=????????????????
6: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff80064d07bf5, The address that the exception occurred at
Arg3: ffffed0e1824ecb8, Exception Record Address
Arg4: ffffed0e1824e4f0, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 1656

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6134

Key : Analysis.Init.CPU.mSec
Value: 453

Key : Analysis.Init.Elapsed.mSec
Value: 12558

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80064d07bf5

BUGCHECK_P3: ffffed0e1824ecb8

BUGCHECK_P4: ffffed0e1824e4f0

EXCEPTION_RECORD: ffffed0e1824ecb8 -- (.exr 0xffffed0e1824ecb8)
ExceptionAddress: fffff80064d07bf5 (igdkmdnd64+0x0000000000497bf5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffffed0e1824e4f0 -- (.cxr 0xffffed0e1824e4f0)
rax=000000047da00007 rbx=000000047da00007 rcx=5a0a967e02961000
rdx=ffffed0e1824ef20 rsi=ffffd20f48b95000 rdi=ffffd20f48b95000
rip=fffff80064d07bf5 rsp=ffffed0e1824eef0 rbp=0000000175000000
r8=0000000000000001 r9=0000fffffffff002 r10=0000000000000000
r11=0000000000000027 r12=ffffd20f3439e000 r13=00000000003ff000
r14=0000000175000000 r15=ffffd20f48b95960
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
igdkmdnd64+0x497bf5:
fffff800`64d07bf5 488919 mov qword ptr [rcx],rbx ds:002b:5a0a967e`02961000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80048cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

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: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffffed0e`1824eef0 ffffd20f`48b95000 : 00000004`7da00007 00000001`75000000 fffff800`64d0b3be ffffed0e`1824ef40 : igdkmdnd64+0x497bf5
ffffed0e`1824eef8 00000004`7da00007 : 00000001`75000000 fffff800`64d0b3be ffffed0e`1824ef40 0000012c`670b9d32 : 0xffffd20f`48b95000
ffffed0e`1824ef00 00000001`75000000 : fffff800`64d0b3be ffffed0e`1824ef40 0000012c`670b9d32 5a0a967e`02961000 : 0x00000004`7da00007
ffffed0e`1824ef08 fffff800`64d0b3be : ffffed0e`1824ef40 0000012c`670b9d32 5a0a967e`02961000 00000000`00000000 : 0x00000001`75000000
ffffed0e`1824ef10 ffffed0e`1824ef40 : 0000012c`670b9d32 5a0a967e`02961000 00000000`00000000 ffffd20f`48b95000 : igdkmdnd64+0x49b3be
ffffed0e`1824ef18 0000012c`670b9d32 : 5a0a967e`02961000 00000000`00000000 ffffd20f`48b95000 fffff800`64d07d24 : 0xffffed0e`1824ef40
ffffed0e`1824ef20 5a0a967e`02961000 : 00000000`00000000 ffffd20f`48b95000 fffff800`64d07d24 00000004`00000001 : 0x0000012c`670b9d32
ffffed0e`1824ef28 00000000`00000000 : ffffd20f`48b95000 fffff800`64d07d24 00000004`00000001 00000000`00000000 : 0x5a0a967e`02961000


SYMBOL_NAME: igdkmdnd64+497bf5

MODULE_NAME: igdkmdnd64

IMAGE_NAME: igdkmdnd64.sys

STACK_COMMAND: .cxr 0xffffed0e1824e4f0 ; kb

BUCKET_ID_FUNC_OFFSET: 497bf5

FAILURE_BUCKET_ID: AV_igdkmdnd64!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f72986a3-e8f9-3600-9d7c-dd8a40f557df}

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

Hmm, I tried disabling the phantom disk from the usbc hub in device manager. No BSODs for a few days now(longest ever?).

That might have been the thing causing crashes.

Thanks for bringing that strange thing to my attention, I would've never thought to check for something like that.

Hello again,
Bad news unfortunately.
Had another BSOD.
Driver verifier was active for the BSOD, so it should have captured the driver verifier info.

Box

Dell also recently released an update for the graphics driver, which I installed like a week ago.

Thanks,
G

Hello!
Thanks for the help.

Here is an updated link.

Box

I got another BSOD, but this time it said that there was an error in dump file creation. The laptop was just sitting there in sleep mode.

Also, there was a recent BIOS update I did today, which mentioned "microcode updates to increase stability" (lets hope it works).