X99m Killer - cannot boot with bios >2.1

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Since yesterday morning I can not longer boot windows 10 or ubuntu on my system.
Ubuntu stop and get black screen, windows power off when loading and restart.

I have now spent quite a bit of time to narrow down the problem.

I can boot normally (any OS) with bios 2.1.
With 3.0 or 3.1 problem occur (thank you for dual bios switch!!!)

It took me a while to think of downgrade bios to rule out problem and in my quest to get there I:
* replaced cpu with another so not cpu problem
* replaced 4x memory with other modules and also tried single slot, memory test etc so not memory problem
* replaced and even tried with no disk at all (even win10 installer dies) so not disk problem
* replaced psu with another so not psu problem
* Cmos reset as described in other posts, (no power, no battery, bios reset jumper for 20+ minutes)

Motherboard: Fata1ty x99m Killer
CPU: XEON 2690-v3 (and also tried a 2695-v3)
Memory: 4x SK hynix 8Gb DDR4 (HMA41GR7MFR8N)
Disk is Samsung 950 and a bunch of Samsung 850s

So I can actually use the system right now but I am restricted to old bios.

What is next course of action, RMA?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Dirtylobster Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 May 2016 Status: Offline Points: 8	Post Options Post Reply Quote Dirtylobster Report Post Thanks(0) Quote Reply Topic: X99m Killer - cannot boot with bios >2.1 Posted: 28 May 2016 at 4:19pm
	Since yesterday morning I can not longer boot windows 10 or ubuntu on my system. Ubuntu stop and get black screen, windows power off when loading and restart. I have now spent quite a bit of time to narrow down the problem. I can boot normally (any OS) with bios 2.1. With 3.0 or 3.1 problem occur (thank you for dual bios switch!!!) It took me a while to think of downgrade bios to rule out problem and in my quest to get there I: * replaced cpu with another so not cpu problem * replaced 4x memory with other modules and also tried single slot, memory test etc so not memory problem * replaced and even tried with no disk at all (even win10 installer dies) so not disk problem * replaced psu with another so not psu problem * Cmos reset as described in other posts, (no power, no battery, bios reset jumper for 20+ minutes) Motherboard: Fata1ty x99m Killer CPU: XEON 2690-v3 (and also tried a 2695-v3) Memory: 4x SK hynix 8Gb DDR4 (HMA41GR7MFR8N) Disk is Samsung 950 and a bunch of Samsung 850s So I can actually use the system right now but I am restricted to old bios. What is next course of action, RMA?

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Online Points: 25103	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 4:27pm
	No, no need for an RMA. So far as we have seen BIOS versions 3.00 and above do not work correctly with Haswell CPUs. There has been some speculation as to what the reason is but at present I would not recommend using 3.0 or higher on X99 platforms unless you are using a v4 (Broadwell) CPU. 2.XX should be considered the latest (stable) BIOS for Haswell based systems, so far as I can tell there are no additional features in 3.XX other than Broadwell support. I hope this helps.


Dirtylobster Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 May 2016 Status: Offline Points: 8	Post Options Post Reply Quote Dirtylobster Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 4:29pm
	It does. But its super strange, I have used it for 2 months and then yesterday it started to act up. I was 100% sure it was hardware until I replaced every single bit except the actual motherboard :) Thanks for quick reply.

Dirtylobster Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 May 2016 Status: Offline Points: 8	Post Options Post Reply Quote Dirtylobster Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 4:32pm
	oh and please share any bios setting that might be worth shutting down incase that would help remedy the problem. I am happy to test.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Online Points: 25103	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 4:34pm
	Wait, you are saying you had the system running fine on 3.0/3.1 and it suddenly stopped working? If so, did you update any drivers or Intel Management Engine between the system working as intended and not? That would not effect Ubuntu though.... What were the symptoms exactly? The OS (win/ubuntu) begins to load then halts? Edited by Xaltar - 28 May 2016 at 4:40pm


Dirtylobster Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 May 2016 Status: Offline Points: 8	Post Options Post Reply Quote Dirtylobster Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 4:50pm
	That is correct, it was working great. The only thing that was installed yesterday was silverlight for a webpage and then hell started. I would suspect the OS but since it wont even start a reinstall properly even without disks I am pretty sure it is not the cause. Also Ubuntu would start. I simply cannot explain it, everything is peachy on 2.1 but 3.0 and 3.1 refuse to start anything now...

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Online Points: 25103	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 4:56pm
	So Ubuntu was loading but windows failed and refused to reinstall? Or both OSes failed to boot? That is very odd. I would run some stress tests on the system (intel burn in test, Prime95, memtest) and make sure you get no errors with 2.10. When using 3.X you are able to enter the UEFI? In all honesty, I would contact Tech Support directly and inform them of your problem. They can advise you if you need to take any additional steps. I am just a Moderator and do not speak for ASRock nor do I have access to all the technical details about what has changed between the different BIOS revisions. Bare in mind however that Computex will be starting soon so they may take a while to get back to you. Edited by Xaltar - 28 May 2016 at 4:57pm


Dirtylobster Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 May 2016 Status: Offline Points: 8	Post Options Post Reply Quote Dirtylobster Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 5:00pm
	Ubuntu load the first bit where I just click "try without installing" then it stops on >3.0+ Windows also get stuck. If memory or cpu would be root cause then the replacement units would have solved it. I can enter bios with all versions without any problems, its only the actual loading of OS that get stuck (ubuntu stop, windows restarts) With 2.1 I can do anything with any OS without problem. I fully understand and I will check with Tech support to see what they recommend.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Online Points: 25103	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 28 May 2016 at 5:24pm
	Good luck to you, hopefully there is a simple explanation for the problem.


Dirtylobster Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 May 2016 Status: Offline Points: 8	Post Options Post Reply Quote Dirtylobster Report Post Thanks(0) Quote Reply Posted: 29 May 2016 at 2:17pm
	Today I thought I was going to have a brain aneurysm because the system would not boot windows on 2.1 or 1.6 bios even. (Before you read any longer, it is not connected to the issue above) It would seem a X99M motherboard cannot boot win10 if a ps4 (or 360?) controller is attached. I put my ps4 controller on charging through my monitor yesterday and forgot about it. http://www.overclock.net/t/1582820/asrock-x99-apparently-doesnt-like-booting-with-a-controller-plugged-in-anyone-else Board is going into the shop tomorrow.