Question Another BSOD thread - - - intermittent "ntoskrnl.exe"?

Feb 6, 2025
7
0
10
Morning folks,

I was going to put up a thread 2 weeks ago when this started happening again. However it was ok for 2 weeks following a BIOS update. Now again this morning I've had 3 back to back BSODs, starting with the dreaded ntoskrnl.exe one.

History, purchased this from Scan Computers about 3 years ago. Within the first month had problems and they replaced the motherboard. This fixed the issues. About 12 months ago started having blue screen errors and running MemTest found some errors so Scan replaced the Ram under warranty. Started having issues again 3 months ago, updated the Bios and reset the RAM to default clock speeds. 2 weeks ago, the issue is back, latest BIOS update has not resolved it. Recent Memtest passed succesfully.

Hoping there is some hero that can help me out. Dump files at the bottom.

Edition Windows 11 Pro
Version 24H2
Installed on 02/‎10/‎2024
OS build 26100.3194
Experience Windows Feature Experience Pack 1000.26100.48.0


CPU: Intel i9-12900K 3.2Ghz (OC to 4.7Ghz)
CPU cooler: AOI 3xs Systems
Motherboard: asus rog strix z690-f gaming wifi (BIOS Update 4101 03/12/2024)
Ram: Corsair dominator DDR5 2x16GB 5600 C36
SSD/HDD: 1 x 2tb Samsung 970 Evo Plus M2, 1x 2tb Samsung 980 Pro M2
GPU: EVGA 3080ti
PSU: Corsair RM850xw 3 years old
Chassis: Corsair 600d
OS: Windows 11
Monitor: Asus ROG PG279Q

https://www.dropbox.com/scl/fo/pfq4...ey=8ad95kni3wujrtbfr15vyz214&st=6zbcnxg6&dl=0
 
Last edited:
Welcome to the forums, newcomer!

Ram: Corsair dominator DDR5 2x16GB 5600 C36
The sweet spot for DDR5 platforms is DDR5-6000MHz, so you've got some performance left on the table. As of now, your ram is running with X.M.P disabled?

Can you see any firmware updates pending for your SSD's? Speaking of SSD's, did you install the driver meant for your 970 Evo;
listed as NVME driver v3.3
If you've mistyped the 970 Evo Plus as 970 Evo, no matter, the NVMe driver will work for both.

You can also open up Device Manager and see if anything is flagged with a yellow exclamation mark.
 
Thanks for taking the time to reply.

XMP is disabled. Actually looks like since the BIOS update it was set to AI Auto, not sure what that even means. I've posted some photos of my BIOS settings that hopefully mean something, also of note is the RAM seems to be set to 4800mhz.
I did do the 970 EVO Plus firmware update as it was flagged in Samsung Magician, its on firmware 2B2QEXM7, no mention of 3.3 but is no longer flagging as needing an update. The 980 is also on the latest firmware.

No yellow flags in Device Manager.

BIOS Settings
 
Last edited:
Morning folks,

I was going to put up a thread 2 weeks ago when this started happening again. However it was ok for 2 weeks following a BIOS update. Now again this morning I've had 3 back to back BSODs, starting with the dreaded ntoskrnl.exe one.

History, purchased this from Scan Computers about 3 years ago. Within the first month had problems and they replaced the motherboard. This fixed the issues. About 12 months ago started having blue screen errors and running MemTest found some errors so Scan replaced the Ram under warranty. Started having issues again 3 months ago, updated the Bios and reset the RAM to default clock speeds. 2 weeks ago, the issue is back, latest BIOS update has not resolved it. Recent Memtest passed succesfully.

Hoping there is some hero that can help me out. Dump files at the bottom.

Edition Windows 11 Pro
Version 24H2
Installed on 02/‎10/‎2024
OS build 26100.3194
Experience Windows Feature Experience Pack 1000.26100.48.0


CPU: Intel i9-12900K 3.2Ghz (OC to 4.7Ghz)
CPU cooler: AOI 3xs Systems
Motherboard: asus rog strix z690-f gaming wifi (BIOS Update 4101 03/12/2024)
Ram: Corsair dominator DDR5 2x16GB 5600 C36
SSD/HDD: 1 x 2tb Samsung 970 Evo Plus M2, 1x 2tb Samsung 980 Pro M2
GPU: EVGA 3080ti
PSU: Corsair RM850xw 3 years old
Chassis: Corsair 600d
OS: Windows 11
Monitor: Asus ROG PG279Q

