Print Page | Close Window

bios update 4.40 will not overclock

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=7272
Printed Date: 20 Jul 2025 at 5:08am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com


Topic: bios update 4.40 will not overclock
Posted By: Clemenator
Subject: bios update 4.40 will not overclock
Date Posted: 12 Jan 2018 at 4:39pm
When I overclock to 3.7 easy way cpuz and task manger say I am running at 2.4

When I overclock using pstates to 3.8 under asrock switch it will not save and under amd switch it saves and bios say it is 3.8 however cupz and task manger say it is 2.7 

It is not a visual only bug my computer is running much slower like stock or under.

So literally for me overclocking underclocks the cpu ryzen 1600

Last note the voltage will stay at what I change it to and so will the ram just not the cpu   

ATTENTION !!!!

Found out the problem, it seems it was using pstate 2 and not 0 or 1 for some reason, I disabled all pstate bar 0 and is working fine.

As for putting the ram to 3200mhz the settings are stupid and make no seance I need to manually half it to make it work at the right speed so at 1600mhz it is really 3200mhz however this motherboard still will not boot when it is set to 3200mhz even thought it was advertised as compatible. It will however boot fine at 3066mhz in the latest update appose to 2800mhz before the update.

Also due to it not displaying the ram speed correctly when I try to manually set the timing it is not reflecting what I have set, I am assuming it is doubling it just like the mhz so it crashes the system.

What I am doing at the moment is setting the ram to half so 1533mhz to make it 3066mhz and upping  the ram voltage to 1.35 to make the ram work properly.



Replies:
Posted By: php42
Date Posted: 13 Jan 2018 at 11:06am
use AMD CBS mode, disable Cool 'n' quiet, and only set p0. clear all the other pstates as pstate throttling does not work correctly.

also note that windows task manager is known to show incorrect cpu speeds, cpuz should be correct though.


-------------
https://valid.x86.fr/7gfqhh" rel="nofollow">


Posted By: zlobster
Date Posted: 13 Jan 2018 at 11:27pm
I think OP hit a multibug. Check other posts here and on YT, it's well detailed and also fixable.


-------------
1700X ZP-B1 (stock); X370 Taichi (UEFI 3.10); 16GB F4-3200C14-8GFX XMP; 256GB 960 EVO; RX 580 NITRO+ 8GB


Posted By: Clemenator
Date Posted: 25 Jan 2018 at 2:45pm
Found out the problem, it seems it was using pstate 2 and not 0 or 1 for some reason, I disabled all pstate bar 0 and is working fine.

As for putting the ram to 3200mhz the settings are stupid and make no seance I need to manually half it to make it work at the right speed so at 1600mhz it is really 3200mhz however this motherboard still will not boot when it is set to 3200mhz even thought it was advertised as compatible. It will however boot fine at 3066mhz in the latest update appose to 2800mhz before the update.

Also due to it not displaying the ram speed correctly when I try to manually set the timing it is not reflecting what I have set, I am assuming it is doubling it just like the mhz so it crashes the system.

What I am doing at the moment is setting the ram to half so 1533mhz to make it 3066mhz and upping  the ram voltage to 1.35 to make the ram work properly.


Posted By: php42
Date Posted: 25 Jan 2018 at 3:28pm
Originally posted by Clemenator Clemenator wrote:

Found out the problem, it seems it was using pstate 2 and not 0 or 1 for some reason, I disabled all pstate bar 0 and is working fine.

As for putting the ram to 3200mhz the settings are stupid and make no seance I need to manually half it to make it work at the right speed so at 1600mhz it is really 3200mhz however this motherboard still will not boot when it is set to 3200mhz even thought it was advertised as compatible. It will however boot fine at 3066mhz in the latest update appose to 2800mhz before the update.

Also due to it not displaying the ram speed correctly when I try to manually set the timing it is not reflecting what I have set, I am assuming it is doubling it just like the mhz so it crashes the system.

What I am doing at the moment is setting the ram to half so 1533mhz to make it 3066mhz and upping  the ram voltage to 1.35 to make the ram work properly.

in AMD CBS mode you are setting the actual clock speed of the RAM. DDR speed is double the clock speed so 1600 mhz clock = 3200 MT/s.
you can google "double data rate" if you are curious as to why that is the case.

as for the timings, in AMD CBS mode it expects hexadecimal values. if you are entering decimal values then you will have incorrect timings.

EDIT: really i would suggest just rolling back to e.g. p3.30 and using the OC tweaker. especially since you're stuck with 1.35v max ram voltage on p4.40


-------------
https://valid.x86.fr/7gfqhh" rel="nofollow">


Posted By: kerberos_20
Date Posted: 25 Jan 2018 at 6:09pm
" rel="nofollow - u know that u can use timings in asrock oc right?
just it offers less frequency options. heres a little trick to it:
go to amd cbs , set ddr4 timings overclock to enabled
than go to oc page, switch to asrock, set up whatever u want
and hit f10 to save it, after reboot go back to bios and set oc to cbs
and u dont need to change a thing in cbs timings


Posted By: Clemenator
Date Posted: 25 Jan 2018 at 8:13pm
Nice little trick, I thought if you switched back and forth it would reset everything 


Posted By: Clemenator
Date Posted: 25 Jan 2018 at 8:25pm
Thank you both for the information, yes it was throwing me the hex as I looked at what asrock oc set the xmp to took a photo and than tried to do it in the amd oc settings, thing is in asrock it is not hex but in amd it is. on a side note trfc4 worked in decimal not hex yet trfc and trfc2 need to be in hex ( go figure) 

Everything is working well and will try the timing work around mentioned above     


Posted By: Clemenator
Date Posted: 25 Jan 2018 at 8:48pm
Yep that switch back and forth trick worked like a charm thank heaps.

Also no point in me downgrading as as apart form only being able to use one pstate everything else is working better for instance the ram would not go past 2800mhz stable no matter what I did before the update now it is at 3066mhz stable however problems start to show at 3200mhz even though that is my correct ram speed. Problems are constant turning on and off when trying to restart, resetting bios and bsod. 

Once they fix the pstate issue and push it up from 3066 stable to 3200 stable I will than be happy with my purchase from asrock, dont mean to sound harsh on asrock but truth be told had I known 3200mhz would not work with this board purchase day I would have got the msi or gigabyte one I was also looking at. I have always been with gigabyte mb and gpu and never had any issue so it is annoying that my first time with asrock there product will not do as advertised. 

Also the on-board sound is not so great compared to my gigabyte MB from 2010.  (I guess the saying is true you get what you pay for)  


Posted By: PetrolHead
Date Posted: 26 Jan 2018 at 2:45pm
Originally posted by Clemenator Clemenator wrote:

had I known 3200mhz would not work with this board purchase day I would have got the msi or gigabyte one I was also looking at.


Anything beyond 2666 MHz is an overclock and is not 100% guaranteed, even if the memory QVL lists the modules as compatible and at 3200 MHz. This is also mentioned in the memory QVL and the same applies to all motherboard manufacturers (assuming they even have the memory in question in their memory QVL in the first place).


-------------
Ryzen 5 1500X, ASRock AB350M Pro4, 2x8 GB G.Skill Trident Z 3466CL16, Sapphire Pulse RX Vega56 8G HBM2, Corsair RM550x, Samsung 960 EVO SSD (NVMe) 250GB, Samsung 850 EVO SSD 500 GB, Windows 10 64-bit



Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.04 - http://www.webwizforums.com
Copyright ©2001-2021 Web Wiz Ltd. - https://www.webwiz.net