|
A few weeks ago, I had my system overlocked. I saved the bios settings as a preset. Last week I was troubleshooting my system, and went back to bios defaults to test if the overclock was to blame. My ssd was, so I replaced it and reinstalled windows. While doing this, I noticed that my SATA operation was set to IDE, so I set it to AHCI before the install. Yesterday I wanted to bring back my overclock, so I loaded the bios setting preset. And then Windows failed to boot. Tried repair, didn't work. Safe mode stops at classpnp.sys. Renamed that file as suggested in google searches, issue remains. Wait, this is a blue screen I'm having, what was the code? Oh god, 0x7B. I'm an idiot, I'm all too familiar with this thanks to my job as Dell technical support. (I've moved on to server support, so it had been a while since I've dealt with this and had forgotten.) The BIOS preset has the old IDE setting, that's why. But switching back to AHCI doesn't resolve the issue. I know from experience that sometimes just switching back doesn't fix the issue, it is like the Windows installation goes more permanently bad when you change the SATA operation and have a failed boot. Windows repair won't even work anymore. Anyone know a way to manually resolve this? I can't boot using safe mode, so most methods I'd know to try won't work. But surely a reinstall isn't my only option? Oh, this is Win 7.
|
#
?
Jul 9, 2014 20:13
|
|
|
|
| # ? May 11, 2024 05:49 |
|
|
Did you clear the CMOS and load the default BIOS settings?
|
|
#
?
Jul 9, 2014 20:18
|
|
|
Alereon posted:Did you clear the CMOS and load the default BIOS settings? Yes, doesn't help.
|
|
#
?
Jul 10, 2014 00:46
|
|
|
Please post your full system specs. You have no other drives connected, right?
|
|
#
?
Jul 10, 2014 02:06
|
|
|
Win 7 Ultimate 64 Gigabyte Intel board Intel 2500k CPU Boot disk is a Samsung 250GB SSD Two 2TB HDDs I've since disconnected the HDDs. Problem I've been having with the repair process is getting the recover console to recognize that there is a valid Windows installation. After trying a lot of things, (I believe setting the C partition as active in diskpart was the catalyst for this), I've now moved on to a missing BOOTMGR error, and this now occurs: If I have a BCD file in /boot, then the recovery console cannot attempt any kind of repair. Bootrec /scanos sees no Windows OS. If I delete that BCD file, then the recovery console can attempt an automatic repair. It says it needs to repair something and restart. It immediately restarts once I do this. But this brings me back to having a BCD file that doesn't function correctly. Or, when I have no BCD file, bootrec /scanos will see the Windows installation. I attempt bootrec /rebuildbcd. Now I'm back to having a BCD file that doesn't function. Whether I have a BCD file or not, I get the BOOTMGR is missing error. edit: oh my god I'm back up Umm, I think I fixed it by copying the bootmgr from the recovery partition to the main partition. I think. I mean, I did so much more, maybe that wasn't the only thing that needed to be done? Revol fucked around with this message at 04:10 on Jul 10, 2014 |
|
#
?
Jul 10, 2014 03:41
|
|