F5F Stay Refreshed Hardware Desktop System halts during startup on splash screen after turning on XMP with dual RAM configurations (Trident Z + Ripjaws)

System halts during startup on splash screen after turning on XMP with dual RAM configurations (Trident Z + Ripjaws)

System halts during startup on splash screen after turning on XMP with dual RAM configurations (Trident Z + Ripjaws)

T
Thypolicon
Member
66
10-20-2022, 07:12 AM
#1
Details:
• System runs on Windows 10 Pro 64-bit
• Processor: Ryzen 7 5700X
• Motherboard: Gigabyte AORUS X470 (BIOS F63a – current version)
• Memory:
- 2×8GB G.Skill Trident Z @ 3200MHz
- 2×8GB G.Skill Ripjaws @ 3000MHz
- Grand total: 32GB (4×8GB)
• Graphics: NVIDIA RTX 2080 Ti
• Drive: Samsung 970 EVO NVMe SSD
• Power supply: EVGA 850W SuperNOVA Gold+ (fully modular)
• Overclocking: Not permitted except XMP enabled
• Troubleshooting note: Enabling XMP causes freezing at the Gigabyte splash screen, preventing BIOS or Windows access. No error alerts appear. VGA debug light may illuminate but GPU renders video correctly. Clearing CMOS restores normal boot with RAM defaulting to 2133MHz. Trident Z performs well with XMP at 3200MHz while Ripjaws is off. All four RAM modules installed, XMP still locks the system down.
T
Thypolicon
10-20-2022, 07:12 AM #1

Details:
• System runs on Windows 10 Pro 64-bit
• Processor: Ryzen 7 5700X
• Motherboard: Gigabyte AORUS X470 (BIOS F63a – current version)
• Memory:
- 2×8GB G.Skill Trident Z @ 3200MHz
- 2×8GB G.Skill Ripjaws @ 3000MHz
- Grand total: 32GB (4×8GB)
• Graphics: NVIDIA RTX 2080 Ti
• Drive: Samsung 970 EVO NVMe SSD
• Power supply: EVGA 850W SuperNOVA Gold+ (fully modular)
• Overclocking: Not permitted except XMP enabled
• Troubleshooting note: Enabling XMP causes freezing at the Gigabyte splash screen, preventing BIOS or Windows access. No error alerts appear. VGA debug light may illuminate but GPU renders video correctly. Clearing CMOS restores normal boot with RAM defaulting to 2133MHz. Trident Z performs well with XMP at 3200MHz while Ripjaws is off. All four RAM modules installed, XMP still locks the system down.

T
Texas1047
Posting Freak
889
10-20-2022, 08:48 AM
#2
Have you attempted to enable XMP using a 3200 profile? If yes, begin by enabling it with a 3000 profile. Should that fail, proceed to adjust the RAM speed and timing according to the specifications for a 3000MHz kit.
T
Texas1047
10-20-2022, 08:48 AM #2

Have you attempted to enable XMP using a 3200 profile? If yes, begin by enabling it with a 3000 profile. Should that fail, proceed to adjust the RAM speed and timing according to the specifications for a 3000MHz kit.

C
Celmunchie
Member
192
11-10-2022, 04:34 AM
#3
Using 3000 triggers the same problem—the system prevents manual access.
C
Celmunchie
11-10-2022, 04:34 AM #3

Using 3000 triggers the same problem—the system prevents manual access.

K
katnissgirl115
Member
153
11-10-2022, 05:47 AM
#4
You haven't used Gigabyte's BIOS before. Consider choosing "System Memory Multiplier" and type "32" right away. Also, have you tried booting using only the Ripjaws?
K
katnissgirl115
11-10-2022, 05:47 AM #4

You haven't used Gigabyte's BIOS before. Consider choosing "System Memory Multiplier" and type "32" right away. Also, have you tried booting using only the Ripjaws?