Fix ntoskrnl.exe BSOD Error in Windows 11

The ntoskrnl.exe BSOD (Blue Screen of Death) error in Windows 11 is typically caused by corrupted system files, faulty drivers, or hardware issues like failing RAM. The most reliable fix is to run the System File Checker (SFC) and DISM tools, then update drivers and check memory with Windows Memory Diagnostic.

What Is ntoskrnl.exe and Why Does It Crash?

ntoskrnl.exe (NT OS Kernel) is the core kernel of Windows. It manages memory, processes, and hardware abstraction. When it throws a BSOD, the error code often appears as SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, KERNEL_DATA_INPAGE_ERROR, or IRQL_NOT_LESS_OR_EQUAL. The crash usually means the kernel tried to access a memory address or driver data that was invalid, corrupted, or already freed.

Common triggers include:

• Outdated or corrupted device drivers (especially GPU, network, or storage controllers)
• Faulty RAM modules or incorrect memory timings
• Corrupted system files after a failed update or power loss
• Disk errors on the system drive
• Overheating or unstable overclocks (CPU, GPU, or memory)

Before You Start: Backup and Safe Mode

Some fixes require multiple restarts. Before making changes, back up important files to an external drive or cloud. If the BSOD happens every boot, enter Safe Mode:

1. Restart your PC and press F8 (or hold Shift while clicking Restart) to get to the Recovery menu.
2. Go to Troubleshoot > Advanced options > Startup Settings and click Restart.
3. Press 4 or F4 to boot into Safe Mode.

In Safe Mode, only essential drivers load, which often prevents the crash and lets you run diagnostics.

Fix 1: Run SFC and DISM (System File Repair)

Corrupted system files are the #1 cause of ntoskrnl.exe BSODs. The System File Checker (SFC) scans protected files and replaces damaged ones. DISM fixes the system image that SFC relies on.

1. Open Command Prompt as Administrator (search “cmd”, right-click, “Run as administrator”).
2. Type sfc /scannow and press Enter. Wait for it to finish (may take 10-20 minutes).
3. If SFC reports errors, run DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
4. Restart your PC and run sfc /scannow again to verify the fix.

If SFC cannot repair a file, you may need to run the same commands from the Recovery Environment (Advanced startup > Command Prompt).

Fix 2: Update or Roll Back Drivers

Faulty drivers are the second most common trigger. The kernel loads drivers for every hardware component, and a buggy driver can cause a memory access violation.

• Update drivers: Open Device Manager (right-click Start > Device Manager). Expand categories like “Display adapters”, “Network adapters”, and “Storage controllers”. Right-click each device and choose Update driver > Search automatically.
• Roll back a recent driver: If the BSOD started after a driver update, go to the device’s Properties > Driver tab and click Roll Back Driver.
• Remove and reinstall: For stubborn drivers, uninstall the device (check “Delete the driver software for this device”), then restart and let Windows reinstall it.

Pay special attention to GPU drivers (NVIDIA, AMD, Intel) and any third-party antivirus or virtualization software, which often inject code into the kernel.

Fix 3: Test and Replace RAM

Faulty RAM is a classic cause of ntoskrnl.exe crashes. Windows has a built-in memory test:

1. Type “Windows Memory Diagnostic” in the Start menu and open it.
2. Choose Restart now and check for problems.
3. Let the test run (takes 20-30 minutes). It will restart automatically and show results.

If errors are found, try reseating the RAM sticks (remove and reinsert them) and test each stick individually in different slots. If the errors follow a specific stick, replace it. Also check if XMP/EXPO memory overclocking is enabled in BIOS – disable it to see if that stabilizes the system.

Fix 4: Check Disk for Errors

Bad sectors on the system drive can corrupt kernel data. Run a disk check:

1. Open Command Prompt as Administrator.
2. Type chkdsk C: /f /r and press Enter.
3. Type Y to schedule it on next restart, then restart your PC.

This will scan for file system errors and bad sectors. For SSDs, also update the firmware from the manufacturer’s website. If the drive is failing, back up immediately and replace it.

Fix 5: Disable Fast Startup and Check Overheating

Fast Startup can sometimes cause kernel issues because it saves a hibernation file that gets corrupted. Disable it:

1. Go to Control Panel > Power Options > Choose what the power buttons do.
2. Click Change settings that are currently unavailable.
3. Uncheck Turn on fast startup and save changes.

Overheating can also cause random kernel crashes. Use a temperature monitoring tool to check CPU/GPU temps under load. Clean dust from fans, ensure proper airflow, and if you overclock, revert to stock speeds.

Fix 6: Perform a System Restore or Reset

If none of the above works, try a System Restore to a point before the BSOD started:

1. Search “Create a restore point” and open the System Properties.
2. Click System Restore and choose a restore point.
3. Follow the wizard and restart.

If no restore points exist or the issue persists, consider a Reset this PC (Settings > System > Recovery > Reset PC). Choose “Keep my files” to preserve personal data, but note that installed apps will be removed. This reinstalls Windows and often eliminates kernel corruption.

Frequently Asked Questions

How do I read the BSOD error code to identify the cause?

When the BSOD appears, note the stop code (e.g., 0x0000000A or IRQL_NOT_LESS_OR_EQUAL). Search that code along with “ntoskrnl.exe” to find specific driver or hardware culprits. You can also use the Event Viewer (Windows Logs > System) and look for critical events with source “BugCheck” – the dump file path and timestamp help narrow down the cause.

Can ntoskrnl.exe BSOD be caused by a virus?

Yes, but it’s less common. Rootkits or malware that load kernel drivers can cause ntoskrnl.exe to crash. Run a full scan with Windows Defender (or a reputable third-party scanner) in Safe Mode. If you suspect a rootkit, use Microsoft’s offline Defender scan or a bootable rescue disk.

Do I need to reinstall Windows to fix this?

Usually not. Most ntoskrnl.exe BSODs are fixed by SFC/DISM, driver updates, or RAM replacement. Reinstalling Windows is a last resort, but it effectively resets all system files and drivers. If you have important data, back it up first.

Why does the BSOD only happen during gaming or heavy load?

Heavy load increases power draw and heat. This often points to an overheating GPU/CPU or an insufficient power supply. It can also expose unstable memory overclocks (XMP profiles). Monitor temperatures and stress-test components individually (e.g., Prime95 for CPU, MemTest86 for RAM) to isolate the fault.

Is it safe to delete ntoskrnl.exe if it’s corrupted?

No. Deleting ntoskrnl.exe will make Windows unbootable. The file is protected by Windows and cannot be deleted normally. Instead, use SFC or DISM to repair it, or boot from a Windows installation USB and use “Repair your computer” to fix the boot files.

What is a memory dump file and how do I use it?

When a BSOD occurs, Windows saves a memory dump file (e.g., C:\Windows\Minidump\*.dmp). You can analyze it with tools like WinDbg or BlueScreenView to see which driver caused the crash. This is the most precise way to pinpoint the culprit, but it requires some technical knowledge. If you’re not comfortable, share the dump file with a technician.

Related

• Instant Links in Arc Browser: How to Enable
• iOS 18 Autocorrect Not Working? Fixes That Help
• Fix Error 0x800713ab in Windows: 4 Working Methods