AB350 ITX 2400G dropped FPS?

The chip and board is brand new and came with BIOS 4.40. Installed Windows Fall 2017 version and tried downloading drivers over WiFi and ran into stability issues. Noticed Beta 4.51 BIOS fixes Intel WiFi issues so flashed that and everything seemed great until I actually played my first game.

Playing Quake Champions the game appears to run fine for 15 seconds or so (60+ FPS) and then the FPS drop down to unplayable levels of stutter. This happens over and over rendering the game unplayable.

Noticed in another thread someone mentioned the Raven Ridge APU throttles down from 1200 to 400Mhz at regular intervals basically reaffirming what I'm experiencing.

Does anyone have a fix for this? I bought this setup to play light competitive games and this throttling makes it pointless.

Rest of components:

- 16GB 3000Mhz Trident Z's CL15 running at XMP speeds (Prime large FFT stable). Runs at 3200Mhz but set back to default just in case.

- Stock cooler on open bench, runs in the mid 70's under heavy loads. 127C reported in BIOS but nothing is hot to the touch. Set forced IGP in BIOS and reserved 2GB RAM for it.

- No overclocking at all.

- 300W Silverstone Bronze Power Supply

- 512GB Samsung 960 Pro M.2 NVME SSD.

- 19" Test bed monitor (1280x1024).

Installed the latest WHQL AMD drivers from AMD.com (chipset and graphics). Also updated all Windows patches.

Any help here would be appreciated. This board seems great and I really want to keep it but if I can't solve this stutter issue soon it's going to have to go back for the Gigabyte ITX...

127c reported temp in BIOS is a well know BIOS vers4.40 fault........Are you sure you are not reporting a temp issue discovered when you were on 4.40?
Never heard of it in 4.51 before.

If you message the user, please post back his solution to fixing the throttling, this way all users can have a look and check if it helps them

Thanks all. I meant to reply earlier but figured it mostly out last night (stayed up too late lol). Anyway yes, dymanic clock speeds appear to be the problem on this board. After setting all cores to 3.8Ghz at 1.3V (with a slight negative core voltage offset) all seems well with the stutters.

That being said I lose the ability of booting up at 3200Mhz clock memory speeds (from a cold boot) when I statically set the core clocks? I have to run the memory at 2933Mhz to obtain 100% successful POST when the core CPU speeds are hard set which kind of sucks as I lose a decent chunk of performance not being able to run at 3200Mhz.

So it's a bit of a trade-off at this point but I think it's something that can be fixed in a future BIOS update. Yes I tried setting vsoc voltage to +100mv and set the RAM to 1.4V (from 1.35) as well CL2 instead of 1 but cold boot fails at anything higher than 2933

Once fired up I can quickly profile swap to the 3200Mhz settings and have no problems until I shut down. Everything runs stable. Reboots work fine. The CPU actually runs a little cooler with XFR disabled and all cores set to 3.8Ghz. I wonder if my DIMMs being dual rank have anything to do with compatality issues or if something else is happening. 3200Mhz appears to be LargeFFT Prime Stable so I think it's just improper voltages being applied during the boot "training" process or something.

I will say I'm really impressed with the speeds in general so far. Only tested Tomb Raider, Quake Champions, Rocket League, Doom and 3DMark Firestrike but all blow away my previous 7870K APU with 2400Mhz CL10 Dual Rank memory.
General speeds in Windows is very comparable to my Xeon 1231v3 and 4790K which is impressive for a $160 CPU. I have several more games to test before finding a home (Silverstone ML06B currently selected) but looking for a deal on that InWin Chopin which seem a little overpriced in North America.

Anyway apologies for the long post. Thanks all for the feedback. Let's hope AsRock /AMD steps up their game. 

Edited by Choronsodom - 22 Mar 2018 at 8:43pm

I realize this is a shot in the dark, but since some users are having this issue and others are clearly not with the same hardware and BIOS, I would strongly suggest users who are having throttling issues to (1) clear your CMOS settings/reset them to default (always a must after updating the BIOS) and (2) perhaps try using Process Lasso ( https://bitsum.com/files/processlassosetup64.exe ).

At this point, I am thoroughly convinced that, given multiple users (some of which are professional system builders who have built virtually hundreds of AMD systems) have personally contacted me on Reddit adamantly stating that they have zero frame rate issues after BIOS 4.51A and the latest drivers, there is some differentiating factor other than the BIOS or the CPU.

After all is said and done this does not work for you, I can only conclude that somewhere down the line you few users who are still having issues are experiencing them due to inexperience, user error, or a non-standard configuration.

Edited by hifihedgehog - 23 Mar 2018 at 5:30am