How To Resolve Ntoskrnl.Exe BSOD Error on Windows 11/10

Dealing with the Blue Screen of Death (BSOD) in Windows 11, especially the infamous ntoskrnl.exe error, can be super frustrating. It pops up unexpectedly, often without warning, and leaves you wondering what just happened. Usually, this kind of error hints at underlying hardware hiccups, corrupted system files, or driver conflicts — and trying to fix it without knowing where to start can feel like chasing your tail. So, here’s a rundown of some tried-and-true ways to troubleshoot and hopefully get rid of that BSOD. Expect a bit of trial and error — because Windows, of course, has to make it harder than it needs to.

How to Fix the ntoskrnl.exe BSOD Error in Windows 11

Check Your Memory (RAM) for Errors

Memory issues are a common culprit behind BSODs, especially if your RAM’s acting up or has bad sectors. This is why it’s one of the first places to check. RAM failures tend to cause weird crashes and errors, so catching them early can save a lot of headaches.

Hit the Windows key and search for Memory. Click on Windows Memory Diagnostic.
In the popup, pick Restart Now and check for problems (recommended). On some setups, it might seem like it’s hanging, but just let it do its thing while your PC reboots into the diagnostic tool.
The tool will scan your RAM on reboot. If errors show up, try swapping RAM modules around or reseating them (take out, dust off, pop back in).On some machines, doing this actually clears errors — weird, but it’s worth a shot.

Sometimes, the memory test throws errors on one slot but not another, so…try different configurations. If errors keep popping up, new RAM might be necessary. On the other hand, if all’s clear, move on to the next fix.

Run SFC and DISM to Repair System Files

Corrupt system files can cause all kinds of BSODs, including this ntoskrnl.exe thing. Running System File Checker (SFC) and Deployment Image Servicing and Management (DISM) scans helps fix corrupted files automatically. It’s like giving Windows a health check-up.

Press Windows + X and choose Terminal (Admin), or search for PowerShell, then select Run as Administrator.
First, type: DISM /Online /Cleanup-Image /RestoreHealth and hit Enter. This will take some time, so grab a coffee. It scans and repairs Windows image issues that might be causing the BSOD.
Once the DISM command completes, run the SFC scan: sfc /scannow. This checks your Windows files for corruption and repairs them if needed.

On some systems, you might have to run these commands multiple times or reboot between scans. If corrupt files were the issue, this should help stabilize things. If not, another method might be needed.

Check Your Hard Drive for Errors

A failing or noisy hard drive can also throw Windows into chaos, leading to BSODs. Use the built-in chkdsk utility to scan and fix disk problems.

Open PowerShell as Administrator (same way as before).
Type: chkdsk /r /f and press Enter. It might say the drive is in use and ask if you want to schedule a check on restart — just type Y and hit Enter.
Reboot your PC. During startup, chkdsk will run and scan your disk. Depending on size and errors, it might take a while — don’t panic if it seems slow.

Watch the results for any bad sectors or errors. If disk issues are found, replacing the drive might be the ultimate fix, but in the meantime, fixing errors can help Windows avoid crashing.

Scan for Malware and Viruses

Since malware can hide deep in your system, it’s worth running a full virus scan if this error keeps happening. Windows Security (formerly Windows Defender) can do a good job, and it’s free.

Type Windows Security in the Start menu and open it.
Go to Virus & Threat Protection.
Click on Full Scan and then hit Scan Now. Yep, it might take a while, but it’s worth it to rule out malware as the cause.

If your antivirus finds anything nasty, follow the prompts to quarantine or remove it. Sometimes, malware corrupts system files or drivers, leading to ntoskrnl.exe errors. Cleaning that out might do the trick.

Update Drivers — Especially Graphics and Storage

Old or faulty drivers are notorious for causing BSODs, so updating them is a good move. Use Device Manager for a quick update—just right-click the suspected driver and select Update Driver. Or, for more control and newer drivers, visit the hardware manufacturer’s website.

Press Windows + X and pick Device Manager.
Look for your graphics card, storage controllers, or network devices — basically, anything that’s been around for a bit.
Right-click and choose Update Driver. Then, select Search automatically for drivers. Windows does its thing and downloads the latest if available.

After updating, restart your PC and see if the BSOD persists. If it does, consider rolling back recently updated drivers or using driver-specific tools like Intel Driver & Support Assistant or AMD Software.

Turn Off Overclocking — Or Reset Overclock Settings

If your system’s overclocked — and yes, many folks do it for extra speed — it might be causing instability. Overclocking pushes hardware beyond its certified limits, and on some setups, that leads to errors like ntoskrnl.exe BSODs.

To serious stability, it’s safer to revert to default settings. Usually, you can do this via your motherboard BIOS or UEFI settings. Power off, disconnect power, then reset BIOS to default (look for “Load Fail-Safe Defaults” or similar).

If you use third-party overclocking software, disable or remove it, and test the system again.

Perform a Clean Boot to Isolate Software Conflicts

Some third-party apps or services start sneaking in at boot, potentially causing conflicts. Doing a clean boot helps identify if anything non-essential is to blame.

Press Windows + R, type msconfig, hit Enter.
In the Services tab, check Hide all Microsoft services, then click Disable all.
Switch to the Startup tab, then click Open Task Manager.
Disable all startup items you see there by right-clicking and choosing Disable.
Close Task Manager, click OK, then restart your PC.

If the BSOD stops happening, re-enable services and startup items one by one to find the problematic app. A bit of patience, but it’s worth narrowing down what’s causing the chaos.

Update Windows 11

Finally, staying up-to-date is arguably the simplest fix. Microsoft releases patches that fix bugs, including those that cause blue screens. If you’re running an older build, updating might just resolve the error.

Press Windows and type Windows update settings.
Click on Check for updates. If any are found, click Download and install. Yeah, it might restart your PC several times, but it’s worth it.

Wrap-up and Final Tips

Honestly, fixing BSODs like this can be a bit of a game of trial and error. Sometimes, one fix alone works, other times, you have to stack a few. Don’t forget to keep your drivers updated, check hardware like RAM and HDD, and scan for malware. If the error persists even after all this, it could be a deeper hardware problem or even Windows itself needing a reinstall.

Hopefully, this shaves off a few hours for someone. Good luck troubleshooting!

Summary

Run memory diagnostics to check RAM health.
Use SFC and DISM to fix system file corruption.
Scan your hard drive for errors.
Do a full virus/malware scan.
Update your drivers, especially graphics and storage devices.
Turn off overclocking or reset BIOS to defaults.
Perform a clean boot to find conflicting apps.
Always keep Windows updated.

Wrap-up

That’s about as much as can be done without diving deeper into hardware diagnostics. Usually, a combo of these fixes will patch things up, but hardware problems can sneak in too. Just remember, it’s a process, and patience is key. If one method doesn’t work, try the next. Fingers crossed this helps someone out there deal with those pesky BSODs and get their system stable again.