Hi all,
Here's my situation. I have seen many thread about people having problems with win 8/8.1 and AHCI, and haven't seen an actual working fix for them. In my situation, I have a system that I originally installed for someone, as a fresh, complete W8.1 OEM, 32 bit, clean install - originally set up using BiOS set to AHCI. Working fine for a few months. User had the bios battery go bad (date, time, etc), so they went into cmos and set date and time - left everything else as default - whereby the bios defaulted to Native IDE for the HD. System booted and they worked on it that day - and brought the system to me. I replaced the cmos battery and reconfigured the system HD to AHCI.
That's when it all went to the South pole. The infamous 'There was a problem starting' error, the attempted diagnosis and startup repair by windows, and eventually completely stuck in that loop. I have seen way too many "change the storahci to 0" responses, and did attempt that - no joy. I have a problem with that anyhow - simply because I have seen MANY working systems where all of those settings were the same - some number other than 0 - and they boot just fine. Seems to me that there is something else that gets changed or reset, thus this thread.
I also attempted the "bcedit /set ... recoveryenabled No" suggestion - and no joy there either.
I'd like to see if someone can get to the bottom of what actually gets changed or reset when these things go bad - so an actual fix can be documented. I have twice had this loop happen when accepting an AMD sata driver update from windows update (dated early part of 2013) with similar resulting no boot results.
Anyone finding or have the inside on this? Sure would be nice to have something solid to work with, as I am not a rookie tech, and work on a lot of systems, and this is becoming a real issue.
Here's my situation. I have seen many thread about people having problems with win 8/8.1 and AHCI, and haven't seen an actual working fix for them. In my situation, I have a system that I originally installed for someone, as a fresh, complete W8.1 OEM, 32 bit, clean install - originally set up using BiOS set to AHCI. Working fine for a few months. User had the bios battery go bad (date, time, etc), so they went into cmos and set date and time - left everything else as default - whereby the bios defaulted to Native IDE for the HD. System booted and they worked on it that day - and brought the system to me. I replaced the cmos battery and reconfigured the system HD to AHCI.
That's when it all went to the South pole. The infamous 'There was a problem starting' error, the attempted diagnosis and startup repair by windows, and eventually completely stuck in that loop. I have seen way too many "change the storahci to 0" responses, and did attempt that - no joy. I have a problem with that anyhow - simply because I have seen MANY working systems where all of those settings were the same - some number other than 0 - and they boot just fine. Seems to me that there is something else that gets changed or reset, thus this thread.
I also attempted the "bcedit /set ... recoveryenabled No" suggestion - and no joy there either.
I'd like to see if someone can get to the bottom of what actually gets changed or reset when these things go bad - so an actual fix can be documented. I have twice had this loop happen when accepting an AMD sata driver update from windows update (dated early part of 2013) with similar resulting no boot results.
Anyone finding or have the inside on this? Sure would be nice to have something solid to work with, as I am not a rookie tech, and work on a lot of systems, and this is becoming a real issue.
My Computer
System One
-
- OS
- Win 8.1
- Computer type
- PC/Desktop
- System Manufacturer/Model
- AMD
- CPU
- X4 840
- Motherboard
- Biostar
- Memory
- 4GB
- Graphics Card(s)
- GT220 Nvidia
- Browser
- IE11, FF30.0
- Antivirus
- Defender, Malwarebytes