https://www.dropbox.com/scl/fo/pfq4...ey=8ad95kni3wujrtbfr15vyz214&st=6zbcnxg6&dl=0
strange, you have
asmedia sata driver installed
Asmedia 106x SATA Host Controller Driver
asstahci64.sys Tue Jun 23 23:39:30 2020
but the tech sheet for your motherboard does not list this device. it lists intel chipset device.

notes: your motherboard has a firmware update for audio devices. You have old streaming audio installed.

AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019

various bugchecks. looks like something causing access of a invalid memory address.

---------
got interrupted, will get back in a few
------------
bugchecks. most current: access violation when swapping in data.
second bugcheck access violation from PROCESS_NAME: GameBarPresenc

third: bugcheck trying to read a registry setting. paget table entry problem
4th bugcheck, bad address used trying to read registry

5th bugcheck (0ldest) has a stack corruption.
what is this driver for?
OETIO.SYS ***** Invalid (D4CDD978)
(unexpected driver name, can not find on google)
looks like the dump was corrupted and the file should have been Netio.sys with the same internal codes.

i would first start by updating the drive controller driver. I would also delete the pagefile.sys and create a new one. you might also run crystaldiskinfo.exe and read the status of the drive.
you might also check to see if there is a firmware update for your drives.

I can not rule out that you have a driver that is corrupting system memory. you might consider google how to make windows delete the pagefile.sys on system reboot. make the registry changes and reboot your system more often to see if the problem is reduced.

you might also apply the motherboard audio firmware update, and try to update you streaming media audio drivers if you can. I would also disable any audio source that you do not use.
 
Last edited:
strange, you have
asmedia sata driver installed
Asmedia 106x SATA Host Controller Driver
asstahci64.sys Tue Jun 23 23:39:30 2020
but the tech sheet for your motherboard does not list this device. it lists intel chipset device.

notes: your motherboard has a firmware update for audio devices. You have old streaming audio installed.

AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019

various bugchecks. looks like something causing access of a invalid memory address.

---------
got interrupted, will get back in a few
------------
bugchecks. most current: access violation when swapping in data.
second bugcheck access violation from PROCESS_NAME: GameBarPresenc

third: bugcheck trying to read a registry setting. paget table entry problem
4th bugcheck, bad address used trying to read registry

5th bugcheck (0ldest) has a stack corruption.
what is this driver for?
OETIO.SYS ***** Invalid (D4CDD978)
(unexpected driver name, can not find on google)
looks like the dump was corrupted and the file should have been Netio.sys with the same internal codes.

i would first start by updating the drive controller driver. I would also delete the pagefile.sys and create a new one. you might also run crystaldiskinfo.exe and read the status of the drive.
you might also check to see if there is a firmware update for your drives.

I can not rule out that you have a driver that is corrupting system memory. you might consider google how to make windows delete the pagefile.sys on system reboot. make the registry changes and reboot your system more often to see if the problem is reduced.

you might also apply the motherboard audio firmware update, and try to update you streaming media audio drivers if you can. I would also disable any audio source that you do not use.
if you do not find a driver update, then I would attempt to run verifier to determine if some driver is corrupting memory. (hopefully, you will find a storage driver update or ssd firmware update that will fix the problem. crystaldiskinfo.exe might show poor health of the drive)
 
Thanks for the replies. I downloaded the latest audio drivers, but it says I already have them.

The Cystaldiskinfo.exe has given me drive health of 98% and 99%, the only red markers are because their ambient temperature is 66c which I assume was because I was playing PathOfExile.

I will attempt to install the Sata drivers (Intel according to the Asus website)
 
There's nothing particularly dreaded about ntoskrnl.exe in a dump, that's the Windows kernel. What happens is that when a driver fouls up Windows often don't know that the driver has fouled up until control passes back from the driver to the kernel. It's at this point that the kernel validates what the driver is trying to do, or what system functions it's asking for. If the kernel realises at this point that the driver has fouled up it has no choice but to BSOD, since there is no mechanism for the kernel to fix driver errors. The failing module in the resulting dump will, of course, be ntoskrnl.exe.

In the dumps you've uploaded the first thing that appears common and most likely to be the cause, is bad RAM. The first thing I'd suggest would be a RAM test using Memtest86....
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.