F5F Stay Refreshed Hardware Desktop XMP in dual channel mode leads to BSOD

XMP in dual channel mode leads to BSOD

XMP in dual channel mode leads to BSOD

Pages (2): 1 2 Next
J
JuliBr0
Senior Member
495
09-23-2022, 12:11 AM
#1
Hello, I understand your setup: a 7950x CPU, 6000MHz Trident GSKill, 32GB DDR5 RAM, 4090 Gigabyte water force, MSPI MPX670E with the newest BIOS 7D70v1G1. It was working fine before, but after installing two new 2TB NVMe drives and a fresh Windows install, I encountered issues. When I run Expo settings, I see a memory management BSOD after entering my Windows password. Other errors appear as well. Additionally, SQL not less than or equal to the threshold is reported. I tried running Expo with one stick, which allows access per RAM stick, but switching to dual channel mode at 6000MHz triggers a blue screen. Dual channel at 5800MHz works without problems, though not with the same Expo configuration. I’m unsure what’s causing these problems and am open to adjusting any of your recommendations.
J
JuliBr0
09-23-2022, 12:11 AM #1

Hello, I understand your setup: a 7950x CPU, 6000MHz Trident GSKill, 32GB DDR5 RAM, 4090 Gigabyte water force, MSPI MPX670E with the newest BIOS 7D70v1G1. It was working fine before, but after installing two new 2TB NVMe drives and a fresh Windows install, I encountered issues. When I run Expo settings, I see a memory management BSOD after entering my Windows password. Other errors appear as well. Additionally, SQL not less than or equal to the threshold is reported. I tried running Expo with one stick, which allows access per RAM stick, but switching to dual channel mode at 6000MHz triggers a blue screen. Dual channel at 5800MHz works without problems, though not with the same Expo configuration. I’m unsure what’s causing these problems and am open to adjusting any of your recommendations.

B
BanjoTheBear
Member
68
09-27-2022, 07:19 PM
#2
Additionally, updating drivers via GeForce Experience led to app crashes. Discord would sometimes display a gray screen, requiring minimization and reopening to restore visibility. These issues appeared shortly after the Windows installation. I ran MemTest86, which completed all four test cycles without errors.
B
BanjoTheBear
09-27-2022, 07:19 PM #2

Additionally, updating drivers via GeForce Experience led to app crashes. Discord would sometimes display a gray screen, requiring minimization and reopening to restore visibility. These issues appeared shortly after the Windows installation. I ran MemTest86, which completed all four test cycles without errors.

B
be99e
Junior Member
4
10-05-2022, 01:24 PM
#3
The BIOS may require DRAM tuning adjustments. Set VDDIO up to 1.450v, VDD up to 1.450v, VDDQ to 1.450v, VPP to 1.900v. SoC/Uncore should be adjusted to 1.350v for VDD. VDDG can go up to 1.300v. CCD settings use 1.250v VDDG IOD, and DRAM ODT impedance values are RTT_NOM_WR, RTT_NOM_RD, RTT_WR, RTT_PARK at 36 ohms. DDR bus configurations suggest Processor CK drive strengths of 60.0 0hm, CA drive strengths 30.0 0hm, CS drive strengths 40.0 0hm, and Dram ODT impedance values of 25.3 ohm and 34 ohm respectively. Note: Ensure your new NVMe drives have the latest firmware; Samsung's updates are straightforward.
B
be99e
10-05-2022, 01:24 PM #3

The BIOS may require DRAM tuning adjustments. Set VDDIO up to 1.450v, VDD up to 1.450v, VDDQ to 1.450v, VPP to 1.900v. SoC/Uncore should be adjusted to 1.350v for VDD. VDDG can go up to 1.300v. CCD settings use 1.250v VDDG IOD, and DRAM ODT impedance values are RTT_NOM_WR, RTT_NOM_RD, RTT_WR, RTT_PARK at 36 ohms. DDR bus configurations suggest Processor CK drive strengths of 60.0 0hm, CA drive strengths 30.0 0hm, CS drive strengths 40.0 0hm, and Dram ODT impedance values of 25.3 ohm and 34 ohm respectively. Note: Ensure your new NVMe drives have the latest firmware; Samsung's updates are straightforward.

A
Amtrak10
Senior Member
639
10-12-2022, 02:11 PM
#4
Check if the chipset driver is current for your system.
A
Amtrak10
10-12-2022, 02:11 PM #4

Check if the chipset driver is current for your system.

T
tfarcenim1025
Junior Member
16
10-12-2022, 11:06 PM
#5
Certainly updated and remains functional even after a fresh installation of windows.
T
tfarcenim1025
10-12-2022, 11:06 PM #5

Certainly updated and remains functional even after a fresh installation of windows.

S
SynneK
Member
185
10-13-2022, 01:31 AM
#6
I’ll definitely give it a shot when I get back tonight.
S
SynneK
10-13-2022, 01:31 AM #6

I’ll definitely give it a shot when I get back tonight.

