Quantcast
Channel: ASRock Forums
Viewing all articles
Browse latest Browse all 19545

Intel Motherboards : Asrock x99 fatality bios Broadwell E

$
0
0
Author: parsec
Subject: Asrock x99 fatality bios Broadwell E
Posted: 14 Jan 2017 at 11:51am

Originally posted by discotunax99 discotunax99 wrote:

Update!
I received an updated bios chip from the link I posted (took 10 days to ship to TN over the holiday weekend). It was easy to exchange with the extraction pliers and everything works now.
AsRock contacted me after their holiday break and offered to mail a bios chip. I received it within a week.

There are two snags I still have to work on.
1. Only the intel NIC works, the other one can't start.
2. Creative cinema 3 doesn't recognize my audio device, so no equalizer to fine tune klipsch 2.1 sound.

I'm pretty happy with the system. It boots in less than 15 seconds.

Cheers!


Your thread title just has Asrock x99 fatality in it, and no other mention of the mother board model. There are seven ASRock X99 boards that have Fatal1ty in their model name, so not sure which one you have.

I'm guessing the non-functioning network chip is the Qualcomm® Atheros® Killer??E2200 LAN chip?

Did you install its driver? No idea which version of Windows you are using, but the built in networking drivers in the Windows version you are using apparently cannot be used with that chip.

Have you checked the Device Manager entry for the E2200 LAN chip?

Virtually zero system details, not sure which X99 board you have, etc. So hard to provide help.

To answer your first post, yes your situation is common. Intel has not been able to work around the need to update the CPU microcode with a CPU of the previous generation in the board to do so. The only other method is changing the BIOS chip, as you did yourself. X99 is not the first Intel system that has this issue, and probably won't be the last.

Viewing all articles
Browse latest Browse all 19545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>