F5F Stay Refreshed Hardware Desktop Attempting to upgrade a 64GB Trident Z5 Neo to 8000 MHz memory speed

Attempting to upgrade a 64GB Trident Z5 Neo to 8000 MHz memory speed

Attempting to upgrade a 64GB Trident Z5 Neo to 8000 MHz memory speed

Pages (3): Previous 1 2 3
C
Craft_Mob
Member
73
06-19-2023, 09:38 AM
#21
Using two sticks might yield better outcomes than four. Doing two sets of quick runs can be quite challenging. That’s the way it is.
C
Craft_Mob
06-19-2023, 09:38 AM #21

Using two sticks might yield better outcomes than four. Doing two sets of quick runs can be quite challenging. That’s the way it is.

D
Dat_boi_cheif
Member
56
06-19-2023, 11:04 AM
#22
It operates at 8000 MHz but falls into what’s typically referred to as slow CL38, usually handling 38-38-38-84 patterns—similar to CL46 or above. Essentially you need to run at extremely high speeds (8000 MHz) and pause frequently due to latency. The wide latency keeps things stable but brings performance down to around 5200 MHz CL30 levels. If you measure timing directly, it’ll be significantly slower, likely around 7000 MT/s devices. You might achieve much faster results by adjusting for actual CL38 specs, though this would heavily tax the memory controller. Keep an eye on DDR5 behavior—if it enters desync or fails to run at intended speeds, it signals a potential issue. Lowering latency is key; otherwise you won’t reach the full 6000 MHz performance and may miss out on CPU gains. Some users have pushed to CL22, achieving solid improvements (1-2% in benchmarks) without major strain.
D
Dat_boi_cheif
06-19-2023, 11:04 AM #22

It operates at 8000 MHz but falls into what’s typically referred to as slow CL38, usually handling 38-38-38-84 patterns—similar to CL46 or above. Essentially you need to run at extremely high speeds (8000 MHz) and pause frequently due to latency. The wide latency keeps things stable but brings performance down to around 5200 MHz CL30 levels. If you measure timing directly, it’ll be significantly slower, likely around 7000 MT/s devices. You might achieve much faster results by adjusting for actual CL38 specs, though this would heavily tax the memory controller. Keep an eye on DDR5 behavior—if it enters desync or fails to run at intended speeds, it signals a potential issue. Lowering latency is key; otherwise you won’t reach the full 6000 MHz performance and may miss out on CPU gains. Some users have pushed to CL22, achieving solid improvements (1-2% in benchmarks) without major strain.

T
T___________T
Member
224
06-20-2023, 01:46 AM
#23
I requested a capture from HWiNFO's Memory Timings or ZenTimings screen to observe the memory controller's clock speed. It’s likely running at half speed, so you’d need to be above 7000 on the memory to compensate and match a properly tuned 6000 CL30 configuration.
T
T___________T
06-20-2023, 01:46 AM #23

I requested a capture from HWiNFO's Memory Timings or ZenTimings screen to observe the memory controller's clock speed. It’s likely running at half speed, so you’d need to be above 7000 on the memory to compensate and match a properly tuned 6000 CL30 configuration.

Pages (3): Previous 1 2 3