


Startup repair reportedly made things much worse, but doing a system restore to a previous restore point made things functional again. That's easier said than done, as Chacos had to mash the power button on fifteen different boots before they actually managed to get it recovering. That should encourage an automatic recovery event, which in turn allows you to select from some advanced options to sort out your system. The workaround, which arose from a painstaking back and forth with AMD engineers, is to hit the power switch on your PC in the split second in between the BIOS keypress options screen and the spinning Windows logo appearing. AMD workaround: Uncheck the Factory Reset box on installation of the new drivers or, if your system has corrupted, spam the power switch on bootup to force an automatic recovery event.

