Fix UNEXPECTED_KERNEL_MODE_TRAP on Windows 11

UNEXPECTED_KERNEL_MODE_TRAP is Windows telling you the CPU caught the kernel red-handed doing something impossible. The processor raised an exception — a “trap” — that the kernel had no way to handle, so the system stopped. It’s a serious-sounding error, but the causes are the usual suspects: bad drivers, bad RAM, unstable overclocks, or heat.

The trap code in the crash dump narrows it down, but you don’t need to be a kernel debugger to fix this. Work the list below from most likely to least, and you’ll find it.

Why this happens

• Buggy or corrupted driver. A driver executing an invalid instruction or touching memory it shouldn’t is the top software cause.
• Failing RAM. Bad memory cells corrupt kernel code or data, and the CPU traps when it tries to execute the garbage.
• Unstable CPU or RAM overclock. XMP/EXPO profiles and manual overclocks that pass light use but fail under sustained load.
• Overheating CPU or chipset. Thermal instability causes transient execution errors that surface as traps.
• Corrupted system files. Damaged kernel components or driver binaries producing illegal instructions.
• Failing motherboard or CPU. Rare, but voltage-regulation or silicon degradation produces traps no software fix touches.
• Dust-clogged cooling. The slow-burn cause: gradually rising temperatures until the system crosses the instability threshold.
• Failing power delivery. A worn battery or failing charger causing voltage droops under load can destabilize the CPU exactly when it boosts, producing traps that vanish on AC power with a healthy adapter.

How to fix it

Work through these in order, starting with the quick software checks.

Fix 1: Disable overclocks and XMP/EXPO

If anything is overclocked, this is step one — no exceptions.

1. Enter the BIOS/UEFI at boot (F2, Del, or Esc).
2. Disable XMP/EXPO memory profiles and any CPU overclock or undervolt. Set everything to Auto/defaults.
3. Save and exit, then stress the laptop the way that used to crash it.
4. If crashes stop, your overclock was never fully stable. You can try a milder profile later, but stock speeds are the safe baseline.

Fix 2: Test the RAM

Kernel traps love bad memory.

1. Press Win + R, type mdsched.exe, and press Enter.
2. Choose Restart now and check for problems, press F1 on the test screen, and run Extended mode with at least 2 passes.
3. For a definitive answer, run MemTest86 overnight. Any error means replacing the faulty stick.
4. If your laptop has two sticks, test them individually to isolate the bad one.

Fix 3: Update or roll back drivers

Focus on the drivers most likely to execute in kernel mode.

1. Open Device Manager (Win + X) and update drivers for display adapters, network adapters, and storage controllers.
2. Get chipset drivers from your laptop manufacturer’s support site rather than Windows Update.
3. If crashes started after a specific driver update, roll it back: Properties > Driver > Roll Back Driver.
4. Pay special attention to antivirus and VPN filter drivers — update them or temporarily uninstall to test.

Fix 4: Check temperatures and clean cooling

Heat-induced traps follow a pattern: fine at idle, crash under load.

1. Install HWiNFO and log CPU package temperature during the workload that crashes.
2. Sustained temperatures above 95°C on most laptop CPUs indicate a cooling problem.
3. Blow dust from vents and fans with compressed air. Check that all fans actually spin under load.
4. On older laptops, dried thermal paste is the likely culprit — a repaste by a competent shop restores headroom.

Fix 5: Repair system files

Rule out corrupted kernel components.

1. Open Terminal (Admin) and run sfc /scannow.
2. Follow with DISM /Online /Cleanup-Image /RestoreHealth.
3. Restart and retest under the same workload. If SFC repeatedly finds new corruption, suspect the SSD — healthy drives don’t corrupt system files twice.

Fix 6: Run the crash dump through analysis

Let the dump tell you which driver to blame.

1. Confirm dumps are enabled: Advanced system settings > Startup and Recovery > Settings, with Small memory dump selected.
2. After the next crash, open the .dmp file from %SystemRoot%\Minidump in WinDbg Preview (free from the Microsoft Store).
3. Run !analyze -v and note MODULE_NAME and the trap code (parameter 1).
4. Update, roll back, or remove the named driver. If no driver is named and the trap is a double fault, hardware is the likelier story — see Microsoft’s bugcheck reference for deeper interpretation.

Fix 7: Test with a clean boot

Isolate whether a third-party driver or service is involved.

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 test. If crashes stop, re-enable services in halves until the culprit returns.

Fix 8: Check the disk and consider hardware service

The last software-adjacent checks before calling it hardware.

1. Run chkdsk C: /f /r in an elevated prompt and let it complete at boot.
2. Check SSD health with the manufacturer’s utility.
3. If RAM tests clean, temperatures are fine, and dumps name no driver, you’re likely looking at motherboard or CPU-level failure — document your test results and contact support or a repair shop.

For update-triggered variants of this crash, see our unexpected kernel mode trap after Windows 11 update guide, and for the Dell-specific angle, the kernel mode trap on Dell walkthrough covers brand quirks.

Closing

UNEXPECTED_KERNEL_MODE_TRAP looks like deep kernel magic, but the fix is almost always gloriously mundane: a bad overclock, a tired RAM stick, a dusty heatsink, or a driver that needs updating. Work the list methodically and the trap stops springing. If crashes only happen on battery, test with the charger connected — weak power delivery mimics every other cause on this list.

Frequently asked questions