BIOS reset when active XMP

[basco]

after tatty one´s comment it could be really 1 timing thats not good like trfc setting too low or other that requires higher volts

but again watch out for auto volts getting too high-like the mentioned soc volt just with activating xmp

 

[Tatty_One]

Okay, tonight I'm sending you a full photo of the timings.


Last night after the bios reset, I activated the XMP again and increased the voltage to 1.4V. Now it's waiting again = /

To be honest, you are probably better off manually adjusting your timings and voltage, often you can get more out of your memory that way, the review I read showed that you can get a fair bit more out of those sticks with some tweaking, they ran at 3400mhz at CL18 on 1.4V for example.

 

[Master_Cyber]

To be honest, you are probably better off manually adjusting your timings and voltage, often you can get more out of your memory that way, the review I read showed that you can get a fair bit more out of those sticks with some tweaking, they ran at 3400mhz at CL18 on 1.4V for example.

Okay..

Do you know which memory type to choose? Because when I select Samsung B-die I get the CL14 timings and it doesn't work for me.

 

[Tatty_One]

Well to be honest, I was surprised your memory was Samsung B Die because in my limited experience your XMP timings are considerably looser than the Samsung B_Die I am aware of. I would start by manually inputting what you are trying to achieve with the XMP @ 1.4V and as you said earlier, give it a day or two to see how it responds, if all good leave the CL16 where it is and one at a time increase next timing by one, test and so on.

I no longer use XMP but mainly because I try to get more out of my memory than XMP gives. So for example I have 3000mhz memory rated in XMP at 3000mhz CL15 - 17 - 17 - 37 @ 1.35V, I run them at 3200mhz on those same timings with a voltage hike to 1.4V...…. although I appreciate you are on the AMD platform so it quite possibly will be a different story for you.

 

[basco]

what happens when ya push the button calculate safe? i think this is calc extreme

 

[Master_Cyber]

Well to be honest, I was surprised your memory was Samsung B Die because in my limited experience your XMP timings are considerably looser than the Samsung B_Die I am aware of. I would start by manually inputting what you are trying to achieve with the XMP @ 1.4V and as you said earlier, give it a day or two to see how it responds, if all good leave the CL16 where it is and one at a time increase next timing by one, test and so on.

I no longer use XMP but mainly because I try to get more out of my memory than XMP gives. So for example I have 3000mhz memory rated in XMP at 3000mhz CL15 - 17 - 17 - 37 @ 1.35V, I run them at 3200mhz on those same timings with a voltage hike to 1.4V...…. although I appreciate you are on the AMD platform so it quite possibly will be a different story for you.

Ok. I'm going to manually set 16-18-18-36 @ 1.4V

what happens when ya push the button calculate safe? i think this is calc extreme

This is calculate safe

 

[basco]

and soc volt to 1.10volt plz

after seeing thaiphoon burner B-die ram is normally speedgrade 2133 or 2400 but never saw 2666mhz?

could i ask ya for a pic of the sticker on the ram if its easy for ya- no sorry i see that its from week 41 2019

my hahaha is only for your headbanger

 

[NoJuan999]

Okay..

Do you know which memory type to choose? Because when I select Samsung B-die I get the CL14 timings and it doesn't work for me.

You need to export your XMP profile from Thaiphoon Burner by clicking on Report, then scroll to the bottom and click on display in nanoseconds then click on Export and choose Complete Report in HTML and save it somewhere you can find it again.
Then Import it into the DRAM Calculator then choose Samsung B Die and click on Calculate Safe.
I have a set of G.Skill TridentZ RGB 16GB 3200 MHz (F4-3200C16D-16GTZR) that use the lower binned C16 Samsung B die ICs and I run these timings: 16-17-17-17-36-56 @ 1.35v.

PS
Look at the Samsung OEM / V1 timings as well.

I only used the DRAM Calculator timings as a guide, I did NOT use the exact timings it provided.

 

[Master_Cyber]

and soc volt to 1.10volt plz

after seeing thaiphoon burner B-die ram is normally speedgrade 2133 or 2400 but never saw 2666mhz?

could i ask ya for a pic of the sticker on the ram if its easy for ya- no sorry i see that its from week 41 2019

my hahaha is only for your headbanger

These are the standard XMP 3000 timings.

You need to export your XMP profile from Thaiphoon Burner by clicking on Report, then scroll to the bottom and click on display in nanoseconds then click on Export and choose Complete Report in HTML and save it somewhere you can find it again.
Then Import it into the DRAM Calculator then choose Samsung B Die and click on Calculate Safe.
I have a set of G.Skill TridentZ RGB 16GB 3200 MHz (F4-3200C16D-16GTZR) that use the lower binned C16 Samsung B die ICs and I run these timings: 16-17-17-17-36-56 @ 1.35v.
View attachment 143128

