Multiple BSODs, mostly KMODE_EXCEPTION_NOT_HANDLED

Joses113 · 11 Nov 2023

Windows Version: 22H2 (OS Build 19045.3570)

BSOD Files

Most BSODs have been KMODE_EXCEPTION_NOT_HANDLED

Steps I've tried:

- sfc /scan now, first passed fixed errors, second pass detected no errors.
- Display drivers removed with DDU and reinstalled.
- chkdsk /f
- HCI Memtest passed with slight XMP

All these BSODs have happened during playing Football Manager (FM) 2024, which can be fairly RAM intensive. These all started yesterday, nothing particular in-game seems to cause it. I had been playing FM22 for years with no problems and also have been playing the beta of FM24 for about 2.5 weeks (2 weeks beta, 4 days full release) until BSODs started happening yesterday.

zbook · 11 Nov 2023

Were any hardware components replaced after the September BSODs with bugcheck WHEA 124?

Were any BSOD misbehaving drivers replaced after using WDV?

Uninstall or uninstall and reinstall these drivers then restart Windows Driver Verifier (WDV):
Enable and Disable Driver Verifier in Windows 10

a) ene.sys

b) nvlddmkm.sys > use DDU

c) e2xw10x64.sys
https://download.msi.com/dvr_exe/Killer_network_w10.zip

d) iastora.sys
https://download.msi.com/dvr_exe/int...torage_w10.zip

enetechio EneTechIo \??\c:\windows\system32\drivers\ene.sys

e2xw10x64 NDIS Miniport Driver for Killer PCI-E Gigabit Ethernet Controller c:\windows\system32\drivers\e2xw10x64.sys

iastora iaStorA c:\windows\system32\drivers\iastora.sys

Display Driver Uninstaller: How to use | Tutorials

Display Driver Uninstaller (DDU) | Wagnardsoft

Official Drivers | NVIDIA

Code:

Name	[00000002] Killer E2200 Gigabit Ethernet Controller
Adapter Type	Ethernet 802.3
Product Type	Killer E2200 Gigabit Ethernet Controller
Installed	Yes
PNP Device ID	PCI\VEN_1969&DEV_E091&SUBSYS_79171462&REV_13\4&164DD7F4&0&00E3
Last Reset	11/11/2023 21:34
Index	2
Service Name	e2xw10x64
IP Address	192.168.1.116, fe80::9194:913f:a24f:a11a
IP Subnet	255.255.255.0, 64
Default IP Gateway	192.168.1.1
DHCP Enabled	Yes
DHCP Server	192.168.1.1
DHCP Lease Expires	12/11/2023 21:34
DHCP Lease Obtained	11/11/2023 21:34
MAC Address	‪D8:CB:8A:53:CD:20‬
Memory Address	0xF7100000-0xF71FFFFF
I/O Port	0x0000D000-0x0000DFFF
IRQ Channel	IRQ 19
Driver	C:\WINDOWS\SYSTEM32\DRIVERS\E2XW10X64.SYS (9.0.0.46, 161.73 KB (165,608 bytes), 07/05/2018 20:42)

Code:

Name	NVIDIA GeForce GTX 1080
PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_142619DA&REV_A1\4&B7B0A11&0&0008
Adapter Type	NVIDIA GeForce GTX 1080, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1080
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll
Driver Version	31.0.15.4601
INF File	oem4.inf (Section024 section)
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_677DA8A9230CEA15\NVLDDMKM.SYS (31.0.15.4601, 56.00 MB (58,720,920 bytes), 10/11/2023 22:18)

ubuysa · 12 Nov 2023

From looking through the dumps the most likely cause here is bad RAM. Of the five dumps in November, four of them fail with a 0xC000005 exception code - that's a memory access violation. In one of the dumps the WinDbg triage even flags bad RAM as the cause...

Code:

MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
MEMORY_CORRUPTOR:  ONE_BIT
STACK_COMMAND:  .thread ; .cxr ; kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

The two 0x124 bugchecks in September may well have also been RAM related, but there's no way to know. They were machine check exceptions, which is what you'd expect from bad RAM.