C
Cracra
Member
79
10-18-2022, 11:31 AM
#7
Many of these voltages aren't advisable. VDD Misc and VDDG mainly influence FCLK overclocking, leaving memory overclocking untouched (and likely capped at around 1.15V, let alone higher). SOC voltage should stay below 1.3V on a BIOS released within the past year. DRAM VPP doesn't impact stability—clocks running at 1.6-2V are essentially identical to 1.8V, so adjusting it won't help. DDR bus settings vary by motherboard and BIOS, making them probably worse than factory defaults. Avoid these unless necessary. First, verify the memory is placed in slots 2 and 4 relative to the CPU socket. If correct, reset CMOS and adjust settings manually, turning off EXPO. MSI offers a "Try It!" feature that auto-applies defaults, but if you prefer manual control, set frequency to 6000, configure UCLK DIV1 Mode to UCLK=MEMCLK, SOC voltage to 1.25V, DRAM voltage to your device's rating (typically 1.35V), then navigate to Advanced DRAM Configuration and input the values shown on your memory modules.
C
Cracra
10-18-2022, 11:31 AM #7

Many of these voltages aren't advisable. VDD Misc and VDDG mainly influence FCLK overclocking, leaving memory overclocking untouched (and likely capped at around 1.15V, let alone higher). SOC voltage should stay below 1.3V on a BIOS released within the past year. DRAM VPP doesn't impact stability—clocks running at 1.6-2V are essentially identical to 1.8V, so adjusting it won't help. DDR bus settings vary by motherboard and BIOS, making them probably worse than factory defaults. Avoid these unless necessary. First, verify the memory is placed in slots 2 and 4 relative to the CPU socket. If correct, reset CMOS and adjust settings manually, turning off EXPO. MSI offers a "Try It!" feature that auto-applies defaults, but if you prefer manual control, set frequency to 6000, configure UCLK DIV1 Mode to UCLK=MEMCLK, SOC voltage to 1.25V, DRAM voltage to your device's rating (typically 1.35V), then navigate to Advanced DRAM Configuration and input the values shown on your memory modules.

A
avi15
Member
167
10-18-2022, 10:19 PM
#8
You're questioning the accuracy of the AMD DDR5 Overclocking Guide for Zen4 X3D/V-Cache chips. Others are sharing successful overclocks reaching 6400 MT/s stable, indicating it may still be relevant despite being older.
A
avi15
10-18-2022, 10:19 PM #8

You're questioning the accuracy of the AMD DDR5 Overclocking Guide for Zen4 X3D/V-Cache chips. Others are sharing successful overclocks reaching 6400 MT/s stable, indicating it may still be relevant despite being older.

H
haley123
Member
187
10-19-2022, 06:31 AM
#9
If those came from that place, then it's acceptable. That specific SOC voltage is risky to use; voltages over 1.3V can damage CPUs, which is why most AM5 boards now limit it to 1.3V since mid-2023. It seems the advice was issued around the time of Zen 4 release before those problems were recognized, but it doesn't alter the warning about CPU health. From someone who's achieved stable 6400 on AM5 several times, these tweaks usually don't make a difference. You're more likely to succeed if you get a chip that naturally runs at 6400 or if you adjust it to 1.3V. Only lowering the SOC voltage to 1.3V helps, and even then it's unlikely to fix the issue—VDDP might offer some marginal improvement but rarely resolves the problem. Running in 2:1 mode for speeds above 7600 can help a bit more, particularly with VDDP, though you should only do this if your system includes an APU.
H
haley123
10-19-2022, 06:31 AM #9

If those came from that place, then it's acceptable. That specific SOC voltage is risky to use; voltages over 1.3V can damage CPUs, which is why most AM5 boards now limit it to 1.3V since mid-2023. It seems the advice was issued around the time of Zen 4 release before those problems were recognized, but it doesn't alter the warning about CPU health. From someone who's achieved stable 6400 on AM5 several times, these tweaks usually don't make a difference. You're more likely to succeed if you get a chip that naturally runs at 6400 or if you adjust it to 1.3V. Only lowering the SOC voltage to 1.3V helps, and even then it's unlikely to fix the issue—VDDP might offer some marginal improvement but rarely resolves the problem. Running in 2:1 mode for speeds above 7600 can help a bit more, particularly with VDDP, though you should only do this if your system includes an APU.

D
DaisyPVP
Member
59
10-19-2022, 03:00 PM
#10
I recall the voltage issue with the SoC now that you brought it up, though I believed 1.35-4v was acceptable. After reviewing recent articles, it appears firmware has been updated to cap it at 1.3v. Given that many of these adjustments aren’t essential on AM5 right now, your experience is valuable. Overclock.net recommendations remain useful for rare tweaks that can help stabilize systems, especially with DDR5 support. I’m aware OCN activity has decreased, so the information might be less current than before. You’re right about the guide being released about two years ago, yet there’s still discussion on recent posts. No major complaints seem to exist, and the thread appears to have grown to around nine pages.
D
DaisyPVP
10-19-2022, 03:00 PM #10

I recall the voltage issue with the SoC now that you brought it up, though I believed 1.35-4v was acceptable. After reviewing recent articles, it appears firmware has been updated to cap it at 1.3v. Given that many of these adjustments aren’t essential on AM5 right now, your experience is valuable. Overclock.net recommendations remain useful for rare tweaks that can help stabilize systems, especially with DDR5 support. I’m aware OCN activity has decreased, so the information might be less current than before. You’re right about the guide being released about two years ago, yet there’s still discussion on recent posts. No major complaints seem to exist, and the thread appears to have grown to around nine pages.

Pages (2): 1 2 Next