PS
Look at the Samsung OEM / V1 timings as well.
View attachment 143129
I only used the DRAM Calculator timings as a guide, I did NOT use the exact timings it provided.

I put these frequencies manually, but I put the voltage of 1.4V.

Is this where I put Soc Voltage and VDDP?

 

[Deleted member 193706]

Honestly, 1.15 SOC and 1.4v RAM is not going to hurt anything but it may well give you the stability you crave. I'm running some crap spektec? RAM dies (offshoot of Micron I believe) and they are rated for 2400mhz 16.18.18 I have them running at 1.4v 3000mhz 16.18.18 from day one, I have used mixed RAM's with Ryzen also and been able to do better than what you are experiencing, don't be afraid to push some volts into them, they won't suddenly up and die despite what some people say and with some RAM it is neccesary, vcore is a different beast and I'd leave it alone unless you're shooting for CPU OC at the same time which I woulld advise you get one or the other stable before you attempt both.

 

[Master_Cyber]

Honestly, 1.15 SOC and 1.4v RAM is not going to hurt anything but it may well give you the stability you crave.

This last photo is where I put Soc Voltage, correct? I selected Fixed Voltage.

VDDP 1.0 is ok?

 

[Deleted member 193706]

This last photo is where I put Soc Voltage, correct? I selected Fixed Voltage.

VDDP 1.0 is ok?

You're within AMD spec on SOC voltage up to 1.15, and the higher your memory clock or you push your mem controller you will likely need to raise that voltage, stay within spec and you should be good.

Ryzen 3rd gen don't usually have a problem hitting 3200-3600 with compatible RAM kits and I'm surprised you have Samsung B-Die but don't be afraid to add sonme volts to your RAM or SOC as long as it's within spec

 

[Master_Cyber]

You're within AMD spec on SOC voltage up to 1.15, and the higher your memory clock or you push your mem controller you will likely need to raise that voltage, stay within spec and you should be good.

Ryzen 3rd gen don't usually have a problem hitting 3200-3600 with compatible RAM kits and I'm surprised you have Samsung B-Die but don't be afraid to add sonme volts to your RAM or SOC as long as it's within spec

Ok. I put SOC voltage 1.15.

It's all OK?

 

[trickson]

XMP is really not a good setting to use on that B450 chipset let alone on mine the X470 or any Ryzen. Not sure but I think it is an Intel thing that AMD don't like at all!
I can not get XMP to work on my Ryzen 3 B350 system at all but my Ryzen 7 can do it no problem as long as I do not over clock the CPU .
Just use the manual settings and you will get the same results if not even better.
Good luck.

 

[basco]

yes should be good cypher-soc volt 1,10 to 1,150volt

what happens when ya push import xmp? would be good if this works -you could then push compare timings and quickly see whats different.

 

[Master_Cyber]

yes should be good cypher-soc volt 1,10 to 1,150volt

what happens when ya push import xmp? would be good if this works -you could then push compare timings and quickly see whats different.

When I import and select Samsung OEM, these ranges appear there. I used that.
I called today and it's normal. Now only time will tell. I come back to give feedback.

Thank you all.

 

[maxfly]

Are you running the latest bios? If not i would try updating it. Are you ocing your cpu? If so leave your cpu at stock until you get the reset issue figured out. Can you test your memory in a friends rig? Or test their memory in yours?
If all else fails Id have to agree with the earlier poster in that your needing to rma that mb. You may also try contacting the memory manufacturer to see if they can point you in the right direction. You may need to rma that memory as well but im leaning towards a bad bios.

 

[theoneandonlymrk]

Well to be honest, I was surprised your memory was Samsung B Die because in my limited experience your XMP timings are considerably looser than the Samsung B_Die I am aware of. I would start by manually inputting what you are trying to achieve with the XMP @ 1.4V and as you said earlier, give it a day or two to see how it responds, if all good leave the CL16 where it is and one at a time increase next timing by one, test and so on.

I no longer use XMP but mainly because I try to get more out of my memory than XMP gives. So for example I have 3000mhz memory rated in XMP at 3000mhz CL15 - 17 - 17 - 37 @ 1.35V, I run them at 3200mhz on those same timings with a voltage hike to 1.4V...…. although I appreciate you are on the AMD platform so it quite possibly will be a different story for you.

You can get lower binned bdie.

 

[Master_Cyber]