You Application log also contains several application errors with 0xC0000005 exception codes, and there are many RADAR_PRE_LEAK_64 application errors, and for different applications. These can also be caused by bad RAM.

Either download Memtest86 (free) and use that to test your RAM or, better yet, remove one (or two) sticks and run with the others for a day or two - or until you get a BSOD. Rotate the sticks until you have tested for a day or two with each stick removed. That method is guaranteed to find a flaky RAM stick.

One other thing....
One of the November dumps is a Driver Verifier caused BSOD. Do you have Driver Verifier running, if so why? Driver VErfier needs to be started with very specific options to be useful, so for now I'd advise you to disable it via the verifier /reset command (then reboot).

The Driver Verfier caused BSOD flags the ene.sys driver as mismanaging pool allocations. This is a driver associated with keyboard lighting control software, the version you have installed is quite old, dating from 2020...

Code:

0: kd> lmvm ene
Browse full module list
start             end                 module name
fffff808`f1d40000 fffff808`f1d48000   ene      T (no symbols)           
    Loaded symbol image file: ene.sys
    Image path: ene.sys
    Image name: ene.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May  8 09:07:19 2020 (5EB4F717)
    CheckSum:         0000E8E9
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would suggest that, for this one dump, you look for an update to whatever keyboard lighting control you use.

Joses113 · 12 Nov 2023

zbook said:

Were any hardware components replaced after the September BSODs with bugcheck WHEA 124?

Were any BSOD misbehaving drivers replaced after using WDV?

Uninstall or uninstall and reinstall these drivers then restart Windows Driver Verifier (WDV):
Enable and Disable Driver Verifier in Windows 10

a) ene.sys

b) nvlddmkm.sys > use DDU

c) e2xw10x64.sys
https://download.msi.com/dvr_exe/Killer_network_w10.zip

d) iastora.sys
https://download.msi.com/dvr_exe/int...torage_w10.zip

enetechio EneTechIo \??\c:\windows\system32\drivers\ene.sys

e2xw10x64 NDIS Miniport Driver for Killer PCI-E Gigabit Ethernet Controller c:\windows\system32\drivers\e2xw10x64.sys

iastora iaStorA c:\windows\system32\drivers\iastora.sys

Display Driver Uninstaller: How to use | Tutorials

Display Driver Uninstaller (DDU) | Wagnardsoft

Official Drivers | NVIDIA

Code:

Name	[00000002] Killer E2200 Gigabit Ethernet Controller
Adapter Type	Ethernet 802.3
Product Type	Killer E2200 Gigabit Ethernet Controller
Installed	Yes
PNP Device ID	PCI\VEN_1969&DEV_E091&SUBSYS_79171462&REV_13\4&164DD7F4&0&00E3
Last Reset	11/11/2023 21:34
Index	2
Service Name	e2xw10x64
IP Address	192.168.1.116, fe80::9194:913f:a24f:a11a
IP Subnet	255.255.255.0, 64
Default IP Gateway	192.168.1.1
DHCP Enabled	Yes
DHCP Server	192.168.1.1
DHCP Lease Expires	12/11/2023 21:34
DHCP Lease Obtained	11/11/2023 21:34
MAC Address	‪D8:CB:8A:53:CD:20‬
Memory Address	0xF7100000-0xF71FFFFF
I/O Port	0x0000D000-0x0000DFFF
IRQ Channel	IRQ 19
Driver	C:\WINDOWS\SYSTEM32\DRIVERS\E2XW10X64.SYS (9.0.0.46, 161.73 KB (165,608 bytes), 07/05/2018 20:42)

Code:

Name	NVIDIA GeForce GTX 1080
PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_142619DA&REV_A1\4&B7B0A11&0&0008
Adapter Type	NVIDIA GeForce GTX 1080, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1080
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_677da8a9230cea15\nvldumdx.dll
Driver Version	31.0.15.4601
INF File	oem4.inf (Section024 section)
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_677DA8A9230CEA15\NVLDDMKM.SYS (31.0.15.4601, 56.00 MB (58,720,920 bytes), 10/11/2023 22:18)

