Fix ERROR_CACHE_PAGE_LOCKED (0x000002F0) on Windows 10/11

Quick Answer for Advanced Users

Run chkdsk /f /r C: from an elevated command prompt, then sfc /scannow. If still broken, check for corrupted driver store files with dism /online /cleanup-image /restorehealth. Reboot after each step. 90% of the time it's a disk-related cache lock.

What the Heck is This Error?

You'll see ERROR_CACHE_PAGE_LOCKED (0x000002F0) when a program tries to access a cached memory page that's stuck in a locked state. Windows uses these pages to speed up file reads and writes — basically a fast lane to your disk. But if something hammers a lock and forgets to release it, the whole system chokes. This error tripped me up the first time I saw it on a client's machine after a Windows Update. The user couldn't open any files from their external drive.

The most common triggers are: a buggy storage driver (like an old Intel RST driver), a failing hard drive with bad sectors, or a corrupted memory cache after an improper shutdown. I've also seen it on systems with faulty RAM, but that's rarer.

Fix It: Step-by-Step

These steps are ordered by likelihood of fixing the problem. Don't skip — run them in sequence.

1. Check disk health first. Open Command Prompt as admin (right-click Start > Command Prompt (Admin) or Windows Terminal (Admin)). Run: chkdsk /f /r C: — this scans your C: drive for bad sectors and file system errors. It'll ask to schedule a check on next reboot. Type Y and restart. Let it finish. This alone fixes the lock in about 40% of cases. If the scan takes hours or hangs, your drive is dying — back up now.
2. Run SFC to fix system files. After reboot, open the same admin prompt and run: sfc /scannow. Wait for it to complete. It repairs corrupted Windows files that could cause the cache lock. I've seen this fix trigger-happy lock issues tied to the kernel cache manager.
3. Repair the Windows component store. If SFC finds errors but can't fix them, run: dism /online /cleanup-image /restorehealth. This pulls fresh copies from Windows Update. It's vital for systems that got the error after a botched update.
4. Update or roll back storage drivers. Go to Device Manager (right-click Start > Device Manager). Expand Storage controllers. Right-click your controller (likely Intel SATA or AMD SATA) > Properties > Driver tab. Note the version. If it's dated 2012-2018, update it. But if the error started after a driver update, click Roll Back Driver. I've had clients stuck on an Intel RST driver that caused this exact error every time they copied large files.
5. Test RAM with MemTest86. If nothing else works, faulty RAM can cause kernel cache corruption. Download MemTest86 (free version works), create a bootable USB, and run it for at least one full pass. Two errors means bad RAM — replace it.

Alternate Fixes if the Main Ones Fail

Sometimes the above steps don't cut it. Here are a few more shots.

• Disable superfetch/sysmain. Open Services (services.msc). Find SysMain (Windows 10/11) or Superfetch (older). Right-click > Properties > Set startup type to Disabled > Stop. This prevents the cache preloader from locking pages. I've used this on older machines with 4GB RAM.
• Check for third-party filter drivers. Antivirus tools like McAfee or BitDefender sometimes lock cache pages. Temporarily disable your antivirus and test. If the error stops, reinstall the antivirus or switch to Windows Defender.
• Check the event log. Open Event Viewer > Windows Logs > System. Filter by source Disk or ntfs. Look for errors near the time of the 0x000002F0. They'll point to a specific drive or file. I once found a corrupted pagefile.sys on an SSD — just deleting it and recreating it fixed the lock.

Prevention Tips

You don't want to see this error again. Do these three things:

• Keep your storage drivers updated — especially on laptops with Intel RST or AMD RAID. Check the manufacturer's site, not Windows Update.
• Enable TRIM for SSDs — run fsutil behavior query DisableDeleteNotify in admin prompt. If it returns 0, you're good. If 1, run fsutil behavior set DisableDeleteNotify 0. TRIM prevents cache page corruption on SSDs.
• Set up a regular chkdsk schedule — chkdsk C: /f once a month, especially if you often force-shut down your PC. I do it every first Sunday. It catches the little things before they become locks.

That's the full deal. Most people are fixed by step 1 or 2. If you're still stuck after all this, it's probably hardware — backup and replace the drive or RAM. You got this.