F5F Stay Refreshed Hardware Desktop I'm a DumbDumb, also known as Ryzen 1600AF RAM compatibility.

I'm a DumbDumb, also known as Ryzen 1600AF RAM compatibility.

I'm a DumbDumb, also known as Ryzen 1600AF RAM compatibility.

T
TRIGGERBARBER
Member
58
08-23-2018, 12:58 PM
#1
I bought several components without proper investigation. My first desktop took some time to assemble, which led to errors. I own a Gigabyte Aorus B450 Elite with a Ryzen 5 1600AF and two Corsair Vengeance LPX CMK8GX4M1D3000C16 sticks. I also have an M.2 NVME drive, specifically the SX8200PNP 1TB, which isn’t listed on the QVL—this might complicate things further. I’m hoping for some guidance on making the system stable at frequencies above 2133MHz in the RAM. If anyone has advice, I’d really appreciate it. Otherwise, feel free to tease me about my choices.
T
TRIGGERBARBER
08-23-2018, 12:58 PM #1

I bought several components without proper investigation. My first desktop took some time to assemble, which led to errors. I own a Gigabyte Aorus B450 Elite with a Ryzen 5 1600AF and two Corsair Vengeance LPX CMK8GX4M1D3000C16 sticks. I also have an M.2 NVME drive, specifically the SX8200PNP 1TB, which isn’t listed on the QVL—this might complicate things further. I’m hoping for some guidance on making the system stable at frequencies above 2133MHz in the RAM. If anyone has advice, I’d really appreciate it. Otherwise, feel free to tease me about my choices.

D
DokiBaby
Junior Member
34
08-23-2018, 08:27 PM
#2
I’m not sure you’ll run into any problems. The best chance is the XMP profile works at 2933MHz or a small voltage increase, though a drop to 2933MHz or a slight boost might fix it. Running 3000MHz CL16 on two single-rank sticks should be fine on a 1600AF and B450 board.
D
DokiBaby
08-23-2018, 08:27 PM #2

I’m not sure you’ll run into any problems. The best chance is the XMP profile works at 2933MHz or a small voltage increase, though a drop to 2933MHz or a slight boost might fix it. Running 3000MHz CL16 on two single-rank sticks should be fine on a 1600AF and B450 board.

A
Alexandrea1
Member
233
08-25-2018, 05:42 PM
#3
It should work if you make a few adjustments as discussed. My Ryzen 5 1600 (nonAF) runs on a B450, and I was able to get non-QVL 3200 to function eventually.
A
Alexandrea1
08-25-2018, 05:42 PM #3

It should work if you make a few adjustments as discussed. My Ryzen 5 1600 (nonAF) runs on a B450, and I was able to get non-QVL 3200 to function eventually.

Z
Zorro340
Junior Member
48
08-25-2018, 07:31 PM
#4
Activate XMP while configuring the frequency to 2933MHz for improved speed! :3
Z
Zorro340
08-25-2018, 07:31 PM #4

Activate XMP while configuring the frequency to 2933MHz for improved speed! :3

K
karlerik_1999
Member
205
08-25-2018, 08:05 PM
#5
I'm still checking the idea but it seems the Boot Drive might be the root cause. If the computer stops working then there are two possible situations: either it doesn't start at all when I power it on and both the CPU and VGA lights come up on the motherboard, or the system boots but the NVME isn't recognized. In either case, the fix is to unplug the device and let power settle on the board. When I return to BIOS, everything resets back to defaults and I can log back into Windows. I believe the issue relates to power states—specifically a recent blackout in South Africa that caused loadshedding. It worked fine after the machine came back online last night. I turned off sleep, fast startup and fast boot but haven't found a resolution yet.
K
karlerik_1999
08-25-2018, 08:05 PM #5

I'm still checking the idea but it seems the Boot Drive might be the root cause. If the computer stops working then there are two possible situations: either it doesn't start at all when I power it on and both the CPU and VGA lights come up on the motherboard, or the system boots but the NVME isn't recognized. In either case, the fix is to unplug the device and let power settle on the board. When I return to BIOS, everything resets back to defaults and I can log back into Windows. I believe the issue relates to power states—specifically a recent blackout in South Africa that caused loadshedding. It worked fine after the machine came back online last night. I turned off sleep, fast startup and fast boot but haven't found a resolution yet.

R
Razore
Junior Member
6
08-26-2018, 09:45 PM
#6
Is your BIOS updated to the newest release? This could assist with RAM problems if your system uses an older model.
R
Razore
08-26-2018, 09:45 PM #6

Is your BIOS updated to the newest release? This could assist with RAM problems if your system uses an older model.

A
Antal1609
Junior Member
3
09-01-2018, 07:46 PM
#7
A fresh update is now available focusing on XT enhancements and better APU support. I'll monitor for any fixes related to memory issues before proceeding. Some users recommend reverting to a previous BIOS release instead.
A
Antal1609
09-01-2018, 07:46 PM #7

A fresh update is now available focusing on XT enhancements and better APU support. I'll monitor for any fixes related to memory issues before proceeding. Some users recommend reverting to a previous BIOS release instead.

S
swedish_melon
Member
109
09-05-2018, 03:36 PM
#8
The newest release (F52f) includes AMD AGESA ComboV1 1.0.0.6, significantly enhancing memory support. It’s worth updating for better performance.
S
swedish_melon
09-05-2018, 03:36 PM #8

The newest release (F52f) includes AMD AGESA ComboV1 1.0.0.6, significantly enhancing memory support. It’s worth updating for better performance.

N
nenette24
Member
149
09-05-2018, 06:00 PM
#9
I couldn't locate any information on AGESA ComboV1 1.0.0.6. Could you share the changelog or describe your situation? I'm here to help.
N
nenette24
09-05-2018, 06:00 PM #9

I couldn't locate any information on AGESA ComboV1 1.0.0.6. Could you share the changelog or describe your situation? I'm here to help.

H
heroboy17
Senior Member
528
09-05-2018, 07:49 PM
#10
The BIOS update didn't help; I'm now checking for newer SSD firmware since the problem seems to be with my NVMe drive. The fix might be available.
H
heroboy17
09-05-2018, 07:49 PM #10

The BIOS update didn't help; I'm now checking for newer SSD firmware since the problem seems to be with my NVMe drive. The fix might be available.