Fix STATUS_PURGE_FAILED (0XC0000435) on Windows 10/11

A memory purge error that usually appears during shutdown or heavy multitasking. We'll walk through quick checks, then deeper fixes like driver updates and registry tweaks.

What is STATUS_PURGE_FAILED?

The error 0XC0000435 means Windows tried to clear (purge) data from memory and failed halfway through. You'll usually see it as a blue screen with the stop code STATUS_PURGE_FAILED, or as an event log entry during shutdown. It's not super common, but when it appears, it's often after a Windows update, a driver change, or when you're running memory-heavy applications like Chrome with 40 tabs plus a game.

Don't panic. Nine times out of ten, this is a driver or system file issue, not dead RAM. We'll go from easiest to most involved, so you can stop as soon as the error stops.

Fix 1: The 30-Second Check

Sometimes this error is a one-off glitch, especially after a sleep/wake cycle. Before you start changing anything, try this:

Press Ctrl + Shift + Esc to open the Task Manager.
Look at the Memory column under the Processes tab. Is it at 90% or higher?
If yes, close the biggest memory hogs by right-clicking them and selecting End task.
Restart your PC normally.

If the error doesn't come back after a few days, you're done. If it appears again, move on.

Fix 2: The 5-Minute Moderate Fix

Most persistent cases trace back to a corrupt driver or a system file. Let's knock those out.

Step 1: Run the System File Checker

Open Command Prompt as administrator (type "cmd" in the Start menu, right-click it, choose Run as administrator). Then run:

sfc /scannow

Let it finish. It takes about 5-10 minutes. If it finds errors and fixes them, restart your PC. After the restart, check if the error is gone. If it's still there, continue.

Step 2: Check for Pending Windows Updates

Microsoft frequently patches memory management bugs. So:

Go to Settings > Windows Update.
Click Check for updates.
Install anything that shows up, then restart.

If you're on Windows 11 22H2 or earlier, this error is more common. Updating to 23H2 often resolves it.

Step 3: Update Your Chipset and Graphics Drivers

Drivers that handle direct memory access are the usual culprits. Go to your motherboard manufacturer's site (Dell, HP, Lenovo, ASUS, etc.) and grab the latest chipset drivers. For graphics, use the vendor's tool:

NVIDIA: GeForce Experience
AMD: Adrenalin software
Intel: Intel Driver & Support Assistant

Install them, restart, and test. If the error vanishes, great. If not, we go deeper.

Fix 3: The Advanced Fix (15+ Minutes)

Step 1: Disable Fast Startup

Fast Startup is a hybrid shutdown that can mess with memory purging. Turn it off:

Open Control Panel, go to Power Options.
Click Choose what the power buttons do on the left.
Click Change settings that are currently unavailable.
Uncheck Turn on fast startup.
Click Save changes and reboot.

This is a common fix for 0XC0000435 on SSDs.

Step 2: Run CHKDSK to Rule Out Disk Issues

A failing disk can cause bizarre memory errors because Windows caches data from the disk. Open Command Prompt as admin and run:

chkdsk C: /f /r

It will ask to schedule a scan on the next restart. Type Y and reboot. Let it finish. It can take an hour on a large hard drive, but it's worth the time.

Step 3: Check for RAM Issues

While less common, faulty RAM does produce this error. Run the Windows Memory Diagnostic:

Press Win + R, type mdsched.exe, hit Enter.
Choose Restart now and check for problems.
Let it run its full cycle. After it finishes, Windows restarts and shows the results.

If it finds errors, your RAM is bad. Replace the stick or sticks—don't just ignore it.

Step 4: Registry Tweak for Memory Management

If you've made it this far and still get the error, you can adjust how Windows handles memory purging. This is a real fix that works for some, but be careful—wrong registry edits can break Windows. Use it as a last resort.

Press Win + R, type regedit, hit Enter.
Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Look for a DWORD called DisablePagingExecutive. If it doesn't exist, right-click on the right pane, choose New > DWORD (32-bit) Value and name it exactly that.
Set its value to 1.
Close Registry Editor and restart.

This forces the kernel to stay in memory and not be paged out. It can stop purge failures because there's less paging activity. Some report a slight performance gain, but it uses a bit more RAM. If it doesn't help, set it back to 0 and delete the DWORD.

When to Give Up and Reinstall

If you've done all of the above and the error still appears, it's likely a deeper corruption in Windows. Before you nuke everything, try a Repair Install (also called an in-place upgrade). Download the Windows 11 ISO from Microsoft, mount it, and run setup.exe. Choose Keep personal files and apps. This reinstalls Windows without wiping your data. It takes about 30 minutes and fixes nearly any system file corruption.

If that doesn't work, then a clean install is your last option. Back up your stuff and use the Reset feature in Settings > System > Recovery.

Why This Happens: Real-World Scenario

I've seen this most often on laptops that have been woken from sleep while running a memory-heavy app. The system tries to empty the standby memory, but a driver or the disk controller is still in a low-power state, so the purge stalls. That's why the driver and fast startup fixes are so effective. On a desktop, it's often after a Windows feature update that changed how the memory manager works with certain SSDs.

One more thing: don't install third-party "memory cleaners"—they cause more problems than they solve. Stick with the steps above and you'll get this sorted.