No worries on the Master the F5C bios seems to resolve the issue, well for me.
XMP enabled @3600, infinity fabric set to 1800, SVM enabled, IOMMU enabled, PBO enabled, XFR enabled with Auto Scalar setting and Spread Spectrum set to Auto.
Hmm… Solve one problem find another, with the latest bios, windows to go hardlocks, at the login screen. Rebooting, causes the system to become unbootable, unless doing a CMOS clear. This is with and without XMP, even the default optimized settings.
I use Windows to go to set my Ram and RGB fusion colors.
I am also running Windows to Go, off a Samsung T5 External drive. Microsoft, isn’t developing Windows to go anymore. I think its just unique to me. I ended up using OpenRGB in linux to set my Ram and Motherboard colors.
Still would be nice if Asrock and Msi boards,
could also being tested for the said issue.
But there seem to be enough complaints for AMD,
to take a close look to it.
And they seem to have figured out the issue with Gigabyte boards.
I apologize for the lack of recent updates on this topic. Obviously the current health crisis has not sped up the process.
On March 7th I wrote in this thread:
It turns out that is not the case, at least on my system: I recently switched back to the GIGABYTE TRX40 Aorus Xtreme motherboard (after a few weeks on the ASUS Zenith II Extreme Alpha) and the fact is that GIGABYTE’s latest BIOS version (“F4d”, AGESA 1.0.0.3 B) does not fix the instability under Prime95.
As can be witnessed in this thread, AMD has been extremely responsive and helpful. They do have a fix for the instability that works on my system, but either GIGABYTE screwed up when merging it into their F4d BIOS, or they introduced another issue.
That’s the current situation. At this point, and per my current understanding of the situation, I believe the pressure should be put on GIGABYTE, not AMD.
Ideally GIGABYTE would wake up, get in touch with us and join our conversation with AMD. Unfortunately there’s no sign that they’re willing to do that.
I’m personally done with switching motherboards. I’ve spent far too much time on this issue.
Hello @FranzB , I saw this thread and Since I have a 3960x with Aorus Master board I went ahead to test Prime95.
I currently can’t reproduce any issue with Prime95 under Windows 10 or Server 2019 (I have a dual boot system). My BIOS version is F5c
However, I tried a live Ubuntu Linux 20.04 and downloaded Prime95. I started to perform the torture test but after all threads are started I am getting a “killed” message on the terminal window. Doesn’t seems to be related to the issue you have but maybe an issue with using Ubuntu Live.
Unfortunately, Ubuntu 20.04 runs with Kernel 5.4, and only the newer Kernel 5.6 fully supports the Ryzen 3000 series power states, and PBO system. I can see that currently Ubuntu defaults to the lower PState (2.200 Mhz). So I decided not to install Ubuntu on one of my hard drives. I can also see a lot of ACPI errors under linux on boot (Oddly looks like Ubuntu supported as declared on the AMD’s CPU page is false)
I had the same issue on my TRX40 designare - PRIME seemed to work on windows and was dying like that on Linux.
This was fixed by latest firmware F4C I think.
EDIT: maybe not the same issue - I got the issue of some torture threads failing like what started that discussion.
