In today’s post, we will identify the cause and then provide the resolution to the issue Bug Check 0x34 – CACHE_MANAGER blue screen (BSOD) on Windows 11/10. A fatal system error, also known as a system crash, stop error, kernel error, or bug check, occurs when an operating system halts because it has reached a condition where it can no longer operate safely.
CACHE MANAGER Blue Screen
The full error message reads thus;
The CACHE_MANAGER bug check has a value of 0x00000034. This indicates that a problem occurred in the file system’s cache manager.
For a better understanding, below is the CACHE_MANAGER Parameters:
| Parameter | Description |
|---|---|
| 1 | Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the “0x”) identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred. |
| 2 | Reserved |
| 3 | Reserved |
| 4 | Reserved |
According to Microsoft, the one possible cause of this bug check is the depletion of nonpaged pool memory.
The memory manager creates the following memory pools that the system uses to allocate memory: nonpaged pool and paged pool. Both memory pools are located in the region of the address space that is reserved for the system and mapped into the virtual address space of each process. The nonpaged pool is kernel memory which can’t be paged out into the pagefile when Windows runs out of free physical memory. It is used by drivers to allocate memory which they need.
If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Add new physical memory to the computer
To resolve a nonpaged pool memory depletion problem, add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.
There are a few other things you could try to resolve the issue:
- Run the online Windows Blue Screen Troubleshooter from Microsoft
- Run Memory Diagnostic Tool
- Run Hardware Troubleshooter.
If you cannot log in to your Windows computer, boot into Advanced Startup Options and open an elevated command prompt window. The process is explained there in detail. Once at that screen, select Troubleshoot > Advanced options > Command Prompt. Using the CMD, you can access the more advanced built-in Windows tools easily.
If you wish to directly access these Advanced startup options when working on your Windows 10, you can do so via the Settings app of Windows 10 > Update & Security > Recovery > Advanced startup and click the Restart now button.
All the best.
