How to Fix CACHE_MANAGER BSOD in Windows?
When users encounter the Blue Screen of Death (BSOD) with the stop code ‘CACHE_MANAGER’ in Windows, it indicates a critical issue with the cache manager, which manages cached data in memory to optimize file access and improve overall system performance.
This error suggests Windows encountered a problem reading or writing cached data, which may lead to system instability, crashes, and BSODs. Common causes include memory corruption, faulty disk sectors, outdated or incompatible drivers, or conflicts between hardware and software.
The CACHE_MANAGER error is more likely to occur on systems under heavy load, such as those running intensive applications or handling large amounts of data.
This article provides solutions to resolve the CACHE_MANAGER error.
1. Run SFC, DISM, and CHKDSK
Corrupted system files or disk issues may cause this error. The System File Checker (SFC), Deployment Image Servicing and Management (DISM), and CHKDSK commands can repair these problems.
- Press Windows + S to open the Search menu, type cmd, and run Command Prompt as an Administrator.
- Type the following commands:
sfc /scannow Dism /Online /Cleanup-Image /RestoreHealth chkdsk C: /f
- Restart your computer after the scans complete.
2. Run Memory Diagnostic Tool
Faulty memory is a common cause of this error and can lead to system crashes and data corruption. The built-in Windows Memory Diagnostic Tool can detect memory-related issues, such as faulty RAM modules.
- Press Windows + S and type Windows Memory Diagnostic.
- Click Open to run the tool.
- Select “Restart now and check for problems (recommended)”. Note: Save all your work, as your PC will restart.
- Wait for the diagnostic to complete and follow any on-screen instructions.
For more advanced testing, you can use the PassMark MemTest86 program. Learn more in our article here.
3. Replace the CMOS Battery
A weak or dead CMOS battery can cause issues like incorrect system time, boot errors, and BSODs. The CMOS battery powers the BIOS firmware that stores important settings like the system clock and hardware configuration.
Replacing the CMOS battery may resolve these issues. Read our detailed article on CMOS batteries here.
4. Rename AODDriver2.sys to AODDriver2.old (for AMD users)
AODDriver2.sys is a driver associated with AMD OverDrive, a utility for overclocking AMD processors and GPUs. If this driver becomes corrupted, outdated, or incompatible with newer Windows versions, it can cause BSODs.
Renaming the file prevents Windows from loading it, which can stop the BSODs. However, this will disable AMD OverDrive functionality, so it’s recommended for users who no longer need overclocking or are experiencing issues related to this driver.
- Boot into Advanced Startup.
- Select Troubleshoot.
- Select Advanced options.
- Choose Command Prompt and follow the on-screen instructions.
- Type the following commands:
cd C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\
ren AODDriver2.sys AODdriver2.old
- Restart Windows.
6. Clean Install Windows
If none of the previous solutions work, reinstalling Windows may fix the issue. This process installs a fresh copy of Windows and removes any problematic files or software.
- Download the Media Installation Tool from Microsoft’s official website here.
- Connect a USB drive to your PC.
- Click “Create Installation Media“.
- Select the Language, Architecture, and Edition of Windows.
- Choose the “Use recommended settings” option or customize it, then click Next.
- Select the ISO option and click Next.
- Choose a location to save the ISO file.
- Once downloaded, open Rufus and download the software.
- Run Rufus and select your USB device.
- Set the Partition scheme to GPT and Target system to UEFI.
- Select the ISO file and click Start.
- Once finished, restart your PC and boot from the USB using the F12 key (or another boot key for your motherboard).
- Follow the on-screen instructions to install Windows.
If none of the solutions work, the issue may be hardware-related. Faulty components like RAM, motherboards, or CPUs often cause BSODs. Inspect your system’s hardware and replace any faulty parts. If unsure, visit a technician, as some parts are sensitive to handling.