SFCFIX : Some corruptions could not be fixed automatically

Hi Peter!

Unfortunately things have taken a turn for the worse. The disk started showing signs last week of failing entirely (as you had warned me last year it was starting to do). So i bought a SSD replacement drive (Crucial MX500 1TB). And planned to clone the failing drive to this one. In the mean time the 'old' drive stopped loading into Windows and so i used the Windows 8.1 repair disk i have, and was running check disk as the standard repair was failing to work. However, after running check disk it was telling me that there wasn't enough space on the disk to repair the problem files (it did seemingly repair quite a few), equally the System Restore points wouldn't work either. At certain points in the past few days the disk itself stopped appearing on the PC at all (wouldn't appear in BIOS or when within Windows Repair and it didn't sound like it was working at all) i gave it a bit of a shake and it came back to life but still wouldn't load into Windows.

So i installed the same OS (8.1) on the new SSD and installed the cloning software (Minitool Partition Wizard) and from the new SSD and using the cloning software i've been able to clone the old drive to the new SSD (removing the new OS i had installed on the SSD). But it's still failing to load into Windows (using the SSD) due to the same Windows Boot Manager error (which was stopping the old drive from loading).

file: \windows\system32\ntoskrn1.exe
status: 0xc0000098
Info: The operating system couldn't be loaded because a critical system driver is missing or contains errors.


Check disk now comes back 100% clean and i've tried to reset the boot records but still no use, SFC is finding corruptions that it cannot fix (i'm having to run it /offline as i cannot get into Windows itself, only through Windows Repair, command line), and the Windows Repair is still failing to resolve the problem itself. It did say it's created a CBS error file but being i'm having to do things through the Windows Repair i'm not sure how i could access it to attach here.

I have a Windows 10 installation CD ready that i want to upgrade the SSD to (from Windows 8.1) but i want it to upgrade and not overwrite (as i want all the files and programs i've been using). With the apparent problems with boot manager, would this be possible to just upgrade or is it likely to fail because of the corruptions/missing files?

Any suggestions would be much appreciated.
 
Cloning a corrupted drive onto a new drive does not fix corruptions. A broken file or file-structure will not be a valid file on the new drive.

\windows\system32\ntoskrn1.exe
Click to expand...
Are you sure the filename ends with 1 ?. I would expect its an L .
Check if the filename it at the given location.

Note: This is maybe beyond repair and you need to start from scratch.
 
I knew it would not work by simply cloning it but the old drive was giving me real concern that it could stop working entirely at any time and from what i read on various forums it was suggested to transfer (or clone if you want to try and save the OS/user accounts) to a fresh fully working disk and attempt to fix the problems from there. The old disk was/is seemingly becoming more corrupted every few days and so i decided to get it cloned and try to fix it from a new disk that isn't going to potential 'die' or stop being readable.

I can access the data through the Windows Repair disk from it's 'Microsoft Diagnostics Recovery and Tools Set'. It was indeed an 'L', it was the way it appeared to me on the error. I have searched and the file itself is there, in the system32 folder.

Would it be possible to just try and 'upgrade' from Windows 8.1 to 10 or is that likely to fail due to the missing/erroneous file-structure?
 
Would it be possible to just try and 'upgrade' from Windows 8.1 to 10 or is that likely to fail due to the missing/erroneous file-structure?
Click to expand...
I don't think it will work but you give it a try.

Since this is not a Windows Update issue I suggest to create a new thread here: BSOD Crashes, Kernel Debugging
Put a link to this thread in your initial post.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top