ErrorFix
Windows PC Errors

How to Fix BSOD DRIVER_CORRUPTED_EXPOOL (0x000000C5)

By ErrorFix · Updated October 27, 2026 · 8 min read

Error 0x000000C5Plain English: a driver damaged Windows own memory bookkeeping — like tearing pages out of a library ledger so later entries point at the wrong books. Rather than let that damage spread to other drivers and your files, Windows stopped the whole PC with a blue screen. The usual culprits are a buggy driver, faulty RAM, an unstable memory overclock, or a filter driver from an antivirus or VPN program.
Quick answer: 0x000000C5 means a driver corrupted the executive memory pool. Boot into Safe Mode, update or roll back the driver that changed most recently, test your RAM with Windows Memory Diagnostic, repair system files with DISM and SFC, and turn off any memory overclock. Work the steps in order — most cases resolve by step 4.

What error 0x000000C5 means

Windows manages kernel memory in pools, and the executive pool (ExPool) is the area where drivers and the Windows executive allocate blocks of memory for everyday work. Every allocation is tracked: pool headers record which driver owns each block, how large it is, and whether it is still in use. DRIVER_CORRUPTED_EXPOOL, stop code 0x000000C5, fires when a driver breaks those rules — freeing a block twice, using memory after it has been freed, writing past the end of a block, or damaging a pool header so the next allocation reads garbage.

The reason Windows halts instead of carrying on is that a corrupted pool is contagious. If one driver frees memory that another driver still owns, the second driver will later write into memory that now belongs to something else, and the damage spreads silently until files are corrupted or the system becomes unstable in ways that are far harder to diagnose. The blue screen is therefore a protective stop: it freezes the system at the exact moment the corruption is detected, before it can spread. That also means the fix is rarely about the pool itself. The pool is the victim, and the real job is finding the driver, the faulty RAM stick, the unstable overclock, or the filter program that corrupted it in the first place.

Common causes

How to fix error 0x000000C5 — step by step

Work through these fixes in order, from least invasive to most. Step 1 gets you into a state where everything else can run safely, steps 2–4 resolve the large majority of cases, and steps 5–6 cover the stubborn ones.

  1. Boot into Safe Mode and note what changed. DRIVER_CORRUPTED_EXPOOL usually appears right after a driver update, a new program install, or a hardware change, so think back to the last change before the first blue screen. From the login screen, hold Shift while clicking Power > Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart and press 4 for Safe Mode. If Windows only reaches the blue screen, force the recovery screen by interrupting the boot three times in a row, powering off while the Windows logo shows. Safe Mode loads only essential drivers, so if the crashes stop there, a third-party driver is the prime suspect.
  2. Update, roll back, or reinstall the suspect driver. Open Device Manager with Win + X > Device Manager, and look first at Display adapters, Network adapters, Storage controllers, and any device with a yellow warning icon. Right-click the suspect device, choose Update driver, then Search automatically for drivers. If the crashes started right after an update, right-click the same device, choose Properties > Driver > Roll Back Driver instead. A clean reinstall helps too: choose Uninstall device, restart the PC, and let Windows install a fresh copy of the driver.
  3. Test your RAM with Windows Memory Diagnostic. Search the Start menu for Windows Memory Diagnostic, choose Restart now and check for problems, and let it complete at least one full pass. DRIVER_CORRUPTED_EXPOOL is a memory-pool bug check, so a bad RAM stick is a strong suspect: corrupted pool headers in memory look exactly like a driver corrupting the pool. If the tool reports hardware errors, test your sticks one at a time and replace the faulty one before chasing drivers any further.
  4. Repair system files with DISM and SFC. In an elevated Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth first, then run sfc /scannow. On Windows 10 and Windows 11, DISM must run first because SFC pulls its repair sources from the component store that DISM fixes. Corrupted system files and a damaged driver store can make even a good driver behave badly, so this step rules out the operating system itself as the source of the pool corruption.
  5. Check the drive and turn off overclocking. Open Command Prompt as administrator and run chkdsk C: /f /r, then restart to let the scan complete. A damaged file system can corrupt driver files and pool data as they are read from disk, producing a DRIVER_CORRUPTED_EXPOOL crash that looks like a driver bug. Also return any overclock to stock: restart into your BIOS or UEFI, disable XMP or EXPO memory profiles and any CPU overclock, save, and test for a day. Unstable memory timings corrupt pool headers in exactly the way this bug check detects.
  6. Remove the culprit program and roll back with System Restore. If the crashes started after installing a new antivirus, VPN, disk tool, or driver utility, uninstall it from Settings > Apps > Installed apps and see if the crashes stop. You can also clean-boot to confirm: search for msconfig, go to the Services tab, check Hide all Microsoft services, click Disable all, then open the Startup tab in Task Manager and disable all startup items. If nothing else helps, boot into recovery, choose Troubleshoot > Advanced options > System Restore, and pick a restore point dated before the first blue screen. As a last resort, go to Settings > System > Recovery and use Reset this PC, choosing Keep my files.

Did this fix it? Quick checklist

If the blue screens continue after all six steps, check the minidump files for the faulting driver name: the crash dump usually names the driver that corrupted the pool, and that name points straight at the vendor to update or remove. Enabling Driver Verifier on suspect drivers can also catch the culprit, but use it carefully — it deliberately stresses drivers and can make an unstable system crash more often, so only enable it when you can still boot into Safe Mode to turn it off. Crashes that survive repaired files, tested RAM, stock memory timings, and rolled-back drivers point at hardware that is actively failing, so keep your backups current.

Frequently asked questions

What does DRIVER_CORRUPTED_EXPOOL (0x000000C5) mean?

It means a driver attempted to corrupt the executive pool: a driver tried to free memory that was already freed, accessed memory after freeing it, wrote past the end of a pool block, or damaged a pool header. Windows stops the whole system with the 0x000000C5 blue screen rather than letting the corrupted pool damage other drivers and data.

Is 0x000000C5 caused by a faulty driver or by faulty RAM?

It can be either, and the two look identical from the outside. A buggy, outdated, or corrupted driver is the most common cause, especially a graphics, network, storage, or antivirus filter driver updated just before the crashes began. Faulty RAM is the second most common cause, because corrupted pool headers in memory mimic a driver error. Update or roll back the suspect driver first, then run Windows Memory Diagnostic to rule out bad RAM.

Can antivirus or a VPN program cause DRIVER_CORRUPTED_EXPOOL?

Yes. Antivirus, VPN, firewall, and disk-utility programs install filter drivers that sit between Windows and the hardware, and a buggy or outdated filter driver can corrupt the executive pool and trigger 0x000000C5. If the crashes started after installing or updating one of these programs, uninstall it temporarily and test for a day or two. If the crashes stop, reinstall the latest version from the vendor or switch to a different program.

Will fixing 0x000000C5 delete my files?

No. Booting into Safe Mode, updating or rolling back drivers, testing RAM, running DISM, SFC, and chkdsk, turning off overclocking, uninstalling a program, clean-booting, and using System Restore all leave your personal files untouched. Only the last-resort Reset this PC or a clean Windows reinstall would touch your data, and the reset option lets you keep your files. Still, back up anything important first, because repeated blue screens can themselves corrupt files that are open at crash time.

Related fixes