One of my internal benchmark applications is insta-hard-freezing on Ryzen.
- Ryzen 7 1800X
- Asus Prime B350M-A (BIOS 0502)
- 4 x 8GB Corsair CMK32GX4M4A2400C14 @ 2133 MHz
- Nothing is overclocked. Everything is stock.
- Windows 10 Anniversary Update
When I run the Haswell binary from here: https://github.com/Mysticial/Flops/t...naries-windows
The entire system usually freezes when it gets to:
Single-Precision - 128-bit FMA3 - Fused Multiply Add:
Sometimes, it will make it past that, but it usually ends up crashing/freezing later on in the test anyway.
For those who don't trust the binary, the program is completely open-sourced in that GitHub repo
. If you have Visual Studio installed: Open the project, build the x64 Haswell binary, and run.
For me this always
hard freezes the computer:
- At all clock speeds.
- When running single-threaded, it happens to any core that I pin it to.
The questions that I want to answer are:
Is this specific to my setup? No - Confirmed by multiple other people.
- Is this specific to Asus mobos or an immature BIOS? If so, can it be fixed with a later BIOS?
- Is this an issue with Windows? The crash does not seem to happen in Linux, but that is with slightly different code due to differing compilers.
- Is this a CPU errata? (I hope not - however unlikely it might be.)
Current Testing Status:
All of these are running Windows, and are at stock settings or underclocked.
- 1800X + Asus Prime B350M-A (BIOS 0502)
- 1700 + Asus Prime B350M-A (BIOS ???)
- 1700 + Asus Crosshair VI Hero
- 1700 + Asus Crosshair VI Hero (BIOS 5803) (two sets of memory G.Skill + Kingston - also fails with overvolted SOC)
- 1800X + Asus Crosshair VI Hero (Windows 7) - Once pass, mostly failures.
- none yet
For those interested in the technical details, I'm getting hard freezes for all types of FMAs (128-bit, 256-bit, single and double precision). But for some reason, it only affects this particular benchmark. Other programs (like prime95 and y-cruncher) aren't affected despite using FMAs.
As much as I had least expected this to be the case, this appears to have been confirmed as an errata in the AMD Zen processor
. In other words, the last bullet on my list (and the most serious). Fortunately, it's one that is fixable with a microcode update and will not result in something catastrophic like a recall or the disabling of features.
To everyone pouring in from the various news sites:
- The important part is that a user mode program should not be able to hard freeze the entire system. Because if it can (as is the case here), it makes it possible to perform DOS attacks. IOW, this errata is a security issue.
- Don't be fooled by the "Haswell binary". The benchmark is 5 years old and I've largely neglected it for the last 3. So I haven't updated it for Zen yet. Any processor will be able to run any of the binaries if it supports the underlying instruction sets. If it doesn't, the program merely crashes with an, "illegal instruction". Under no circumstances should a user-mode application be able to bring down an entire system.