![]() |
P67 Extreme4 Not Booting After BIOS Update |
Post Reply ![]() |
Page <1 23456> |
Author | ||
IronRinn ![]() Newbie ![]() Joined: 13 Aug 2015 Status: Offline Points: 9 |
![]() ![]() ![]() ![]() ![]() |
|
I swear I tried this and it was still a no go, but I'll give it another shot on 3.21a. |
||
![]() |
||
Xaltar ![]() Moderator Group ![]() ![]() Joined: 16 May 2015 Location: Europe Status: Offline Points: 23963 |
![]() ![]() ![]() ![]() ![]() |
|
Thanks for posting back with your fix MikeyJ. I am sure someone will find it useful
![]() |
||
![]() |
||
MikeyJ ![]() Newbie ![]() Joined: 16 Aug 2015 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
|
OK, so I solved this and I'm very upset with myself because I should have known better!
Go into your BIOS. Go to Advanced. Go to Storage Configuration. Make sure "SATA Mode Selection" is set to "AHCI". Go down to "Marvell SATA3 Operation Mode" and make sure it's set to "AHCI Mode". Exit and save changes. These had changed back to their default settings as IDE on the BIOS update. These were the only changes I made as far as I can remember and it booted right into Win10. If this doesn't work for you, the only thing I can think is that you may need to be on the beta 3.21a BIOS that I tried as a Hail Mary when nothing else was working. Good Luck! Mike PS - Yes, it fixes the 100% CPU issue! |
||
![]() |
||
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
|
So the 3.10 BIOS version did not work with Windows 10? Don't forget there are driver updates that are needed with that BIOS updates, the Intel IME software being the most basic one. But if the PC won't boot, how can you update a driver, right?
I really don't know which version would be better with Windows 10. I would assume a later version would be the better bet, so 2.10 is what I would choose. Sorry about your experience with support, I guess if they are out of ideas they stop responding. |
||
![]() |
||
tallshortguy ![]() Newbie ![]() Joined: 12 Aug 2015 Status: Offline Points: 6 |
![]() ![]() ![]() ![]() ![]() |
|
Was waiting for my new BIOS chip before posting updates. I got a 3.1 chip to make sure it wasn't a corrupt BIOS issue and it isn't. The vendor (not Asrock) offered to reflash any version I want. Parsec would you recommend 1.6 or 2.1? It seems that Ivy Bridge support is the issue. Thanks for the help, you've been much more helpful than Asrock support who stopped responding to my questions.
Edited by tallshortguy - 20 Aug 2015 at 7:38am |
||
![]() |
||
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
|
Frankly, I don't think any mother board manufacture was aware of all the issues that Win 10 would cause. Please try to understand and remember that every time a new version of Windows is released, that issues like these appear. When Win 8 was first released, Microsoft had a web page where they asked users to post their experiences with drivers that worked and did not work with it! ![]() Consider that when we think about whom is responsible for getting a new version of Windows working correctly across many differing hardware platforms. ![]() The Sandy Bridge to Ivy Bridge compatibility BIOS update must be done carefully by itself, but add another variable to that such as a new release of Windows at the same time... is it really surprising if the combination of the two did not work? I'm sorry guys, I simply want you all to keep these things in mind. Add to all this the release of the Skylake platform and all the new boards, and last minute UEFI/BIOS and driver updates which also must work with Windows 10... you can imagine how busy the mother board manufactures are at this time. The phrase "Perfect Storm" comes to mind. ![]() |
||
![]() |
||
MikeyJ ![]() Newbie ![]() Joined: 16 Aug 2015 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
|
I'm running an i7 2600 Sandy Bridge.
|
||
![]() |
||
IronRinn ![]() Newbie ![]() Joined: 13 Aug 2015 Status: Offline Points: 9 |
![]() ![]() ![]() ![]() ![]() |
|
I tried updating to 3.21A as well, just to see if it would by chance happen to boot up but yeah, no go. What processor are you running? Edited by IronRinn - 18 Aug 2015 at 12:48am |
||
![]() |
||
MikeyJ ![]() Newbie ![]() Joined: 16 Aug 2015 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
|
Hi All,
I too got sucked into this issue trying to solve the 100% CPU issue with Win 10. Sort of luckily for me I had a dual boot Win 7 set up so I was able to get back in using my Win 7 OS. Still doesn't fix my Win 10 no boot issue tho. :( I'm very surprised ASRock was not more clear on the fact that 3.10 was not compatible with Win 10 right on the support page. Just for reference, I've tried the 3.21A beta BIOS from a link found further up in the comments and it does not solve the problem. Here's to hoping they create an update to fix this! |
||
![]() |
||
IronRinn ![]() Newbie ![]() Joined: 13 Aug 2015 Status: Offline Points: 9 |
![]() ![]() ![]() ![]() ![]() |
|
Thanks, parsec! Seems my hunch was right and I had 1.60. Now I just have to mail them a check or money order (Really? No PayPal? Not even credit cards?) and wait for the new chip, I guess. I hope they get this stuff straightened out at some point.
|
||
![]() |
Post Reply ![]() |
Page <1 23456> |
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |