ROG STRIX B350-F GAMING issues

[CornFlakes]

Having constant blue screens with new bios. PC won't go 10 minutes without them and doesn't want to restart anymore. Can't even rollback to previous version. Stay away from this ****.

Can't confirm that. My Rig especially RAM is more stable now. No bluescreen or game crash since then

[Equinox187]

Having constant blue screens with new bios. PC won't go 10 minutes without them and doesn't want to restart anymore. Can't even rollback to previous version. Stay away from this ****.

Did you make sure to update to the latest Chipset Drivers? There are reports that if you did not then you might have an unstable experience in windows as in blue screens, also are you running any OC or DOCP? if so reset to default and then test if the blue screens stop then you know that previous settings will not work with the new bios.

[IIINikolaiIII]

Did you make sure to update to the latest Chipset Drivers? There are reports that if you did not then you might have an unstable experience in windows as in blue screens, also are you running any OC or DOCP? if so reset to default and then test if the blue screens stop then you know that previous settings will not work with the new bios.

I did a fresh windows install after the update so it is impossible to install the new drivers before the new BIOS as they recommend. This was at stock speeds btw. Just got the previous BIOS installed and a new windows install also and now everything is back to normal. Won't be trying that again.

[hazium233]

...
Tested headphones connected to a different device playing the same songs and they were fine. Tested the front panel connector, and it seemed mostly fine. Ended up finding a thread "Maximus Audio Popping" with a registry edit. On my Win 10 1809 machine with the MS HD Audio driver, the key I changed was at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\0000\PowerSettings

IdlePowerState changed from 03 00 00 00 to 00 00 00 00.

This seemed to fix the crackle. .

I spoke too soon, after resuming it from sleep this morning, it crackled again (static/distortion mostly right channel). But restart "fixed" it. There is another registry setting at \0007 I can try, or might need to roll back some network drivers I installed.

I disabled hibernation to get the file off my SSD, so not using fast start.

Don't know if related, but Realbench 2.56 gives 0 scores with error if I have resumed from sleep, but works perfectly if the system has been booted from off or rebooted.

[DazKnotz]

Hi guys. I'm also a (not)happy owner of this board. And I'm here to list a few problems and if any of you can give me a tip for a solution or work around to it I appreciate a lot.
First of, I bought this board over a year ago in January 2018. I knew at the time that AM4 mobos had problems with RAM compatibility issues so I make sure to get a RAM kit that was in the QVL. I bout a Corsair Vengeance LPX 8GB (2x4GB) 3000MHz CL15 (CMK8GX4M2B3000CL15 in the QVL) and what happened is that only one stick would work. If I put both it would not boot. If I put them in a different slot and different order, it would not boot, but the "working one" closer to the CPU soquet and the "faulty one" next the LED troubleshoot would cycle and then stop with the CPU error and sometimes RAM error. I fought for the RMA of the sticks for a year with the retailer and the refused to send me another one because it worked just fine on their intel bench test. Now I have a working kit that doesn't work on my mobo that is listed on my QVL. I decided to buy another kit a CORSAIR VENGEANCE® RGB PRO 16 GB (2 x 8 GB) DDR4 DRAM 3200 MHz CL16 (CMW16GX4M2C3200C16). It is not on any QVL of the mobo and it works "just fine" because at 3200MHz is unstable and it reserves 65mb to the system even by disabling all sort of things in the BIOS.
Another issue is that the voltages for the CPU is all over the place, it is set at 1.357v automatically but it jumps to 1.4, sometimes 1.5 (I have a Ryzen 5 1600X) and the BCLK is never at 100, is always lower than this. The voltage tweaking is only available over offset mode, I tried all sorts of values it but nothing works as expected Making it terrible for overclocking. It today I finally saw the new BIOS update for the new AGESA that will give support for upcoming Ryzen 3000 series and see nothing else new in it.
In all accounts, I would not suggest this mobo for anybody. It has a premium feeling to it, many interesting features but when it comes to the basic expected stuff it fails miserably since it is an expensive B350 board, it should deliver top notch performance and features, but not even decent overclocking capability or RAM compatibility. I would love some tech rundown by some specialist to see what this MOBO is capable of, because all this time, it is being really frustrating. Reply to me with any question or information so I at least can have a not so bad experience with this board.

[hazium233]

Tried to clean everything up and reinstall the Realtek_Audio_Driver_WIN10-64_V6.0.1.8496_1114 package. Updated to bios 4207. Still get static / crackles some times. Most likely to be in the right channel, and likely to happen if volume gets adjusted.

I manually installed the Realtek Audio Console since it did not install itself. Was that a mistake?

[Sapphiress]

As an update there has been no change after reflashing, clearing CMOS, and everything else. Also sometimes the new 4602 BIOS will just refuse to POST. Then I have to go in and do a CMOS reset to get it to boot up again. e.g. Set my CPU fan monitor to ignore so I could boot as I use a fan controller. Only changing that setting the motherboard refused to post then I had to do a CMOS reset and set it to ignore again and booted up without issue. There is something very wrong with this new BIOS I'd suggest not to go past 4207 as of right now.


More info: No beep codes, Top LED stayed solid and orange.

[Sapphiress]

Tried to clean everything up and reinstall the Realtek_Audio_Driver_WIN10-64_V6.0.1.8496_1114 package. Updated to bios 4207. Still get static / crackles some times. Most likely to be in the right channel, and likely to happen if volume gets adjusted.

I manually installed the Realtek Audio Console since it did not install itself. Was that a mistake?

Check your audio circutry on the board itself. I have no issues with Audio via, 3.5, optical, bluetooth or USB. There was the occasional crackle when outputting through HDMI(GPU not MoBo) but it seems to have fixed itself with AMD driver updates.

My Realtek console installed itself also with no issues. Sonic Studio also works fine.

[hazium233]

Check your audio circutry on the board itself. I have no issues with Audio via, 3.5, optical, bluetooth or USB. There was the occasional crackle when outputting through HDMI(GPU not MoBo) but it seems to have fixed itself with AMD driver updates.

My Realtek console installed itself also with no issues. Sonic Studio also works fine.

Hmmm, not sure how to check the circuitry.

The problem was somewhat intermittent and seemed like it may have been related to playing certain frequencies at certain volume ranges. When it would do it, I could set volumes to a level and play a particular song and it would crackle in the same spots. Or hit the Windows volume control repeatedly and the ding would crackle as it fade out. Turning the volume down below 10 or way up made it disappear.

But last night Windows Update found some A-Volute(?) updates and applied them. This morning it seems to be working correctly. So I have no idea if it is really hardware, intermittent interference from wifi or power cable routing (in Meshify C case with two SSDs behind the board and 8 pin wire routed up the rear), or drivers that weren't quite installed correctly. If it comes back I might tear down the case and fool around with it.

[hazium233]

There was another little thing I had noticed with this system, and that was that Realbench 2.56 would give a score of 0 for any of the tests if the system was resumed from sleep.

It would seem that this is a Ryzen sleep bug with timers, and forcing HPET via powershell fixed this issue.

I am currently on bios 4207 and chipset driver 18.50.16.01. Known issue on this board? Does bios 4602 fix this by any chance?