I can't blame the motherboard 100% but it is unlikely it failed at the same time could be the other way too, drive failed and broke the motherboard.who knows. Sorry for the rant, just not too happy with the bios issues.Ĭlick to expand.Yes it's dead basically the controller, nand flash should be fine though. Pay $350 for a motherboard that lets you disable hardwire ethernet but not wireless ethernet, gigabyte needs to employee some people who don't eat spaghetti with a spork. That and the fact I can't disable bluetooth or wifi in bios (security vulnerability and plain moronic), but I can disable ethernet lan. I get its a new platform and all but posting a bios on main page that has a wide variety of results on consumers and enthusiasts systems is to me nothing less than a hackjob. For anyone who suggests to flash it and find out, I'd rather keep 30 settings unchanged then have to do everything over just to find out if gigabyte got this bios right. So I am just curious if for those who did have any issues on F20, if F21 resolved them. On a clean flash, with resetting cmos before and after flashing, I noticed the F20 bios had a setting that would try to save even when nothing was touched, thats how I know for me something was off on that bios but it seems other people had different experiences. Has F21 resolved those issues? For me I could not boot into windows with default settings, it would get the windows screen then instantly reboot. Question for the Aorus Master owners who had issues on F20.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |