Cool and Quiet seems to cause freezing

Robmeng

Prominent
Jun 26, 2017
14
0
510
Hi chaps,

I built a new rig for my partners birthday a few days ago

Asrock ab350m pro4 (BIOS/UEFI 2.50)

Hynix sl308 canvass 120GB

2x4GB corsair vengeance lpx 2400 DDR4

Ryzen 5 1500x (stock cooler - no OC)

MSI gtx 970 4g gaming (no OC - has a factory OC i believe?)

Seasonic G series 450W hybrid modular

Corsair 270R case

I pulled two old WD 1TB green drives for storage, OS and Team Fortress 2 both installed on SSD though.

PC seems to freeze at random, but not lock up, just certain tasks will hang. Happened when trying to view a saved image file yesterday. Today it was playing TF2, a minute or so after starting up the game it would hang, we could alt-tab just fine and HWMonitor showed sub 60c temps from mobo to drives to cpu etc we restarted PC three times, reinstalled GPU driver but still the same.

The issue is seemingly caused by cool and quiet, i disabled in bios/uefi and the game ran smooth as butter.

Ram was underclocked by default by mobo, i loaded included XMP profile which was set to advertised speed, timing etc. I touched nothing else.

I've used HWMonitor and Coretemp, temps read fine in both. I've download AMD's power plan, it must be related to cool and quiet but i have no idea what/why. Any help would be much appreciated.



 
Solution
I've got this exact same problem with a Ryzen 1600 and gigabyte gaming 3 mobo.
System would just hard-lock at the most inconvenient times.

Took me forever to figure out that disabling cool&quiet stopped it -- who would have thunk?
I've got all the latest bios, didn't matter.


I had same issues with A12-9800 on GA-ab350m.. Tried everything to stop game crashes until i switched off Cool and Quiet function on the BIOS.. Quite few people must be having same problem. Installed latest F10a .
 
I've got this exact same problem with a Ryzen 1600 and gigabyte gaming 3 mobo.
System would just hard-lock at the most inconvenient times.

Took me forever to figure out that disabling cool&quiet stopped it -- who would have thunk?
I've got all the latest bios, didn't matter.
 
Solution