only affects those who stress-testing it to ensure OCed speeds are stable. Other than that, regular, day-to-day use shouldn't have such problems.

How much you want to bet this microcode "fix" breaks BCLK OCing?

Just a thought... I for one have never had Prime95 freeze, and I always stress test with it.

EDIT: Though it does appear to be reproducible doing a highly specific test, interesting. Still, I am leaving the above as food for thought...

as per the thread quoted by btarunr, it only affects after running a certain type of benchmarking test. Not sure which one though...

Tsukiyomi91as per the thread quoted by btarunr, it only affects after running a certain type of benchmarking test. Not sure which one though...

Yeah, I was able to freeze my system fairly quickly using the Prime95 instructions, so it's real.

Here's the other thing though: It STILL would not surprise me if they break BCLK ocing that's become popular while they fix this...

That's a really, really specific number to cause a freeze (like winning the lottery to find that). I'll grab the BIOS update ASAP just to be safe.

Edit: No BIOS updates since December. I'm sure that doesn't contain a fix...

Tsukiyomi91only affects those who stress-testing it to ensure OCed speeds are stable. Other than that, regular, day-to-day use shouldn't have such problems.

That didn't stop people from crucifying AMD and that bug was so rare it was insane.

Hmm.. Just bought an i5-6500, I only do 3D Mark benching, I don't think my processor will run into these freezing problems with that.
If it would, I just update the BIOS then.

Quote from PCWorld article "How to test your PC for the Skylake bug" by Gordon Mah Ung

Inb4 microcode removes non-K OC.

MadsMagnusInb4 microcode removes non-K OC.

:D You're late then. Post #3: www.techpowerup.com/forums/threads/intel-core-skylake-processors-freeze-under-certain-workloads-company-issues-fix.219167/#post-3400407

rtwjunkie:D You're late then. Post #3: www.techpowerup.com/forums/threads/intel-core-skylake-processors-freeze-under-certain-workloads-company-issues-fix.219167/#post-3400407

:banghead:

so they are sure that this major hardware cockup can be fixed in microcode? for all cases and not just this fft avx subroutine implementation? or can we expect multiple "fixes" from here on out for other "might freeze" scenarios?

if this can really be fixed with microcode only, microsoft probably already has a new version of mcupdate_genuineintel.dll available in windows update, *nix users might have to wait for a bios updates (if they ever come)

Now I feel much better for going with the older Haswell-E instead. I don't want "unpredictable behavior" under stress. Mostly because encoding H.264 video on all cores gives me pretty similar stress conditions as torture stability testing tools. So, the situation is pretty real.

RejZoRNow I feel much better for going with the older Haswell-E instead. I don't want "unpredictable behavior" under stress. Mostly because encoding H.264 video on all cores gives me pretty similar stress conditions as torture stability testing tools. So, the situation is pretty real.

I've been using Skylake for longer than you have been using Haswell-E, and I have yet to see an FMA3 freeze. I also don't tend to mod software just to be able to break stuff. Do keep in mind that's what you are doing. AMD supports FMA4, Intel FMA3, but either way, since both do not support the same stuffs, the chances of a programmer actually using this stuff is actually kind of rare, especially given that you need to mod P95 to get the freeze to happen.

As to this affecting BCLK OC on non-K CPUs, we'll need to see these BIOSes roll out first, and then the "fixed" BIOS will get the same mod that the current ones do. If it breaks BCLK OC, then you should be able to simply flash back to the appropriate BIOS, and then to avoid the problem, don't mod software, m'kay? :P

cadavecaAMD supports FMA4, Intel FMA3
...
the chances of a programmer actually using this stuff is actually kind of rare

im not so sure about the changes of a programmer using avx instructions common to both camps being so rare

cadavecamod software just to be able to break stuff

cadavecadon't mod software

changing config settings is now considered modding? the guys changed a text file flag...

besides this looks to me a lot like a marriage of the fdiv and f00f bugs (one only triggered on some situations, the other promptly halted execution until reset), and while people dont run prime95 fft mode with avx acceleration all the time, i still wouldnt want to use a cpu that might trip on some avx usage scenario

truth tellerim not so sure about the changes of a programmer using avx instructions common to both camps being so rare



changing config settings is now considered modding? the guys changed a text file flag...

besides this looks to me a lot like a marriage of the fdiv and f00f bugs (one only triggered on some situations, the other promptly halted execution until reset), and while people dont run prime95 fft mode with avx acceleration all the time, i still wouldnt want to use a cpu that might trip on some avx usage scenario

