First, let me me say thanks so much for your detailed reply. I hope you had at least some of it available via copy/paste
I think we can mark this one as solved, but I'm still at a loss about wtf happened.
I'm hoping someone can hazard a guess.
- At some point over the last 3 days, both my PC and my buddy's PC got two repeated errors...
the bootmgr missing and rebooting during the "starting windows" screen. Mine also got the blue screens at the beginning. Which got which error and in which order is a blur, I've been hammering at this for hours and it's 4 am. The ram issue was just the usual... I was too timid with reseating it.
So here's where it gets weird:
- Your thoughts about the PSU were right, maybe. My buddy's PSU died today. Rather than get the multimeter like I should have, I decided to buy a new PSU to test everything.
- Buddy's drive, in his PC, but in a different building... got the reboot issue.
But the first time I booted it up with the brand new PSU, it was fine (in that building).
- But later that day in my house, it was not fine (reboot issue)
- Same hard drive, same new PSU, but plugged into my PC/mobo, was not fine (reboot issue)
- My hard drive in either PC, got bootmgr error, invalid partition table error, or disk boot failure.
So it's my house that's the problem right? But no, because buddy's PC with buddy's hard drive works fine in my house. Also my own is finally fine and currently running at my house (using it now).
So anyway, here's what I did to fix it, hopefully it helps someone else:
Since my DVD drive is broken, I tried to make a bootable copy of windows 7 on a USB stick. On both our PC's, it didn't work. So I happened to have a third PC to test with, one that's brand new. The BIOS on it is so nice. It recognized the make and model of my USB drive and booted win7 from it no problem. If people are having a problem with bootable USB installations despite doing the diskpart and bootsect stuff, they probably need an updated bios.
- Got into repair and it didn't see my windows installation. But via command prompt it saw my C:\ drive (sata) and I could navigate to it and to my windows folder no problem.
- Bootrec's various options didn't make it recognize the install. What seemed to fix this was not bootrec but the bootsect command. Went to C:\ from the command prompt, then ran bootsect /nt60 C:
and it was successful.
- Then, just to be sure, ran diskpart (using the shotgun approach to problemsolving) and set it to active by doing the usual steps:
diskpart
list disk
select disk 0 (in my case that's the C: drive)
list partition
clean
create partition primary
select partition 1 (in my case)
active
format fs=NTFS (or fat32. They say that ntfs is bad to put on a flash drive)
assign
exit
- I think now I could tell it was going to see my installation, and at this point I used bootrec (once again resorting to noob shotgun method). I did bootrec /fixmbr , then bootrec /fixboot , then bootrec /rebuildbcd
- On the next reboot it listed my windows installation on the C:\ drive and I chose to repair (no system restore). It completed, rebooted, and now windows is happy.
Sort of. It removed my validation even though I have a legit copy of windows7?! I need to fix that but first I need to sleep.