[SOLVED] ntoskrnl.exe causing bsod, no idea how to solve this problem

Sep 1, 2019
9
1
15
0
I'm at a lost my computer keeps BSOD on me it's alway ntoskrnl.exe. I have tried everything i could find to fix the issue, Doing the DISM.exe to reset the system files or what ever it does again. setting my bios back to stock, turning off the OC for my intergrated GPU and ram setting it back to stock clock. Last night it seem to run great for 3+hrs with no issues. The bsod seems to happen at random too. It seems to either be a kernel security check or irql not equal or less. I'm at a lost.

I have a msi B450M gaming plus, 16gb of G skill Ripjaw V 3000 ram, with a 2400G. As far as i know all drivers seem to be installed correctly with 0 issues. I tested the ram in windows with zero errors.
 

PC Tailor

Dignified
Herald
Due to the number of dump files, I have simply run the last 4 as this should give us enough information. You can view the full reports here that include all the information you should need:

Dump 1: https://pste.eu/p/8sxU.html (KERNEL_SECURITY_CHECK_FAILURE)
Dump 2: https://pste.eu/p/vw5J.html (KERNEL_SECURITY_CHECK_FAILURE)
Dump 3: https://pste.eu/p/EEar.html (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
Dump 4: https://pste.eu/p/cubP.html (KERNEL_MODE_HEAP_CORRUPTION)

Being as there are multiple dumps, the decription and detail of each bug check can be found in each of the reports:

Security checks and system thread are often drivers, but the variation of bug checks could potentially mean we may need to look at hardware, however you have plenty of third party drivers to go off. Problem with Windows is often it doesn't know what to blame when it crashes, so when it blames ntoskrnl.exe - in reality, that's just kernel that crashed, but not what caused the crash.

So from the reports, some things to consider:
  • DX often means GPU drivers are faulting - so you'll need to look at these.
  • Your AMD Chipset drivers are out of date, you can install the latest from here: https://www.msi.com/Motherboard/support/B450M-GAMING-PLUS#down-driver&Win10 64 (don't ever use third party driver updaters)
  • Your BIOS is up to date.
  • MSI Afterburner can cause BSOD, so I would uninstall this or disable it using autoruns (link in report above third party modules).
  • You may want to check your HID drivers from Logitech are up to date
  • Antivirus (especially AVG) can cause various problems, so once we've covered the above, if there is no change, next step may be to uninstall AV and run on Windows Defender to verify if the issue repeats.
  • Does the BSOD occur every time you use the PC?
EDIT: Modified GPU comment.
 
Last edited:
Reactions: Hackodis

PC Tailor

Dignified
Herald
Welcome to the forums my friend!

Unfortunately every stop error (BSOD) you encounter is completely different, and every stop error also has a series of sub types, which all mean something different too. So the DISM / OC etc. will only really help depending on the problem you are encountering.

Typically IRQL etc. can often be driver based.

Please see this guide to enable minidumps and post the links to the minidumps here so we can help debug :)https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/
 

PC Tailor

Dignified
Herald
Due to the number of dump files, I have simply run the last 4 as this should give us enough information. You can view the full reports here that include all the information you should need:

Dump 1: https://pste.eu/p/8sxU.html (KERNEL_SECURITY_CHECK_FAILURE)
Dump 2: https://pste.eu/p/vw5J.html (KERNEL_SECURITY_CHECK_FAILURE)
Dump 3: https://pste.eu/p/EEar.html (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
Dump 4: https://pste.eu/p/cubP.html (KERNEL_MODE_HEAP_CORRUPTION)

Being as there are multiple dumps, the decription and detail of each bug check can be found in each of the reports:

Security checks and system thread are often drivers, but the variation of bug checks could potentially mean we may need to look at hardware, however you have plenty of third party drivers to go off. Problem with Windows is often it doesn't know what to blame when it crashes, so when it blames ntoskrnl.exe - in reality, that's just kernel that crashed, but not what caused the crash.

So from the reports, some things to consider:
  • DX often means GPU drivers are faulting - so you'll need to look at these.
  • Your AMD Chipset drivers are out of date, you can install the latest from here: https://www.msi.com/Motherboard/support/B450M-GAMING-PLUS#down-driver&Win10 64 (don't ever use third party driver updaters)
  • Your BIOS is up to date.
  • MSI Afterburner can cause BSOD, so I would uninstall this or disable it using autoruns (link in report above third party modules).
  • You may want to check your HID drivers from Logitech are up to date
  • Antivirus (especially AVG) can cause various problems, so once we've covered the above, if there is no change, next step may be to uninstall AV and run on Windows Defender to verify if the issue repeats.
  • Does the BSOD occur every time you use the PC?
EDIT: Modified GPU comment.
 
Last edited:
Reactions: Hackodis
Sep 1, 2019
9
1
15
0
The bsod are random at best. Last night when i got home computer was stable for 3+ hrs. It doesn't seem everytime i use my computer which is weird. Which can be frustrating. I'll try those fixes you suggested and see what happens.
Oh as for my mouse and keyboard, i did download the latest drivers, so those should be good (i think) when i reinstalled everything.
 

Colif

Win 10 Master
Moderator
ntoskrnl isn't causing BSOD, its the victim. It is what crashed but it never crashes without being pushed.

ntoskrnl - windows Kernel. Windows cannot run without it. It sits between Applications & Hardware. . It handles all driver requests, power management, and memory management.

3 out of the 4 errors shown above by PC Tailor, all mention directx.

Try doing this and grab new GPU drivers - https://forums.tomshardware.com/faq/how-to-perform-a-clean-install-of-your-video-card-drivers.2402269/ - might need to use a few different driver versions to find some that don't causd BSOD. If you got the last drivers from AMD, try windows update.

9 out of 10 times DirectX is blamed, its gpu drivers

See if that fixes your problems :)
 
Last edited:
Reactions: Hackodis
Sep 1, 2019
9
1
15
0
The computer seems to be running fine. I did the amd updates i missed. I uninstalled MSI to see if that was another cause. No issues last night playing apex last night for 2+ hrs. Gonna give it today to see what it does.
 
Reactions: PC Tailor

PC Tailor

Dignified
Herald
The computer seems to be running fine. I did the amd updates i missed. I uninstalled MSI to see if that was another cause. No issues last night playing apex last night for 2+ hrs. Gonna give it today to see what it does.
Good to hear so far, thanks @Colif for adding, yes I that's why I added the GPU drivers as the first item due to the DX faults. Let us know how it goes.
 
Sep 1, 2019
9
1
15
0
I'm gonna call it fixed. The computer has been running all day with zero issues. @PC Tailor Thank you for your help, i think it was just me missing some important updates.
Lesson learned ensure all your drivers are update to date after doing a pc build, don't let the excitement get to your head :D
Thanks to @Colif for stopping in and mentioning the GPU drivers.
Now i can really enjoy my pc with out being left frustrated. Thanks again guys!! Now i wish i could give you guys both a trophy for helping me.
 

ASK THE COMMUNITY

TRENDING THREADS