Upgrade path leading to NO BOOT after new MB and CPU

mikelmykel

Honorable
Sep 22, 2012
13
0
10,510
Previously had F2A85-V-Pro with A10-5800k, decided on new build to Sabertooth 990FX R2.0 with FX8350.

After turning on went to BIOS to check/verify for all drives are listed, latest BIOS is 2104, did not change anything, F10 save and continue..AND... No Boot,

Monitor shows "The system found unauthorized changes to the firmware, OS, or UEFI drivers"

Press [N] for next boot device blah blah blah,...nothing happens

Tried to boot from DVD with repair disk=nope
Hummmm.....need to re-install OS?
 
did you have any custom settings on the bios like raids? I would also just switch your bios to the 2nd bios if you have one to see if it fixes anything, but do not update it if it works. Instead use this time to download flashes for your other bios to try to do a proper flash
 


No custom raids, tried to flash older bios, "image out dated", and even the one previous to current..flashed backed to current...did read about doing a sysprep method. AND... also read that windows doesn't like when you change mobo's or HW..must do a clean re-install..ehhh..that's my last resort. if u got any other trick(s) would be liked😀
 
Yeah if you swapped the motherboard for a new one (which normally means a new chip set) windows normally will require you to do a clean install of windows. This is just something that windows does to help prevent the reuse of oem versions on windows. windows sets installs things that make it so when you boot up your computer into windows it looks for the old chip set if it is unable to find it what will happen is it may boot the first couple of times but after that it will blue screen when you try to load windows. then even sometimes it may even make the os undetectable. There is a lot more to it but I guess if you wanted a more in depth answer about why or how windows does that I would just google search it. But when I upgraded from my 1155 motherboard to my 2011 socket motherboard with a different chip set I had to do the same thing. So a re-install after a good back up would be your best bet.
 
Yup, .Agreed....looks that way, tried the other two ways, not even close, thanks for the advice..will restart run and install..
 


Agreed..will restart install run..