[Full Guide] How to Fix ntoskrnl.exe BSOD Random Crashes – Causes, Solutions, and Hidden Tricks

Blue digital graphic with large bold text: ‘FIX ntoskrnl.exe BSOD’ on a simple blue background with subtle diagonal lines.

Have you been dealing with random Blue Screen of Death (BSOD) crashes that mention ntoskrnl.exe?

Or does it happen sometimes when Google Chrome or Firefox refuses to open?

If so, you’re not alone. This type of BSOD is one of the most frustrating because it seems completely random, and no simple error message tells you what’s really causing the problem.

In this guide, I’ll explain what’s happening behind the scenes, go over common causes, provide step-by-step solutions, and even share some hidden tricks that helped many users finally fix their systems—without spending money.

What is ntoskrnl.exe?

The file ntoskrnl.exe stands for Windows NT Operating System Kernel. It’s one of the core components of Windows responsible for:

  • Memory management
  • Hardware interaction
  • Process control
  • Overall system stability

When you see “ntoskrnl.exe” mentioned in a BSOD, it doesn’t necessarily mean the file itself is corrupted. Instead, it usually means that something else triggered a critical failure, and the kernel (ntoskrnl.exe) couldn’t recover.

In short:

ntoskrnl.exe is the victim, not the criminal.

Common Causes of ntoskrnl.exe BSOD

There’s no single cause. Many different problems can trigger this error. Here’s a summary table:

CategorySpecific CauseExplanation
Memory (RAM)Faulty RAM, unstable XMP settingsEven if MemTest passes, borderline issues may exist
StorageFailing SSD/HDD sectorsCauses read errors that crash system calls
Graphics DriversOutdated or corrupted NVIDIA/AMD driversOften triggered during gaming or video playback
Power SupplyLow-quality PSU or voltage fluctuationsSudden power drops during high load
Security SoftwareConflicts or kernel interferenceAntivirus may trigger unexpected kernel behavior
Windows UpdatesBuggy patches or driver conflictsNew updates may destabilize older drivers
BIOS/UEFI SettingsOverclocking instability, outdated BIOSCan trigger timing issues at kernel level
Software ConflictsBackground apps interferingSome poorly coded apps destabilize system processes

Your Case (Based on Real User Example)

  • Crashes happen while gaming
  • Sometimes Google Chrome or Firefox won’t open
  • MemTest shows no memory errors

Highly suspected areas:

  • Graphics drivers
  • Storage stability
  • Power supply behavior under load
  • Potential Windows kernel corruption

Step-by-Step Solutions

Let’s move through a logical sequence, from simplest to more advanced.

Run System File Checker and DISM (Essential First Step)

Corrupted system files can cause the kernel to behave unpredictably.

Steps:

  1. Open Command Prompt as Administrator
  2. Type the following:
sfc /scannow

Let it complete (may take several minutes).

  1. Then type:
DISM /Online /Cleanup-Image /RestoreHealth

Why this works:

If any core system files were altered or damaged, these commands can automatically repair them.

Fully Reinstall Graphics Drivers Using DDU

Graphics drivers are often responsible for ntoskrnl.exe BSODs, especially during gaming.

Steps:

  1. Download Display Driver Uninstaller (DDU) – a free tool that completely removes existing drivers.
  2. Boot into Safe Mode.
  3. Run DDU and remove your current graphics driver.
  4. Reboot.
  5. Download the latest official NVIDIA driver for your RTX 2060 directly from NVIDIA’s website and reinstall it.

Why this works:

Simply updating drivers sometimes leaves old files behind. A clean uninstall using DDU eliminates any leftover corrupted driver files.

Check Your SSD or HDD Health

Even minor drive problems can cause kernel failures.

Steps:

  • Open This PC > Right-click your drive > Properties > Tools > Check for errors
  • For SSDs, use the manufacturer’s diagnostic tool (Samsung Magician, Crucial Storage Executive, etc.)

Tip:

Sometimes failing NAND cells cause random read/write failures that crash the system unpredictably.

Monitor Your Power Supply (PSU)

When gaming or under load, your PSU might not deliver stable voltage.

Simple test:

  • Use free software like HWMonitor to observe voltages while gaming.
  • Watch for voltage drops under the 12V, 5V, and 3.3V rails.

Hidden trick:

If your PSU is borderline insufficient, random BSODs can occur without any other signs.

Update BIOS and Chipset Drivers

Especially with AMD Ryzen builds, an outdated BIOS can cause kernel instability.

Steps:

  • Visit your motherboard manufacturer’s website.
  • Download the latest BIOS update.
  • Also download and install the latest AMD chipset drivers.

Note:

Many Ryzen instability issues have been resolved in BIOS updates that improve memory timing and stability.

Perform a Clean Boot (Software Conflict Test)

Third-party apps or services may interfere with Windows kernel operations.

Steps:

  1. Press Win + R, type msconfig, press Enter.
  2. Go to the Services tab.
  3. Check “Hide all Microsoft services”, then click Disable All.
  4. Restart your PC and test if the BSOD still happens.

If crashes stop:

You likely have a background app causing the conflict.

Hidden Tricks and Insider Tips

These are extra methods that have surprisingly worked for many users struggling with this issue for months:

Turn Off XMP / Memory Overclock

Even stable-looking XMP profiles can cause kernel crashes.

  • Try disabling XMP (Extreme Memory Profile) in BIOS.
  • Run your RAM at JEDEC standard settings temporarily to test.

Why?

Marginal memory instability can pass MemTest but still crash under specific real-world loads.

Disable Hardware-Accelerated GPU Scheduling (HAGS)

In some systems, HAGS causes crashes:

  1. Go to Settings > System > Display > Graphics > Change Default Graphics Settings
  2. Turn Hardware-accelerated GPU scheduling OFF.

Re-seat RAM and GPU

Physical connection issues are sometimes overlooked:

  • Power off your PC completely.
  • Gently remove and reinsert your RAM modules and GPU.

Loose contacts can cause rare but very frustrating crashes.

Replace SATA or Power Cables

Sometimes faulty cables cause intermittent errors that software checks can’t detect. Simply swapping them has resolved BSODs for some users.

Consider Repair Installation of Windows (In-Place Upgrade)

If nothing works, but you want to avoid a full reinstall:

  • Download the Windows 10/11 installation media tool.
  • Choose Upgrade this PC now.
  • This will reinstall Windows while keeping your files and apps intact.

This refreshes core system files and resolves hidden corruption.

Summary Table

Here’s a quick reference:

Suspected CauseSolution
Corrupted System FilesSFC /scannow + DISM
Graphics Driver IssuesUse DDU + Clean Install Latest Driver
Storage FailuresDisk Error Check + SSD Health Tools
Power Supply ProblemsMonitor Voltages + Consider PSU Test
BIOS InstabilityUpdate BIOS + Chipset Drivers
Background App ConflictsClean Boot Test
RAM Stability IssuesDisable XMP + Re-seat Modules
Last ResortRepair Install of Windows

The ntoskrnl.exe BSOD is challenging because it’s a symptom of many possible root causes. But with patience, methodical testing, and some of these lesser-known tricks, you can usually fix it without replacing expensive hardware.

If even one of these steps brings your system back to stability, you’ll be glad you found this guide. Don’t give up!

✔️You might also find these helpful:

▶︎【Windows 11/10対応】Chrome Won’t Launch and Remains “Paused” — Causes and Fixes

▶︎KB5039302 Windows 11 Update Error – Symptoms, Causes, and Real Fixes

▶︎June 2025 Windows 11 Update Errors – Complete Guide for Troubleshooting