No hardware changed after September - I was attempting to overclock either my CPU/RAM and couldn't get it stable so gave up there.

Thanks I'll update these drivers and check what happens.

- - - Updated - - -

ubuysa said:

From looking through the dumps the most likely cause here is bad RAM. Of the five dumps in November, four of them fail with a 0xC000005 exception code - that's a memory access violation. In one of the dumps the WinDbg triage even flags bad RAM as the cause...

Code:

MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
MEMORY_CORRUPTOR:  ONE_BIT
STACK_COMMAND:  .thread ; .cxr ; kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

The two 0x124 bugchecks in September may well have also been RAM related, but there's no way to know. They were machine check exceptions, which is what you'd expect from bad RAM.

You Application log also contains several application errors with 0xC0000005 exception codes, and there are many RADAR_PRE_LEAK_64 application errors, and for different applications. These can also be caused by bad RAM.

Either download Memtest86 (free) and use that to test your RAM or, better yet, remove one (or two) sticks and run with the others for a day or two - or until you get a BSOD. Rotate the sticks until you have tested for a day or two with each stick removed. That method is guaranteed to find a flaky RAM stick.

One other thing....
One of the November dumps is a Driver Verifier caused BSOD. Do you have Driver Verifier running, if so why? Driver VErfier needs to be started with very specific options to be useful, so for now I'd advise you to disable it via the verifier /reset command (then reboot).

The Driver Verfier caused BSOD flags the ene.sys driver as mismanaging pool allocations. This is a driver associated with keyboard lighting control software, the version you have installed is quite old, dating from 2020...

Code:

0: kd> lmvm ene
Browse full module list
start             end                 module name
fffff808`f1d40000 fffff808`f1d48000   ene      T (no symbols)           
    Loaded symbol image file: ene.sys
    Image path: ene.sys
    Image name: ene.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May  8 09:07:19 2020 (5EB4F717)
    CheckSum:         0000E8E9
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would suggest that, for this one dump, you look for an update to whatever keyboard lighting control you use.

- RAM has passed Windows Memory Diagnostic and memtest (w/ DRAM Calculator) but I will try checking the physical check as well.
- I have disabled driver verifier as I put me in a BSOD loop, I won't be using it again.
- I'll update ene.sys as well.

ubuysa · 12 Nov 2023

Joses113 said:

I have disabled driver verifier as I put me in a BSOD loop, I won't be using it again.

In which case you have a flaky driver there. It will be a boot loaded driver of course but if Driver Verifier BSODs it then it's definitely a bad driver and you need to locate it and update/remove it. If it fails Driver Verifier then it will be causing you continuing problems - it's probably the ene.sys driver above however.

You can create a log of drivers loaded at boot time, and it is woirth doing, just in case it wasn't ene.sys. That log will enable us to identify all the boot-loaded third-party drivers, and that will give us a head start on finding the bad one. To do that enter the msconfig command into the Run command box, the msconfig dialog will open. Click the Boot tab and in there check the Boot Log checkbox and then click OK. Reboot.

On rebooting, navigate to the C:\Windows folder and locate the file ntbtlog.txt, upload it to the cloud somewhere with a (public) link to it here. Then enter the msconfig dialog again and uncheck the Boot Log checkbox.

zbook · 12 Nov 2023

1) Please run Tuneup plus > post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging

2) After replacing the drivers monitor the computer for:
a) hangs
b) freezes
c) BSOD
d) unexpected shutdowns and restarts without BSOD

For any of the above post a new V2 share link into the newest post.

3) When WDV was used which link had been used for the test settings?

Joses113 · 15 Nov 2023

I want to thank everyone for their help on this. I haven't had any BSODs for about 3 days now after hours of use on each day, so fingers crossed all is well. FM24 is no longer causing BSODs.

I had been running TestMem5 during my last post and I passed 3 cycles of Absolut, so I haven't done the manual check of RAM as I'd now passed Windows Mem Diagnostic, HCI MemTest and now TestMem5.

What I did do as advised was update Killer Network driver and remove ene.sys.