Windows 10: blue screen stop code CASHE_MANAGER

So I have setup a new RAID volume in Linux and after that I can’t boot in to windows 11 pro. Windows is not installed on that volume and nothing has been changed beside I have created the volym. The blue screen appears before I can boot into windows and I get the CHACHE_MANAGER stop code. I have 64gb ddr5 memory so I am confident that I have enough even for windows I have tried different memory profiles in bios as well. I can without problem boot into Linux Fedora KDE plasma and run some memtest, nothing is wrong. This is always the case, In fedora everything works, it is stable, never a probl

:)

 

Stop code blue screen sdbus

Hello,

Stop errors (also sometimes called blue screen or black screen errors) can occur if a serious problem causes your device to shut down or restart unexpectedly. These errors
can be caused by both hardware and software issues.

For us to better assist you, we'd like to know the following:

Confirm which build is currently installed on your device. To check, follow the steps below:

• Press Windows key + R, then type in winver.
• Click OK.

• Were there any recent changes made prior to this issue?
• What actions were you performing when normally encounter the said error?

Meanwhile, we recommend performing the suggested steps in this article to
troubleshoot blue screen error on Windows 10.

We'll be waiting for your response.

 

Blue Screen

Hi,





Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
would like to know more about the issue. Please clarify the following:

• Did you get a STOP code?
• Did you install any hardware or driver recently?

For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
article and simply follow the steps.



Feel free to contact us if you need further help.

 

Blue screen and stop code

Hi
Jeferis,

There are a lot of factors for this matter to occur. To isolate the issue, we have some questions for you:

• 
  What activity have you done to
  trigger the NTFS and FAT FILE SYS loop?
  
• 
  were there any error messages?
  
• 
  What troubleshooting steps have you done so far?
  

It is possible that the
Boot
Sequence were corrupted by the previous activity which
triggered the Blue Screen Error and the loop. We recommend that you perform these
suggested troubleshooting
and see if there are any changes:

Startup Repair.


To access the
Startup Repair Screen, turn off the
PC 3-4 times(force shutdown),
while on the Blue screen Error. This will route you to the
Startup repair screen:

Advanced Boot Options > click Troubleshoot > Advanced options > Command Prompt

and run the following command:

Run SFC Scan:  

SFC
will
scan
and
run
an
automatic repair
to any
corrupted system files
that it will detect. We suggest that you perform it twice. To run an
SFC scan, follow these steps:  

• 
  Run
  Command Prompt as Administrator.  
  
• 
  Type
  sfc /scannow
  and hit
  Enter.   
  

Boot Record:

This will fix the corruptions on
boot records or boot
sequence. To run this command, follow these steps:

• 
  Run
  Command Prompt as Administrator.
  
• 
  Type the following command:  
  
  • 
    Bootrec /fixMBR  
    
  • 
    Bootrec /fixBoot
    
  • 
    Bootrec /rebuildBCD
    

Update us on how it goes.

Regards.