Repairing corrupted system files.

[LimitedWard]

Today my computer had a BSOD and could not recover with the code 0xc000000f. I tried fixing by using the system repair tools built into the installation media on my USB, but when attempting to refresh, the system gave me an error saying that the disk containing windows was locked.

I did a little more tinkering, and eventually the problem seemed to magically resolve itself. When Windows booted up properly again, I tried running the System File Checker through command prompt to check for corrupt files. Sure enough, it found some, but it was unable to fix them. Here's the log information on it:

2015-01-18 00:12:26, Info                  CSI    0000086e [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-01-18 00:12:26, Info                  CSI    00000870 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-01-18 00:12:26, Info                  CSI    00000871 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"

Does anyone know how I can fix this manually? What's surprising to me is that it mentions "PROCESSOR_ARCHITECTURE_AMD64," but I have an Intel CPU. Could have something to do with it? Also, is there anything else I should do to make sure this doesn't happen again?

 

[LimitedWard]

I solved my own problem by doing more research. If you ever encounter this problem, follow these steps:

1. open command prompt as administrator.
2. paste the following command and press enter:

DISM /Online /Cleanup-Image /RestoreHealth

3. wait for DISM.exe to finish working.
4. enjoy your fixed computer!

 

[Chicano]

Rebuild the BCD using bootrec.exe
https://neosmart.net/wiki/0xc000000f/

Why your PC shows Status: 0xc000000f. It’s difficult to determine the main cause of this error, but the most likely cause is a hard drive failure or a corrupted boot sector.

a) If you suspect your hard drive is the cause; run Hard Disk Sentinel to know it's condition...
b) And if you suspect it's the Bootloader (most likely) run the Startup Repair using the following repairs;
"Bootrec /FixMBR" followed by the "Bootrec /FixBoot" or "Bootrec /RebuildBCD"
c) I doubt the part where it mentions the "PROCESSOR_ARCHITECTURE_AMD64" has anything to do with the main issue. Those files may be corrupted but they are not being used.... so, it should make no difference whether you repair them or not.

Check the details.
Rebuild the BCD using bootrec.exe
https://neosmart.net/wiki/0xc000000f/

 

[LimitedWard]

Rebuild the BCD using bootrec.exe
https://neosmart.net/wiki/0xc000000f/

Why your PC shows Status: 0xc000000f. It’s difficult to determine the main cause of this error, but the most likely cause is a hard drive failure or a corrupted boot sector.

a) If you suspect your hard drive is the cause; run Hard Disk Sentinel to know it's condition...
b) And if you suspect it's the Bootloader (most likely) run the Startup Repair using the following repairs;
"Bootrec /FixMBR" followed by the "Bootrec /FixBoot" or "Bootrec /RebuildBCD"
c) I doubt the part where it mentions the "PROCESSOR_ARCHITECTURE_AMD64" has anything to do with the main issue. Those files may be corrupted but they are not being used.... so, it should make no difference whether you repair them or not.

Check the details.
Rebuild the BCD using bootrec.exe
https://neosmart.net/wiki/0xc000000f/

It appears to be working fine now. Should I still follow these steps anyways?

 

[Chicano]

If it's booting normally now, it probalby doesn't need any further fixing but applying that information doesn't hurt either.. so apply the steps or save them just in case it happens again.

 

[LimitedWard]

If it's booting normally now, it probalby doesn't need any further fixing but applying that information doesn't hurt either.. so apply the steps or save them just in case it happens again.

Okay I did the fix commands just in case. Thank you!