Fatal1ty X99X Killer BIOS update from 1.10 to 1.50

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

   Specs:
Fatal1ty x99x killer
i7 5820K
Crucial 4 x 8gb 2133 (tried to upgrade to G.Skill 4x16GB AEGIS 2400)
850 EVO 500GB x 2

Updated my BIOS since it didn't read the new RAM. Installed the old RAM back in and updated it via the BIOS files form the ASROCK website and updated to 1.40 from 1.1 without an issue. When I went to update to 1.50 the system wouldn't POST. I emailed tech support and they asked me to try to switch from A to B on the BIOS switch. Did that and cleared CMOS and now I get Debug code 99 which when I looked up the FAQ it meant that the videocard has issues. 
I tried a different video card the 6850 and it gave me error code d6 which is VGA not recognized. 

My problem is that it was working fine until the update to 1.50. Any ideas on how to get it back?!?!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
nyichiban Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 11 May 2016 Location: NYC Status: Offline Points: 5	Post Options Post Reply Quote nyichiban Report Post Thanks(0) Quote Reply Topic: Fatal1ty X99X Killer BIOS update from 1.10 to 1.50 Posted: 11 May 2016 at 12:14pm
	Specs: Fatal1ty x99x killer i7 5820K Crucial 4 x 8gb 2133 (tried to upgrade to G.Skill 4x16GB AEGIS 2400) 850 EVO 500GB x 2 Updated my BIOS since it didn't read the new RAM. Installed the old RAM back in and updated it via the BIOS files form the ASROCK website and updated to 1.40 from 1.1 without an issue. When I went to update to 1.50 the system wouldn't POST. I emailed tech support and they asked me to try to switch from A to B on the BIOS switch. Did that and cleared CMOS and now I get Debug code 99 which when I looked up the FAQ it meant that the videocard has issues. I tried a different video card the 6850 and it gave me error code d6 which is VGA not recognized. My problem is that it was working fine until the update to 1.50. Any ideas on how to get it back?!?!