Through some rigorous troubleshooting steps on a Ryzen 1700x recently, I have discovered that Ryzen Master was the cause of instability.
I am unable to rule out the suggestion that RAM compatibility might be part of the issue, however many symptoms have been fixed after removing Ryzen Master from the system.
Stuttering/Choppiness during games
Random FPS drops during games
Crashes during games
RM was installed on the system as a tool to monitor temps and voltages and was not intended to overclock. Having a search around, I read that Ryzen Master (once installed) uses a “default” profile. The default profile apparently comes with an overclock (which I was unaware of)
After removing Ryzen Master from the system, games instantly ran as expected. CS:GO no longer randomly stutters or freezes. Overwatch is as smooth as silk.
I would actually go as far as to recommend not using Ryzen Master for anything. At all. Seriously..
I read a somewhere that Ryzen Master was used to overclock the CPU. The issue arose when they tried to reverse the overclock. RM apparently overrides BIOS settings so resetting the BIOS is futile.
After removing Ryzen Master from Windows, they found that the overclock was still active. Flashing the BIOS still didn’t help. The solution was to reinstall Windows as Ryzen Master settings (somewhere) were still changing BIOS settings when Windows has been booted.
Sure, this part of my post is heresay, however after learning of this experience and solving my own issue, I will be sure not to install RM again (even of it is purely for monitoring purposes). If you plan to overclock, go old school!
After wasting a large amount of time on a recent problem detailed on this extensive blog post, I am unhappy about the way AMD drops driver packages.
This post will try to highlight some of the peculiar issues that I have noticed during this endless battle to stop BSOD’s happening to my shiney new Ryzen system.
AMD Drivers -UI
If you have an Intel CPU and an AMD GPU, or an AMD Zen CPU and an Nvidia GPU, you can read on with a smug grin. If you have both an AMD Zen CPU and AMD GPU, join the hair pulling club.
Trying to install AMD GPU and Chipset drivers to the same system can start to make you feel insane, as anyone in an infinite loop condition would do.
Effectively, they (the driver installers) fight for superiority; an AMD driver package you are trying to install checks the driver version against one that is already present on the system, regardless of the type of drivers that you are trying to install.
So for example:
You install AMD GPU driver 19.1.2. After the reboot, you say…
“Hey!, it’s now time to install the chipset drivers while I’m at it!”
…which is not a bad idea at all.
You go to the website and jump through all of AMD’s hoops to pick the right driver and download chipset driver version 18.10.1810.
You start the installer and are confronted with a screen that effectively tells you that you are installing an older driver version, comparing it with the 19.1.2 GPU driver.
This comes down to clarity; which is frankly laziness from AMD. And it doesn’t end there; the GPU drivers have an interface which allows you to find the driver version, which the chipset drivers lack only adding further to the confusion.
Below are some screenshots taken from the AMD site, showing the revision numbers. Yes! they are different, as expected. They are two separate drivers after-all but the installation battle is determined here.
Currently, the way to overcome this is to install the chipset drivers first. The UI will install version 18.10.1810. Installing the GPU drivers after means you will be “upgrading” to 19.1.2 but it doesn’t contain any chipset drivers so the currently installed chipset drivers will be untouched..
Very confusing, AMD.
The BSOD Blame Game
Issues to my system started when the Windows 10 1809 update dropped on my PC. When the problems appeared (many BSODs), I updated to the latest chipset drivers which (as it turned out) seemed to be incompatible with my “older” BIOS. Let’s explore this further.
Windows 10 1809 was officially released November 13, 2018. It wasn’t until late December that Windows Updates decided that it was time to install this hefty upgrade. The upgrade happened as usual and completed without issue.
But something had changed to make my system unstable (did I mention many BSODs?!). The only thing I can think of is a driver update with 1809 or a change relating to the kernel which meant that something isn’t working correctly. This forced me to look at updating to the latest drivers to be sure.
Alas, the latest drivers did not solve the problem and only made the issue worse. Windows 10 was the cause.
AMD – Drivers
For the time being, I’m ignoring AMD’s GPU driver roulette…
… and concentrating on chipset drivers. I think AMD likes to assume that you not only have the latest AGESA BIOS readily available for your motherboard, but also applied.
As it turns out, the latest chipset driver package doesn’t specify any patch notes, AGESA or pre-configuration requirements and it doesn’t specify exactly what is included in the package.
This most recent version could be AMD’s response to the new W10 1809 version! How Ironic.
If only AMD could tell me that this was only compatible with the most recent AGESA BIOS and that if it wasn’t available, I could try an alternative driver.
Not afraid of getting my hands dirty, let’s check for a BIOS update!
GIGABYTE – BIOS
Currently, the timeline is around 2.5 months since Windows 10 1809 was released. Had I decided to update on release day, I would have had to wait through 2 months worth of BSODs until I found a solution. I finally found the solution on Gigabyte’s website.
The new BIOS (F25) is just over a week into its’ release (currently 25/01/2019). As you can clearly see from the description, it requires the latest chipset drivers that AMD released 26/10/2018. That could mean that the chipset drivers relies heavily on the F25 BIOS. Maybe.
After looking for information about AGESA 18.104.22.168, Google is littered by speculation as far back as May 2017. So I ask myself, how bad is Gigabytes’ hardware support? and the answer is obvious, it seems*. So essentially, Gigabyte could have sat on AGESA 22.214.171.124 as early as 2017.
It’s not as clear cut as this, though. There are different AGESA versions depending on the type of chip, ZEN, ZEN+ and ThreadRipper to name those that I dug up.
*not so much obvious, actually. AGESA is incredibly badly documented for the most part, and it seems only high level slithers of the contents dribble down to consumers such as “better memory support” etc.
I am happy to conclude that the issues (since the BIOS update) have been resolved and it was most definitely a software issue.
Although only a couple of weeks of constant BSOD’s interrupted my ability to use the computer, I feel it’s still wholly unfair that we have to deal with these issues at a time when updates to security are as important as it has ever been.
If indeed Gigabyte has been sitting on this update for a while, it is totally unacceptable that these things should be left beyond the last minute.
On the same note, AMD need to provide greater clarity about the contents and pre-requirements to their drivers and stop blanketing their customers with just another iteration of the version number. Incredibly unhelpful.
My theory now is: due to the sheer amount of different BSODs errors that all pointed to memory faults, it could only have been a collaborated effort from AMD and Microsoft to help mitigate against Spectre on the AMD platform. But since the BIOS didn’t know about the changes, the drivers threw up errors.
If you have ever wondered how to add desktop shortcuts to Ubuntu, fret no more!
Whenever I use Ubuntu, it is normally through command line. But recently, I have been using Ubuntu 16.04 Desktop in a VirtualBox container, almost solely as a C IDE. I’ve never really understood the workings of the GUI (properly) and have almost become used to finding it unnecessary, until now.
Unfortunately, adding icons to the desktop is a little more involved then just “right click, make shortcut” as you would in Windows, but it’s not too complicated.
In Windows, an icon is usually a direct link to an .exe file within the installation directory.
In Linux, it’s a script. It’s a file that tells the GUI environment the icon picture, the text to be displayed underneath the icon, and can house different configurations such as the name depending on local language settings for example.
To add an icon, you need to locate the folder where all of your installed software icons are stored.
The “Creators” update dubbed by Microsoft as being the latest big update to their heavy-lifting Windows 10 OS.
Most of the new features are pretty obscure and won’t bring me any great enjoyment (other then being up-to-date, which seems to be pretty important in recent times).
However, it seems it has “created” some problems of its’ own. After doing some housekeeping (updating to the new W10 update, updating drivers and applying a bios update), I noticed the boot process spending alot more time then it did previously.
At first it could have been a problem with UEFI after the bios update, but ruled it out when it eventually booted and didn’t prompt me to activate Windows again.
indicator-multiload is a small lightweight package found in Ubuntu to display different system IO graphs on the GUI menu bar. It’s really simple and lightweight, with numerous graphs and options to choose from!