New
#1
Drive Corruption 0xc000000f on Win Boot Manager 2nd time
One of my machines, for some reason, keeps corrupting the boot drive.
Custom built Intel i3-3245, 8 gigs memory, 250Gb HDD, EVGA 950Ti, Win7 64 bit. This machine has been up since 2013. I added an Samsung EVO 850 to it Sept 2016 and it's been working ok with an occasional BSOD (can't recall the code, but it was pointing at a hardware problem), but otherwise been great. Last weekend, it BSOD'ed and upon reboot got the Windows Boot Manager with a 0xc000000f an error occurred while trying to read the boot manager. I switched back to the old 250GB hdd in the system and it booted back up ok. So I got the Win7 disc out, and went through with bootrec /fixboot and /fixmbr, did chkdsk on boot, it tried to fix permissions issues galore across 500k+ files, etc. I got it all the way to at least find the disc again at the right size, and the files were back, but the registry was also corrupted, so I finally gave up, and did a re-install and got everything back up and working again. Sunday, the drive corrupted yet again. Same boot message again. System again sees it as a 0MB drive. System wants to chkdsk again. So something keeps corrupting a LOT of the drive. But again, I can boot back to my old 250GB drive.
I looked at it with Samsung Magician. SMART data shows good. It finds the drive perfectly fine, and I can run benchmarks against it.
So only thing I can think of this is is the drive is bad, the SATA cable is bad or the SATA controller on the motherboard is bad. I also suppose a voltage spike to the drive could be corrupting it as well. The PSU is a CoolMax CR550B which is likely around 10 years old. Voltages in UEFI show slightly above voltage on 12, 5 and 3.3v lines so that looked fine at least. But it is old. It could also explain the occasional BSOD's as well.
Thoughts?
Devon