I mean, I've got like 10+ months of running Skylake (before retail launch), and have yet to see any problem, so yeah, it's rare now, and only really triggered by changing the default configuration of the software, which, yeah, I call modding. Most users will download and run the software without any such changes... until now. Most users won't even have any idea that changing options this way is possible. You do have to create a file that didn't exist prior and add it to the program, so yeah, modding.

However, you are right, it is possible that in the future there will be some software that causes this bug to trigger. Yet by then, these BIOS updates will probably be out.

FordGT90ConceptNo BIOS updates since December. I'm sure that doesn't contain a fix...

I'm guessing we won't see updated BIOSes for a few weeks at least. Unless you have an eVGA board, then you won't see an updated BIOS at all...

newtekie1I'm guessing we won't see updated BIOSes for a few weeks at least. Unless you have an eVGA board, then you won't see an updated BIOS at all...

is eVGA really that bad with bios updates?

Much ado about nothing... run P95 and modify the length? You MAY have an issue. Otherwise, nothing to really worry about.

This is exactly the reason enthusiasts ( Extreme edition ) CPU should not be released first. Let the mainstream users Beta test the new CPU and re release once they are perfected ( aka Devils Canyon, Kaby lake etc)

R-T-Bis eVGA really that bad with bios updates?

Still waiting on a promised BIOS update for my P55 FTW 200 motherboard to fix the broken front side USB ports...

So, I'd say yes.

cadavecaHowever, you are right, it is possible that in the future there will be some software that causes this bug to trigger. Yet by then, these BIOS updates will probably be out.

From what I understand, they are actually disabling FMA3, forcing Prime95 to use the older AVX. That is what is causing the bug, and AFAIK, AMD supports AVX in their processors too(from the FX line on). So it could be something that crops up if you have a program that uses the older AVX. Unless disabling FM3A causes Prime95 to switch to AVX2.0, which AMD doesn't support. In which case you're right, none but a very select few Intel only programs will show an issue.

truth tellerso they are sure that this major hardware cockup can be fixed in microcode? for all cases and not just this fft avx subroutine implementation? or can we expect multiple "fixes" from here on out for other "might freeze" scenarios?

It only seems to happen with hyper-threading enabled if I understood correctly -- so that points to the instruction being right, but some sort of resource sharing being wrong, perhaps dispatch rules.

This would be a great time to also "fix" that whole motherboards that allow non-K CPU's to overclock "problem."

Y'know? Because stability. Or something.

I did a bit of homework on this issue.

I'm a bit of a bios modder in my free time.

It appears this issue got fixed with Skylake Microcode update 56 (that's hexidecimal 56), possibly even earlier, I didn't test every version, but patching my bios with that microcode fixed this issue.

Here's the kicker: Microcode update 56 came out 10-24-2015. That's right, almost 3 months ago.

Yep, Intel has had this fixed for a while... Not sure if @btarunr wants to note that or not. ;)

Meanwhile, nearly all skylake boards I played with have old revisions down in the 30-4A range. My gigabyte board I use was particularly low. No idea why the board vendors do this, but they really dropped the ball here.

So blame the board vendors... for not actually using the code intel releases.

I'm skilled enough to patch the microcode on most bioses to the right version if anyone wants to contact me and accept the "if it's bricked it's not my fault" policy etc etc.

Here's a relevant screenshot. Before applying intels proper microcode, this would've crashed long ago:

R-T-BI did a bit of homework on this issue.

I'm a bit of a bios modder in my free time.

It appears this issue got fixed with Skylake Microcode update 56 (that's hexidecimal 56), possibly even earlier, I didn't test every version, but patching my bios with that microcode fixed this issue.

Here's the kicker: Microcode update 56 came out 10-24-2015. That's right, almost 3 months ago.

Yep, Intel has had this fixed for a while... Not sure if @btarunr wants to note that or not. ;)

Meanwhile, nearly all skylake boards I played with have old revisions down in the 30-4A range. My gigabyte board I use was particularly low. No idea why the board vendors do this, but they really dropped the ball here.

So blame the board vendors... for not actually using the code intel releases.

I'm skilled enough to patch the microcode on most bioses to the right version if anyone wants to contact me and accept the "if it's bricked it's not my fault" policy etc etc.

Here's a relevant screenshot. Before applying intels proper microcode, this would've crashed long ago:

If you can combine the non-K OC bits with this MC update... We needs to have a chat. I'll be PM'ing you about this soon.