• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

ASRock Releases BIOS Update to Fix Intel "Skylake" Bug

btarunr

Editor & Senior Moderator
Staff member
Joined
Oct 9, 2007
Messages
47,670 (7.43/day)
Location
Dublin, Ireland
System Name RBMK-1000
Processor AMD Ryzen 7 5700G
Motherboard Gigabyte B550 AORUS Elite V2
Cooling DeepCool Gammax L240 V2
Memory 2x 16GB DDR4-3200
Video Card(s) Galax RTX 4070 Ti EX
Storage Samsung 990 1TB
Display(s) BenQ 1440p 60 Hz 27-inch
Case Corsair Carbide 100R
Audio Device(s) ASUS SupremeFX S1220A
Power Supply Cooler Master MWE Gold 650W
Mouse ASUS ROG Strix Impact
Keyboard Gamdias Hermes E2
Software Windows 11 Pro
Earlier, Intel confirmed that its Skylake processors were plagued by a bug which causes the system to freeze or act abnormally when executing complex workloads, such as the stress test benchmark Prime95. While the majority of computer users might not use Prime95 at all, or never had the urge to stress their system to the point of discovering this Intel Skylake bug, still ASRock has already released BIOS updates for fixing this flaw on all of their Intel 100 Series motherboards. So, on the bright side, after a quick ASRock BIOS update you will never notice or remember Intel's small hiccup.



View at TechPowerUp Main Site
 
What about H.264 encoded using AVX ? Are Skylakes prone to acting "abnormally" in those conditions as well? Because video encoding is nothing special compared to synthetic torture of Prime95?
 
What about H.264 encoded using AVX ? Are Skylakes prone to acting "abnormally" in those conditions as well? Because video encoding is nothing special compared to synthetic torture of Prime95?

Afaik the error is specific to prime numbers not heavy AVX workloads per se.
 
Afaik the error is specific to prime numbers not heavy AVX workloads per se.

It is an AVX bug. To get it to happen you have to mod Prime95 to get it to use AVX, otherwise Prime95 works just fine. I believe the bug is caused by heavy AVX load on the CPU.

I just hope this patch doesn't hinder AVX performance, and kill BCLK overclocking...
 
I'm asking that because I know many people got super stable overclocks in all torture programs, but same system got unstable when encoding longer H.264 videos using AVX extension.
 
Nice, flash done.
 
AWESOME!!!!

Not that I've had any problems with my baby, but it's good to know ASRock did their homework and found a fix for it.
 
AWESOME!!!!

Not that I've had any problems with my baby, but it's good to know ASRock did their homework and found a fix for it.

Thats a microcode update, so asrock has nothing to do with it.
 
I hope this microcode update is not going to partially disable AVX for certain workloads.

The famous TSX bug in Haswell was sorted out by disabling it through microcode update. So I hope it doesn't repeat with this (disabling a feature != fixing a bug in my book).
 
Thats a microcode update, so asrock has nothing to do with it.
Indeed. And the microcode in question has been out since october last year. This is a case of ALL mobo vendors NOT doing their homework.
 
I hope this microcode update is not going to partially disable AVX for certain workloads.

The famous TSX bug in Haswell was sorted out by disabling it through microcode update. So I hope it doesn't repeat with this (disabling a feature != fixing a bug in my book).

Wasn't TSX bug also present on Skylakes, making that extension useless and afaik they even disabled it?
 
Wasn't TSX bug also present on Skylakes, making that extension useless and afaik they even disabled it?

I thought I heard it had been fixed in Haswell-EP/EX and Broadwell onwards. Maybe there has been another update to the matter which I'm not aware of.
 
Wasn't TSX bug also present on Skylakes, making that extension useless and afaik they even disabled it?

No. It is an on-silicon bug in Haswell/Haswell-E only.
 
I'm pretty certain Skylake was mentioned before as well. It's pretty lame they can't fix this stuff in 3 major CPU revisions...
 
I'm pretty certain Skylake was mentioned before as well. It's pretty lame they can't fix this stuff in 3 major CPU revisions...
hardware bugs are not something you can fix in one day.
 
hardware bugs are not something you can fix in one day.

Haswell-K (and neither the Haswell-E) wasn't exactly released "few days ago"...
 
Haswell-K (and neither the Haswell-E) wasn't exactly released "few days ago"...

Well, i willing to bet that skylake design was well underway when haswell was released. CPU micro architectures are not exactly made overnight.
 
anyone know if there is a change in BLCK adjusting for non-K processors?
 
Does it retain your previous settings or do I have to take care of them myself?

TIA

I don't remember off the top of my head if can do a complete Save All but on the OC Tweaker tab there is an option to save your CPU/Mem settings to disk. Would be nice if I was on Z170 with a K CPU but since my system is H170 with an i5-6600 I really only have 1 setting to change after a BIOS update - fan profile set to Silent from Standard - and I'm done.
 
  • Like
Reactions: bug
Well, i willing to bet that skylake design was well underway when haswell was released. CPU micro architectures are not exactly made overnight.

Still, I highly doubt that it was so far they couldn't fix it before 3rd iteration was released?
 
Back
Top