Error BSOD indicates the problematic driver is ntoskrnl.exe.
Error BSOD indicates the problematic driver is ntoskrnl.exe.
Hello,
I'm working on resolving a recurring problem where I consistently encounter BSODs after exporting videos or during gameplay. The issue was identified using the Bluescreen Viewer.
I've attempted several solutions:
- Ran memtest86 to check RAM, which showed no errors.
- Updated drivers via Windows and GPU settings.
- Applied driver updates from my ASUS manufacturer.
- Investigated the problematic ntoskrnl.exe driver.
...and more.
Could you assist in pinpointing the cause or guide me through updating the driver? I've been struggling for a while without progress.
Minidump file:
https://1drv.ms/f/s!Aj3HgdzJg5ALiYkXItzV...g?e=yW95yr
Thank you!
Just so you understand for what comes next, ntoskrnl.exe is the core of the Windows kernel. Standard utilities such as BlueScreenView highlight this part because it's the element that triggered the bug check. Yet, if a third-party driver misbehaves or a hardware fault occurs, the issue often surfaces only when control returns to the kernel and it verifies what the driver demands. Since the kernel can't fix driver code, it has no choice but to trigger a BSOD—highlighting ntoskrnl.exe as the problematic component. This is why examining the complete dump files is essential for tracing back the root cause, whether it's a driver or hardware fault.
In your situation, considering all the dumps together, this appears to point toward a RAM problem. The evidence suggesting this direction includes:
- None of the dumps mention any third-party drivers on the call stack that led to the bug check—this often signals a hardware issue.
- One dump encounters a 0xC000005 exception, indicating a memory access violation (possibly due to an unallocated or paged-out page).
- Another dump is affected by a faulty instruction pointer.
- A third dump fails because of a bad stack pointer.
- It's extremely hard to identify another common cause besides faulty RAM. Memtest86 works well, but running it at least twice in a row, and preferably more than twice, is necessary to detect RAM issues.
- You seem to have only a single 32GB RAM module installed, which isn't ideal (as dual-channel memory isn't utilized), but it also limits the ability to test RAM by removing modules.
I recommend using Memtest86 (free) up to four times consecutively; avoid pausing between runs, as continuous stress is crucial to uncover subtle problems. If all four tests succeed, we'll shift focus to other potential sources.
Thank you for your response.
At first, I considered it to be RAM and haven’t completely eliminated the possibility. It seems unusual since I was running tests with my RAM (two 32GB DDR5 sticks). I checked each one separately and together, and the BSOD kept occurring. When I would experience a blue screen, I would replace the next stick and try again, which suggests both sticks might be faulty.
I eventually ordered new RAM from a different manufacturer. The RAM I currently have is from Corsair, while the new one is from Kingston. According to the specifications for my motherboard, both should function properly. Could XMP settings be influencing this issue?
I turned off XMP on my existing setup because it was increasing the number of BSODs.
Ensure the new Kingston RAM is set to disable XMP and any overclock/undervolt settings on the CPU. This will keep everything running at standard frequencies and voltages. If a BSOD occurs afterward, download the SysnativeBSODCollectionApp, run it, and upload the generated zip file to the cloud with a link. This app gathers essential troubleshooting data, preventing repeated requests for similar solutions. It does not store any personal information—review the collected details before uploading if desired, but avoid modifying anything in the app.
After thorough testing of both new and old RAM, I identified the problem. While reviewing BIOS settings and using Intel Extreme Tuning Utility, I noticed my motherboard was running at an unstable 5.5GHz. Running it with fresh RAM only triggered a blue screen again, confirming the RAM wasn’t faulty—overclocking was the real cause. Lowering the frequency to 5GHz with improved voltage settings stopped the BSOD, even after clearing CMOS. Despite error codes suggesting a hardware fault, the system kept overclocking. I realized it was automatically adjusting beyond safe limits. It’s reassuring to know such instability can occur without manual intervention.
Also, thank you for pointing this out.
@ubuysa
For reminding me to disable XMP and any overclock/undervolt settings on the CPU so everything operates at default speeds. That clarified my next steps.
TLDR: My PC was overclocking itself improperly, causing the BSODs; once I adjusted settings, everything stabilized.
Thanks!
Greatly appreciated! It's unusual to encounter an automatic overclock, though overclocking is often a frequent cause of BSODs.