Rebooting When Activating XMP Profile

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640
I recently bought a new motherboard, cpu, and memory to go with it. I got a Asrock Fatal1ty AB350 Gaming K4 AM4, G.SKILL TridentZ Series 16GB (2 x 8GB) DDR 4 3200, and a Ryzen 1600x. The manufacturer says the motherboard supports OC 3200 so I go into the bios and set the XMP profile 1 that sets the speed to 3200, the timings to what their supposed to be, and Dram Voltage to 1.35v what it also says on the box of the ram.

When I do this my computer reboots and reboots over and over about 4-5 times before it does a successful boot. Obviously I'm not gonna keep these settings if its causing reboots like this. I suspect it has something to do with voltage issues, but I do not see why it is not working and for reference I am using a 620W SeaSonic M12II. I have no idea whats going on please let me know if anyone has any ideas or if I just have something defective.
 
Solution
Shoot for 2933. There are issues with ryzen above that speed right now. AMD is supposed to be releasing a microcode update to help soon. Also ensure you have the latest BIOS. It won't run 2933 with the bios that came on the board most likely

Supahos

Expert
Ambassador
Shoot for 2933. There are issues with ryzen above that speed right now. AMD is supposed to be releasing a microcode update to help soon. Also ensure you have the latest BIOS. It won't run 2933 with the bios that came on the board most likely
 
Solution

Dan28453

Reputable
Feb 1, 2016
159
0
4,710
overclocked cpu + high frequency ram = instability.

i went through a similar problem, my pc attempting to boot multiple times before sucessfully booting.
i would turn off turbo boost for the processor since that might help.
 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640


I'm not sure exactly what you mean do you want me to set timings and voltage to what the manufacture suggest and then change the speed to 2933 after a successful boot at default speeds but upped voltage and timings?
 

Dan28453

Reputable
Feb 1, 2016
159
0
4,710


dude, did you even consider my solution....
 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640


I was trying to see If I could keep the turbo speeds on first, but I will try turning off turbo and up the speeds. Though I wonder if for gaming keeping turbo on and slower ram is better or vice versa.
 

Dan28453

Reputable
Feb 1, 2016
159
0
4,710


asrock was a disappointment for b350 series so its most likely using an excessive amount of voltage for the 300mhz boost in clock speeds which honestly wont make THAT much of a difference compared to having ram from 2400mhz to 3200mhz.

if you turn off turbo boost you will have a more optimal voltage and the motherboard wont be throwing voltage across the board like a maniac. revert back to stock bios, disable boost and enable xmp settings for 3200mhz
 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640


Yeah I finally fixed the BSOD issue and I plan on running memtest tonight when I have time I'll update with the results.
 

Stag1928

Distinguished
Jan 3, 2010
149
0
18,680
Has there been any success with getting it to run at 2400? I've got the ASRock AB350 Pro4, and a pair of Team Vulcan 2666mhz ram and when I changed the clock speed to 2666, it wouldn't even post. I haven't tinkered since because it runs fine at 2133 but it'd be nice to get it going quicker.
 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640


Yeah I was able to get 2400 you should give it a shot. 2666 and above though will not post like you said. Make sure you have the newest bios I think its 2.50 version.
 

Stag1928

Distinguished
Jan 3, 2010
149
0
18,680


I think I do- the little sticker on the Mobo says p1.4 which should be the AGESA version (I think). I know the ASRock site only has one UEFI version listed for flashing which I presume is what is on there. What's another way to check? I'm a little hesitant in flashing the BIOS due to bricking and whatnot
 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640


You can check in your bios itself on main page what bios version your at. Flashing always has some risk I guess I've never had an issue. ATM though I'm dealing with a lot of BSOD issues non bios related so its hard to help you since my systems got so many issues itself lol.
 

Stag1928

Distinguished
Jan 3, 2010
149
0
18,680


Good call, per the bios I've got 1.4 and the current version is 2.5. Also, I have the RAM installed in slots A1 and A2 which 1) only works in single channel, and 2) doesn't clock above 2400. I'm presuming that along with the bios update might get me running at 2666mhz
 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640


Wait do you have the same Mobo as me because if you do you want the RAM according to the manual in A2 and B2. Make sure you double check your Mobo manual and their website to make sure you have your RAM in the right slots.
 

Stag1928

Distinguished
Jan 3, 2010
149
0
18,680
[/quotemsg] Wait do you have the same Mobo as me because if you do you want the RAM according to the manual in A2 and B2. Make sure you double check your Mobo manual and their website to make sure you have your RAM in the right slots. [/quotemsg]

I've got the AB350 Pro 4. I just realized last night I had them in A1 and A2 so I need to just move one into B2 and that should do the trick. I'm still a little hesitant on the BIOS update until at least the new AGESA update comes out simply because it's working well enough and per the website, the only update deals with Summit Ridge chips (I think). I saw a video on youtube of someone with the same board and his sticks were running at 2666.

 

godlikekittinsoldier

Distinguished
Nov 7, 2010
68
0
18,640
Wait do you have the same Mobo as me because if you do you want the RAM according to the manual in A2 and B2. Make sure you double check your Mobo manual and their website to make sure you have your RAM in the right slots. [/quotemsg]

I've got the AB350 Pro 4. I just realized last night I had them in A1 and A2 so I need to just move one into B2 and that should do the trick. I'm still a little hesitant on the BIOS update until at least the new AGESA update comes out simply because it's working well enough and per the website, the only update deals with Summit Ridge chips (I think). I saw a video on youtube of someone with the same board and his sticks were running at 2666.

[/quotemsg]

Yeah I wouldn't worry too much about the bios unless it fails to go 2666 and you REALLY want it. Even with the BIOS update I still can't get 2666, but it turns out I have a faulty GPU I don't know if that can have any impact. I'll probably try again when I get my RMA.

Hmm looks like somethings going on with the quoting lol.
 

Stag1928

Distinguished
Jan 3, 2010
149
0
18,680


I've got the AB350 Pro 4. I just realized last night I had them in A1 and A2 so I need to just move one into B2 and that should do the trick. I'm still a little hesitant on the BIOS update until at least the new AGESA update comes out simply because it's working well enough and per the website, the only update deals with Summit Ridge chips (I think). I saw a video on youtube of someone with the same board and his sticks were running at 2666.

[/quotemsg]

Yeah I wouldn't worry too much about the bios unless it fails to go 2666 and you REALLY want it. Even with the BIOS update I still can't get 2666, but it turns out I have a faulty GPU I don't know if that can have any impact. I'll probably try again when I get my RMA.

Hmm looks like somethings going on with the quoting lol.[/quotemsg]

Sorry to raise the dead here, but I've got my RAM running at 2666 with DRAM voltage up to 1.35 on the latest BIOS with AGESA 1.06. Just wanted to share since these are technically "unsupported" sticks that are running at the rated speeds
 

hitzatak

Prominent
Jun 25, 2017
1
0
510
I just got myself some DDR4 3000 RAM - now after enabling the XMP (and selecting 2933), it also does the restarting 5-6 times when I reboot the computer.
My ASROCK X370 Taichi BIOS has been flashed the latest version.
After reading the thread, there doesn't seem to be a proper solution...

I guess I have to run it at a lower speed?