ASRock New BIOS Updates For Speculated System Vulnerability - Reboot Issue Identified
ASRock was just informed by Intel that they disclosed the reboot issue on the former microcode released earlier. To fix the security vulnerability (SA-00088), ASRock will keep working closely with Intel to develop and update new BIOS for our 8/9/100/200/Z370/X99/X299 motherboard series.
ASRock is aware that the current Intel microcode version might be defected by security vulnerabilities. We recommend users update their systems by flashing the latest BIOS once the revision microcode is released from Intel. To mitigate this issue promptly and constructively, please refer to below links for more info.
To mitigate this issue promptly and constructively, we will keep our customers posted on our official website, please refer to : http://www.asrock.com/Microsite/SA00088/
Latest BIOS Update :
X299
|
|||||
Z170
|
|||||
H170
|
|||||
Q170
|
|||||
B150
|
|||||
C232
|
|||||
H110
|
|||||
Z370
|
|||||
Z270
|
|||||
H270
|
|||||
B250
|
|||||
Senior Member
Posts: 1117
Joined: 2011-01-11
Here is a guy commited to updating some older ROG boards with all the latest bios goodies: https://rog.asus.com/forum/showthread.php?48001-R4E-BIOS-4804-MODDED-EFI-Intel-13-1-0-2126-Download
I’m thinking about updating my RIVE soon but maybe I’ll wait for Intel to sort out some of their issues first.
I think the 3930K has a microcode update while the 3960X does not.
Right on...! And thank you I will have to check this stuff out. Was hoping to get the NVMe update, but with my added usb 3.0 to C adapter it is already taking pci-e lanes from my GPU's. Adding in a NVMe card would most likely drop me down even further from my 16/8/8/4 as it was 16/8/8/8 before that added USB shtuff....
Senior Member
Posts: 11358
Joined: 2003-05-24
Eh i cant say the same thing, that was first and last evga board I will ever buy, that thing had endless issue with ram disappear, No Bios ever fixed rma of board fixed, and 8+ ram set i tried never fixed, one one set ever worked right at correct speeds, with out randomly lossing ram. and the set that worked was RMA'ed set i got back from manfacture none 4 sets before that or after that ever worked right., and from what read back then X58 systems were notorious for this.
but on topic I think the only way this issue with microcode should be delt with is, All the cpu manufactors make the need microcode, and then FORCE the OS makers to push the updates threw there updates, that is only way every will get protected.