Hey friends, as I said, I adjusted the times and the frequency manually, I increased the DRam voltage to 1.4V and SoC 1.15, I did not change the VDDP and VDDG.
Today (after 4 days), the BIOS was reset at cold boot.
Now I will try to change the VDDP and VDDG and then install the BIOS for agesa 1.0.0.3 ABB.

I researched and this is a known issue in BIOS 1.0.0.4 B, some people with Asrock, Gigabyte and Asus motherboards have this problem.
It’s really something with the increased frequency and cold start

Let's go to the tests again

 

[TheLostSwede]

Hey friends, as I said, I adjusted the times and the frequency manually, I increased the DRam voltage to 1.4V and SoC 1.15, I did not change the VDDP and VDDG.
Today (after 4 days), the BIOS was reset at cold boot.
Now I will try to change the VDDP and VDDG and then install the BIOS for agesa 1.0.0.3 ABB.

I researched and this is a known issue in BIOS 1.0.0.4 B, some people with Asrock, Gigabyte and Asus motherboards have this problem.
It’s really something with the increased frequency and cold start

Let's go to the tests again

Dude, don't waste your time if you haven't upgraded the UEFI. No fiddling with any settings is going to make your system stable if you're not on the right UEFI. Anything prior to 1.0.0.3ABBA had serious issues of all kinds.
You want to upgrade to AGESA 1.0.0.4, as it solves some more issues. I have ZERO issues since 1.0.0.4 and the same goes for a lot of other people here, so whatever you've researched is wrong.

 

[Fry178]

@Master_Cyber
i would start doing memtest86 on stock settings, just to verify if its stable at all/exclude board issues.
once it passes, all other changes/tweaks would just need to be "dialed in", and you then would "know" that any instabilities (memetest)
would come from the tweaks, not from an unstable rig.

and it will cost you a lot less time to do one run on stock, change settings and test again,
instead of messing with multiple settings and/or voltage at once, which clearly hasnt worked out so far.

@trickson
so far, running a x570 and using the xmp is fine, at least for the ones i setup.
did have more trouble getting samsung ram (Gskill) to run on the GB ultra i have myself,
the micron based corsair works with stock/xmp profile (3600/18@1.35v)
but i do apply dram V manually (no matter what parts/platform), so that might make a difference.

 

[Master_Cyber]

I put all frequencies and timings manually in the BIOS, already has 11 days without any reset.

And in special I put that information.

CLDO VDDP VOLTAGE CONTROL = 1.100
CLDO VDDG VOLTAGE CONTROL = 0.950
DRAM VOLTAGE = 1.400V

PROCODT = 40 OHM

GEAR DOWN MODE = ENABLE
POWER DOWN ENABLE = ENABLE

DATA BUS CONFIGURATION
RTTNOM = RZQ/6
RTTWR = RZQ/3
RTTPARK = RZQ/1

CAD BUS CONFIGURATION (CAD BUS DRIVE STRENGTH USER CONTROLS)
CLKDRVSTREN = 24.0 OHM
ADDRCMWDRVSTREN = 20.0 OHM
CSODTDRVSTREN = 20.0 OHM
CKEDRVSTREN = 24.0 OHM

I believe the problem has resolved.

Thanks to everyone and especially to the friend @basco . \o/

 

[Zach_01]

Good to know your issue solved!

Just a heads up tho

cLDO VDDP is voltage for the UMC (unified memory controller) and its located on the I/O die
cLDO VDDG is voltage for IF (infinity fabric) located in between the I/O die and CCD and interconnects them. Some boards even have 2 voltages for cLDO VDDG
1. cLDO VDDG CCD
2. cLDO VDDG IOD

Those voltages are derived from SoC voltage. So you cant set any cLDO VDDP/G equal or above SoC voltage. Its not right. There should be at least 50mv difference (less) from SoC voltage.
I'm saying this because on you last post you didnt mention the SoC voltage.

 

[basco]

Bravo i am happy for ya Master_Cyber

 

[Master_Cyber]

Good to know your issue solved!

Just a heads up tho

cLDO VDDP is voltage for the UMC (unified memory controller) and its located on the I/O die
cLDO VDDG is voltage for IF (infinity fabric) located in between the I/O die and CCD and interconnects them. Some boards even have 2 voltages for cLDO VDDG
1. cLDO VDDG CCD
2. cLDO VDDG IOD

Those voltages are derived from SoC voltage. So you cant set any cLDO VDDP/G equal or above SoC voltage. Its not right. There should be at least 50mv difference (less) from SoC voltage.
I'm saying this because on you last post you didnt mention the SoC voltage.

I used SOC VOLTAGE = 1.100