Author: Teyn
Subject: Upgrade to Ryzen 3600 on Fatal1ty AB350 gone wrong
Posted: 12 Jul 2019 at 5:22am
Hey Matt,
strange, I'm experiencing all the same discribed issues with a B450 Fatal1ty Gaming-ITX/ac and my new Ryzen 5 3600. Exactly the same. I contacted the German support but there only guess is a defectice CPU. My guess is, that AGESA 1.0.0.1 is unstable in various configurations and I'm waiting for a new BIOS. MSI draw back all BIOS Versions they released with AGESA 1.0.0.1 caus of instability.
Nils
Subject: Upgrade to Ryzen 3600 on Fatal1ty AB350 gone wrong
Posted: 12 Jul 2019 at 5:22am
 dillon wrote:I decided to post here just to give ASRock some feedback. I've been working up a number of systems with the 3600X and I have several B350 Gaming-itx/ac mobos. I am having serious trouble just getting the BIOS to post with the 3600X. I upgraded one to BIOS 5.70 and it booted fine with the 2400G that was in there before. However, when I plugged in the 3600X the system got really unhappy. * It takes around 15-20 tries before the BIOS will POST, often requiring a hard power cycle with the power switch on the PSU. I will describe the difficulty down below. * I have an old Radeon 6450 GPU plugged in (to get a display). I also tried plugging in a far more modern RX580, but the behavior is similar (it might successfully post a little more often, but it still fails most of the time). * When the BIOS does post, however, the system appears to come up fine. * I tried many configurations. I tried the stock configuration, I tried undervolting, I tried turning on overclocking but setting the frequency low (3.8 GHz). I tried running the memory at various speeds including 2133. I tried changing the memory out. I tried a different PSU. I tried a more modern GPU (an RX580)... none of this messing around changes the POST behavior by much. Possibly changing out the GPU helps it post a little more often but the behavior is basically the same. The BIOS post behavior is as follows: * Power button. System powers on, CPU fan starts at low speed, system fan does not. GPU fan does not. No display (obviously). System is burning around 35W. The system always starts this way and will then proceed to behave in three different ways: (1) The BIOS will power cycle the machine itself every 10-15 seconds or so. I observe the CPU fan turning off, then on again. The watt meter shows that the system power cycled itself. This will repeat many times (several minutes sometimes) until either the system posts or the system locks up. (2) When the system posts, the CPU fan will cycle to full power and the case and GPU fans will also turn on. The system posts a few seconds later and works normally. (3) Sometimes the CPU fan will cycle to full power and the case and GPU fans will turn on, but the system will fail to post (no display, no beep codes, nothing). In this situation the power button no longer works... neither hitting the power button OR holding it down will power the machine down. I wind up having to switch the PSU off, wait a few seconds, then switch it on again. (4) Sometimes the CPU fan remains at low speed and stops power cycling. Again the system has locked up. The power button does not work either momentary or held-down, requiring the PSU to be switched off and then on again. Note that when the system does post, it seems to operate perfectly. Note that this behavior is definitely BIOS / POST related. It occurs whether I have any storage connected up or not. That is, it has nothing to do with the operating system. Note also that when this BIOS does post, it doesn't seem to recognize its own ethernet adapter so I can't (for example) pxeboot the box. USB recognition seems to be spotty too. SATA recognition appears to be reliable. Finally, note that similar configurations on the B450 mobo with the latest BIOS for that mobo work perfectly. Its the B350 mobo that is having all the issues. Hopefully this helps! -Matt |
Hey Matt,
strange, I'm experiencing all the same discribed issues with a B450 Fatal1ty Gaming-ITX/ac and my new Ryzen 5 3600. Exactly the same. I contacted the German support but there only guess is a defectice CPU. My guess is, that AGESA 1.0.0.1 is unstable in various configurations and I'm waiting for a new BIOS. MSI draw back all BIOS Versions they released with AGESA 1.0.0.1 caus of instability.
Nils