How to Fix Ntoskrnl.exe Blue Screen Error on Windows

Your PC crashes to a blue screen, and the error names ntoskrnl.exe. That file sounds suspicious, but it is not a virus. It is the Windows kernel itself, the program at the center of the operating system.

Here is the twist. Ntoskrnl.exe is rarely the real cause. It is usually the victim. A bad driver, faulty RAM, or corrupt system file trips it up, and the blue screen blames the file it tripped over. This guide walks through 7 fixes for the ntoskrnl.exe blue screen error.

What Is Ntoskrnl.exe?

Ntoskrnl.exe stands for Windows NT Operating System Kernel. It is the heart of Windows. It manages memory, schedules processes, handles hardware communication, and runs security checks. Every program on your PC talks to hardware through this file.

Because it sits at the center of everything, almost any deep system failure passes through it. That is why so many different blue screens list ntoskrnl.exe as the faulty module. The name tells you where Windows noticed the problem, not what caused it.

You will find the file in C:\Windows\System32. Never delete or rename it. Windows cannot boot without it.

Why It Shows Up in Blue Screens

Common stop codes tied to ntoskrnl.exe include MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, and PAGE_FAULT_IN_NONPAGED_AREA. Behind those codes, the usual suspects are:

• Outdated or corrupt device drivers, especially graphics and network drivers
• Faulty or failing RAM
• Corrupt Windows system files
• Disk errors on the system disk
• Overheating CPU or GPU
• Unstable overclocks

The fixes below address each of these in order, from most likely to least likely.

Before You Start: Note the Stop Code

Write down the stop code on the blue screen, such as MEMORY_MANAGEMENT. It hints at the cause. MEMORY_MANAGEMENT points to RAM, while IRQL_NOT_LESS_OR_EQUAL often points to a driver. If the crashes stop you from using Windows at all, boot into Safe Mode first. Hold Shift while clicking Restart, then choose Troubleshoot, Advanced options, Startup Settings.

Fix 1: Update Your Drivers

Bad drivers cause most ntoskrnl.exe crashes. Start with the big three: graphics, chipset, and network drivers.

1. Press Win + X and open Device Manager.
2. Expand Display adapters, right-click your GPU, and choose Update driver.
3. Repeat for Network adapters and your chipset entries.
4. For the newest versions, download drivers from the maker’s site (NVIDIA, AMD, Intel, or your laptop maker) instead of relying on Windows Update.

An outdated BIOS can also trigger these crashes. If your board uses an American Megatrends BIOS, follow our guide to updating an American Megatrends BIOS before you move on.

Fix 2: Test Your RAM with Windows Memory Diagnostic

Faulty RAM is the second most common cause. Windows includes a free memory test.

1. Press Win + R, type mdsched.exe, and press Enter.
2. Choose “Restart now and check for problems”.
3. The PC reboots into the test. Let it finish.
4. After Windows loads, check Event Viewer under Windows Logs, System for MemoryDiagnostics results.

If the test finds errors, one of your RAM sticks is failing. Power down, remove all but one stick, and retest to find the bad one. Replace it.

Fix 3: Repair System Files with SFC and DISM

Corrupt system files can crash the kernel. Two built-in tools repair them.

1. Open Command Prompt as administrator.
2. Type sfc /scannow and press Enter. Wait for it to finish.
3. Then run DISM /Online /Cleanup-Image /RestoreHealth and wait again.
4. Restart your PC.

If SFC itself throws an error, see our fix for the Windows Resource Protection error that blocks the scan from running.

Fix 4: Check Your Disk with CHKDSK

Bad sectors on the system disk can corrupt files the kernel needs. Open Command Prompt as administrator and run chkdsk C: /f /r. Type Y when asked to schedule the check, then restart. The scan can take a while on large drives. If CHKDSK reports many bad sectors, back up your data and plan for a new SSD.

Fix 5: Do a Clean Boot

A clean boot starts Windows with only Microsoft services running. It tells you whether a third-party program is behind the crashes.

1. Press Win + R, type msconfig, and press Enter.
2. On the Services tab, check “Hide all Microsoft services”, then click Disable all.
3. On the Startup tab, open Task Manager and disable all startup items.
4. Restart and use the PC normally.

If the crashes stop, turn services back on in small groups until the crashes return. The last group holds the culprit, often an antivirus tool, RGB app, or overclocking utility.

Fix 6: Check for Overheating

Heat causes random crashes that look like software bugs. Install HWiNFO or HWMonitor and watch your CPU and GPU temps under load. Anything past 90C during games or heavy work is too hot.

Fix cooling before you chase software. Clean dust from fans and heatsinks with compressed air, and check that all fans spin. On older PCs, fresh thermal paste can drop CPU temps a lot. Also remove any overclock while you test.

Fix 7: Use System Restore

If the crashes started after a driver update or new program, roll Windows back. Press Win + R, type rstrui, and press Enter. Pick a restore point from before the crashes began. Your personal files stay untouched, but installed programs and drivers from after that point will be gone.

If Nothing Works

A few options remain. Run MemTest86 from a USB stick for a deeper RAM test. Test with one RAM stick at a time. Or reset Windows through Settings, Recovery, keeping your files.

Seeing a boot message about fTPM after a CPU swap? That is a separate issue. See our fix for the New CPU installed, fTPM NV corrupted error. Fixing other Windows errors? Our guide to error code 0x80070043 covers a common network-path failure.

We publish Windows repair guides like this every week at AxeeTech. Read more about us.

Frequently Asked Questions

Is ntoskrnl.exe a virus?

No. Ntoskrnl.exe is a Windows system file, the operating system kernel. Malware sometimes uses a similar name, but the real file lives in C:\Windows\System32 and is safe.

Can I delete ntoskrnl.exe to stop the crashes?

No. Windows cannot boot without it. Deleting it will break your system. Fix the driver or hardware problem behind the crash instead.

Why does ntoskrnl.exe use so much RAM?

High RAM use by the System process is a different issue from blue screens. It usually comes from a memory leak in a driver. Update your drivers and check Task Manager for the heaviest programs.

Which stop codes point to ntoskrnl.exe?

The most common are MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, and PAGE_FAULT_IN_NONPAGED_AREA. The code hints at the cause but the fixes above cover all of them.

Should I reinstall Windows?

Try the 7 fixes first. Reinstall only if crashes continue after clean RAM tests, fresh drivers, and SFC/DISM repairs. A reinstall rules out software for good.