3 different BSOD's then 0x80070570

ConfusedAF

Reputable
Jul 27, 2014
2
0
4,510
I woke up this morning to a BSOD, the screen changed too fast to see the exact BSOD but I remember the last digits in the serial were "0040" and after some research found it was most likely a memory problem.

However when I tried to boot memtest, I would get the BSOD almost instantly. So after some more research, I removed all of the memory I had installed except one and the computer booted no problem.

I looked up how to test memory without mem test and went the old fashioned way of adding one and rebooting until it BSOD's again, then I know the bad one. Well I found the bad one. Kept it out. Rebooted. Different BSOD. Flashed so quick that all I caught was "WINDOWS_CRI...".

searched around until I found that removing the mem stick apparently messed up my OS? I have never heard of that but I learn new stuff all the time so I decided to try to repair using the normal repair feature. I ran windows repair and it gave me an error saying it couldn't be repaired. I researched the error and found I have to repair from windows disk. So I tried and that failed too.

After the attempt to repair using windows disk, now when I launched it told me windows was unable to load and it kicked me right to the normal windows repair screen. So I decided to just clean install, the computer is fairly new so I figured I wouldn't lose anything worth while, as it is just a streaming computer anyways.

During the clean install process I got the "Error 0x80070570" message, did some research, and tried manually formatting the drive from scratch(using shift+f10 and doing it through the command prompt). Got the exact same error.

Now I have been looking online for about 4 hours and everyone is saying to replace the hard drive on other peoples problem requests. Is this going to be the only resolution? Could my HDD be faulty now because of removing a stick of ram, safely, and trying to repair windows?

I'll post system specs if necessary but i feel like in this specefic case, it shouldn't be. I could be and am most likely wrong.

Any help is appreciated.
 
Solution
0x80070570 = the file or directory is corrupted

lots of potential causes for this:
I would start by a direct inspection of the BIOS settings for the mode that your SAT controller is set to.
sometimes when you pull out hardware, the BIOS gets messed up or the BIOS is reset to defaults. if this occurs you want to make sure the mode that the sata controller has not changed (IDE mode or ACHI) you might want to check it is set correctly (or try the other setting and reboot to see if the disk is recognized as formatted)
When the mode of the sata drive changes, it tells the controller to read the data from the drive using a different method
if it is not set the same as when the drive was installed the data will be read incorrectly and you...
0x80070570 = the file or directory is corrupted

lots of potential causes for this:
I would start by a direct inspection of the BIOS settings for the mode that your SAT controller is set to.
sometimes when you pull out hardware, the BIOS gets messed up or the BIOS is reset to defaults. if this occurs you want to make sure the mode that the sata controller has not changed (IDE mode or ACHI) you might want to check it is set correctly (or try the other setting and reboot to see if the disk is recognized as formatted)
When the mode of the sata drive changes, it tells the controller to read the data from the drive using a different method
if it is not set the same as when the drive was installed the data will be read incorrectly and you will get the error message indicating the disk is corrupted.

- virus/malware can corrupt the disk
- repeated bugchecks with pending disk IO can cause the filesystem to become corrupted (chkdsk /f /r to repair)
(but you have to boot off another disk image and run the chkdsk on the drive)
- some SSD will lag on the trim and Garbage collection routines this may cause a just formated drive to not respond correctly. Often, just leave the system booted into the BIOS with power to the drive for a few hours will allow the drive to run these routines and cleanup its internal resources.

-also, there are cases where a replacement of a RAM module will require a complete reinstall but it should be rare.
(more likely just one of the above cases or a registry corruption)
 
Solution