deleting bootcache to fix blue screen of death windows 10

Status
Not open for further replies.

morgann

Reputable
Nov 29, 2015
33
0
4,530
Ok guys I need your help. I'm getting the blue screen of death for Windows 10 and from what I read I need to delete the Bootcat.cache. How do I delete it? I have my windows 10 CD so I can use it to get into command prompt. But what do I do once in cmd prompt? Thanks!
 
Solution
vendors put on hidden partitions so they can put a hidden copy of windows on it.
there are also reserved partitions, different sizes are required for different versions of windows.

generally the hidden partitions will not have a drive letter assigend to them but when you plug in another drive windows detects the drive and will assign new drive letters to all the partitions that are not reserve partitions.

kind of a bummer, it can result in the OEM install partition becoming drive c: your USB thumb partition becoming drive d: and your actual windows install becoming drive E:

but your boot loader does not get changed and it tells the boot loader to go to drive c: to run winodws.
it is why you would have to run bootrec.exe command with...
So is this the error code: PROCESS1_INITIALIZATION_FAILED

This occurs because the Bootcat.cache file, located at %Systemroot%\system32\codeintegrity, is corrupted or because the size of the Bootcat.cache file is changed since the last successful start.

I think solution you are after is:


  • Boot from the DVD
    At the Install Windows screen, select Repair your computer or press
    At the System Recovery Options screen, select Command Prompt
    When Command Prompt appears, type the letter of the drive where your Windows 7 is installed:C:
    Replace C: with the letter of the drive where Windows 7 is installed, if C: is not your default installation drive. Press Enter
    Then type: cd windows\system32\codeintegrity
    Press Enter.Type: del bootcat.cache
    Press Enter
    Restart your computer

http://www.fixwindowsproblems.com/quick-fix-to-windows-error-code-0x0000006b/

the steps are for win 7 so the main difference is location of Command prompt in advanced startup, its now hiding in troubleshoot/advanced
 
I tried that. I did

cd %SystemRoot%
Enter
cd system32
Enter
cd codeintegrity
Enter

when I type in del bootcat.cache it says it cannot find it.

X:\windows\system32\codeintegrity>del bootcat.cache

Says cannot find it. I have no trouble until I try to enter delete. All the other commands worked till the del bootcat.cache.
 
Colif, I tried the sfc /scannow command and it came back verification 100% complete but says Windows Resource Protection could not perform the requested operation.
 
So everyone here's what I do. I turn on my computer and gives me the PROCESS1_INITIALIZATION_FAILED error. My computer restarts and tries to diagnose and repair. It then says "your pc did not start successfully".

I then click "advanced options". Then click "use a device". Then click use "Cd/DVD drive". Computer seems to restart then windows boot manager pops up. I click 64 bit which is what I installed. I pick language preferences and click next. Finally I click "repair your computer" and not the install now. I click troubleshoot then advanced options. Finally I select command prompt. This is correct right? Only way I know to get to command prompt. Am I doing it right
 
Johnbl ok I did that it seemed to work. I tried the command again and it said it can't find bootcat.cache so I guess it deleted it! I restarted computer and it's still giving me the error....now what : (
 
well, any problem with the disk subsystem can cause this error. for example if you change the SATA controller mode in BIOS, you could get this error. You could get this if you have upgraded a system that had special hard drive drivers.
you could get this error if you have a very old drive that is starting to fail.

you should describe the machine make and model.
if you can you could also provide the memory dump file it you can get to it.
it is at c:\windows\minidump directory.

deleting the bootcache just assumes that your files that will be installed were corrupted. You could have other corruptions or configuration problems that would have the same effect. for example, on older system when the battery backup on the motherboard fails the mode of the sata controller goes back to default and the drive no longer correctly maps file locations to the location on the drive correctly. normally if this is the case you will find that the system time and date are incorrect when you boot the system after the machine has been totally powered down. easy to fix, by changing the sata mode.



 
Johnbl so the make is one I built myself 4 months ago. It has a crucial 250 gb ssd. Msi titanium edition motherboard. Zotac 980 ti graphics. Windows 10. I have gotten this blue screen like 2 or 3 times randomly but restarting my computer fixed it. Now it just goes in the endless cycle or blue screen. Also how do I type that command in?
 
the system should just put them in the c:\system\minidump directory by default. You would just copy the files with a .dmp file extension up to a server like microsoft onedrive, then share the files for public access and then post a link.



 
How do I do that? I see a bunch of suggestions on diffetent sites but they require me to install software but I can't since all I can do is get into command prompt. I can't access my desktop
 
So I just decided to reinstall windows I didn't need any of the files so I deleted all the partitions on my ssd and installed Windows 10 again. That's prob best right? For some reason there was 4 partitions on my ssd but I deleted them all and did a fresh install
 
vendors put on hidden partitions so they can put a hidden copy of windows on it.
there are also reserved partitions, different sizes are required for different versions of windows.

generally the hidden partitions will not have a drive letter assigend to them but when you plug in another drive windows detects the drive and will assign new drive letters to all the partitions that are not reserve partitions.

kind of a bummer, it can result in the OEM install partition becoming drive c: your USB thumb partition becoming drive d: and your actual windows install becoming drive E:

but your boot loader does not get changed and it tells the boot loader to go to drive c: to run winodws.
it is why you would have to run bootrec.exe command with the /ScanOs flag.
it tells the system to look at your drives and find where your actual copy of window is located, then it modifies the boot up info on the reserved partition.

your process should work fine if you did not need your files.





 
Solution
Status
Not open for further replies.

TRENDING THREADS