AB350M Pro4 - Bios 2.50 - Issues with OC. |
Post Reply | Page 12> |
Author | |||
Zach1928
Newbie Joined: 30 May 2017 Status: Offline Points: 107 |
Post Options
Thanks(0)
Posted: 25 Oct 2017 at 5:15am |
||
|
|||
sobekite
Newbie Joined: 27 Jun 2017 Status: Offline Points: 21 |
Post Options
Thanks(0)
|
||
Hmm, I'll see if i can post a picture. I've set it to manual and only have CPU Freqeuncy (Mhz) and then CPU voltage (V) which defaults to 3.200 and 1.25000, with SMT turned on.
Directly below that it's SMT mode disable/enable and then goes into XMP settings. Edited by sobekite - 27 Jun 2017 at 9:48am |
|||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
||
Then again, maybe not.
|
|||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
||
You are. Change the top line under OC Tweaker from Auto to Manual. |
|||
sobekite
Newbie Joined: 27 Jun 2017 Status: Offline Points: 21 |
Post Options
Thanks(0)
|
||
Parsec, thanks for the detailed response.
1. When I have the memory at 2400 (dual channel 2x8) and 2.50 UEFI version and I do NOT OC the cpu, I can successfully boot and go into Windows, totally stable. 2. I don't have access to voltage modes, only core CPU frequency and vcore voltage, unless i'm missing some kind of advanced configuration menu in the UEFI. 3. When OCing with Ryzen Master, I used 1.28v, as it was one of the voltages I noticed the bios was using when I OC'd it on the shipped bios (which only had target freq and everything else auto'd). 4. Thank you for this. It explains alot of the strange voltages, which i'm now noticing on stock. Will update CPU-Z. 5. In the screenshot i'm using bios 2.50 and OCing to 3.8 on 1.28 in Ryzen Master. Will have to take a look at the voltage reading from bios like you mentioned. I can still OC from Ryzen Master successfully and run various benchmarks for stability, but the downside is having to run Ryzen Master in the first place. It seems to take up 10-15% CPU utilization even while static, and it's settings seem to reset after waking from sleep. Is reflashing the bios with 2.50 possible, or maybe rolling back to 2.40? When I tried 3.5 ghz at 1.28v it didn't boot. Could that potentially have caused it (from what I've read it should be stable at 3.5 easily.)?
Worse case scenario I'll wait for another bios update, no big deal. Edited by sobekite - 27 Jun 2017 at 9:35am |
|||
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
||
sobekite, with your memory speed at 2400 and the 2.50 UEFI version, if you do NOT OC the CPU, does the PC boot?
Did you try setting a CPU OC frequency, but leave the VCore on Auto, and does that boot? Now that you can set the VCore, what voltage mode did you use? I should ask what voltage modes do you have, Offset, Fixed? When you did the OC with Ryzen Master, what voltage did you set for the VCore? Or what VCore readin did you get in AIDA64? In you screenshot picture, you can see CPU-Z 1.79 showing 2.56V, while AIDA64 shows 1.250V. That's an example of how that version of CPU-Z is wrong, since a VCore of 2.56V is crazy high. Note that the AIDA64 value of 1.25V, multiplied by two, is 2.5V. A VCore reading is data that must be translated into the correct value, and CPU-Z 1.79 was off by a factor of two for Ryzen processors. It also looks like AIDA64 is only calculating VCore to two decimal places, if we trust CPU-Z 1.79 at all. My point is your VCore would be 1.258V. Next, for an OC to 3.8GHz, a VCore of 1.253V would be on the low side, and if correct would indicate a very good Ryzen 5 1400 CPU. So 1.253V at 3.8GHz was the Auto VCore value according to AIDA64? Actually, what is the situation for your screenshot? Ryzen Master OC? The Auto VCore OC with the original UEFI version? Or something else? You said you had a reading of 1.28V in the UEFI with the original UEFI version? I can tell you the VCore reading in the UEFI will be lower than will be needed in Windows. My Ryzen board's VCore in the UEFI is substantially lower than it is in Windows. But yours seemed to be higher in the UEFI, or almost the same as in Windows? Normally only one core of a CPU is active when in the UEFI/BIOS. |
|||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
||
I've discovered here that when it fails to OC back to where it did, BIOS rev notwithstanding, clearing the CMOS(battery out, jigger the CMOS jumper) most times clears that up. I don't have pics to prove it yet I don't think "Reset to UEFI Defaults" is actually clearing ALL that I've dinked with. |
|||
sobekite
Newbie Joined: 27 Jun 2017 Status: Offline Points: 21 |
Post Options
Thanks(0)
|
||
@wardog, thanks for the help. I will take your advice and update both CPU-Z and some of the other monitoring apps I've been using. Will get the memory model for you as well, although I am almost certain it's BLS8G4D240FSB.
I realize that ram model isn't listed on the supported memory list on Asrocks support page, but it seemed to work without any issues. I'll tinker around when I get home and post the results.
Thanks! |
|||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
||
Prior to 1.79.0 CPU-z had some issuesl. 1.79.1 AFAIK is now working as it should.
Meh, post that mem model when you get home. Now knowing it is running at 2400MHz it might not mean much now. Still .......... |
|||
sobekite
Newbie Joined: 27 Jun 2017 Status: Offline Points: 21 |
Post Options
Thanks(0)
|
||
Attached Images to show these strange voltages. Also CPU-Z didn't validate the score the first time around but after 2.50 it 'validated' it with a green stamp at 2.5v lol. Edited by sobekite - 27 Jun 2017 at 3:46am |
|||
Post Reply | Page 12> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |