The BSOD occurs while using the system normally, linked to ntoskrnl.exe.
The BSOD occurs while using the system normally, linked to ntoskrnl.exe.
Hello.
I'm trying to resolve my BSOD issues. BlueScreenView shows ntoskrnl.exe as the cause for the last three crashes. I've run chkdsk on all drives and everything looks fine.
CPU: Ryzen 5 5600X
GPU: AMD RX 9070
MOBO: Gigabyte X470 Aorus Ultra Gaming
RAM: Corsair DDR4 16GB CL16
PSU: Seasonic Focus+ 650W 80+ GOLD
Windows 11 Professional (x64)
Version 23H2, Build 22631.5909
The issue stems from the lack of support for Windows Mixed Reality in recent updates. If an update is necessary to fix this, I accept it, but I still suspect something else is at play.
Minidump files
Hello, and welcome!
It's worth noting that many BSODs indicate ntoskrnl.exe as the problematic module. In reality, this is the Windows kernel, and it isn't at fault. Typically, a third-party driver malfunctions, but an error is only flagged when the system regains control and realizes the driver's request is invalid, incorrect, or otherwise problematic. Since the kernel lacks insight into the cause of the driver issue and doesn’t understand whether this could damage user data, it triggers a BSOD and initiates a memory dump. At that moment, the kernel itself was running ntoskrnl.exe, which is why tools like BlueScreenView and WhoCrashed capture these events.
Regarding your dumps, they highlight failures across various operations, but the key factor in all cases is RAM. Your Corsair Vengeance DDR4 2 x 8GB RAM sticks (CMR16GX4M2C3000C15) operate at 3000MHz, which exceeds their rated speed of 2133MHz.
I recommend you first disable the overclock in the BIOS via XMP/DOCP settings so the RAM runs at its standard speed of 2133MHz. Then check if the BSODs persist.
If they do, it likely points to a faulty stick. To verify, run Memtest86 on it...
Download
Memtest86 (free), use the extracted imageUSB.exe tool to create a bootable USB drive with Memtest86 (a 1GB file is sufficient).
Perform this on another machine if possible, as you can't fully rely on your current system at this stage.
After booting the USB, Memtest86 will begin scanning immediately.
If no errors appear after completing four iterations of the 13 tests in the free version, restart Memtest86 and repeat with another set of four tests.
Even a single bit error constitutes a failure.