Ryzen memory support Duel Rank - 2 X F4-3200C14D-32GTZ Kit - 64GB - Overclock.net - An Overclocking Community

Forum Jump: 

Ryzen memory support Duel Rank - 2 X F4-3200C14D-32GTZ Kit - 64GB

Reply
 
Thread Tools
post #1 of 19 (permalink) Old 08-04-2017, 07:57 AM - Thread Starter
New to Overclock.net
 
SaiKamalDoss's Avatar
 
Join Date: May 2017
Location: Florida
Posts: 42
Rep: 4 (Unique: 4)
I have 2Kits of F4-3200C14D-32GTZ Kit and would like to share timing and some tips getting good memory speeds without errors.

I have tested 1Kit of 3200Mhz with some help from @harrysun on getting my Mobo boot back to desktop with lower Ohms setting on ProcODT_SM.

I was stuck at ProcODT_SM [96 ohm] for 3200mhz and even 3333mhz and changing it to any value will result in reboot loop.

Thank you @harrysun on CAD bus settings which really helped me tweak further.
Thanks to harrysun (Click to show)

Advanced \ AMD CBS \ DDR4 Common Options \ CAD Configuration
CAD Bus Driver Strenght User Controls = Manual
ClkDrvbStren = 40.0 Ohm
AddrCmdDrvStren = 20.0 Ohm
CsOdtDrvStren = 40.0 Ohm
CkeDrvStren = 40.0 Ohm

RttNom = Auto for 64GB and RZQ/3 for 32GB
RttWr = RZQ/3
RttPark = RZQ/1


Here are some settings that may help you.
Optimized Setting for 64GB 2 x F4-3200C14D-32GTZ Kit (Click to show)





64GBBest3200mhz3_setting.txt 19k .txt file


RttNom = Auto for 64GB and RZQ/3 for 32GB
RttWr = RZQ/3
RttPark = RZQ/1

3333Mhz 64GB No errors -
Optimized Setting 3333Mhz for 64GB 2 x F4-3200C14D-32GTZ Kit (Click to show)








Hope this helps and please do not post about other RAM kits or 16GB single Rank to avoid confusion. Lets keep this only for F4-3200C14D-32GB kit - smile.gif

Motherboard - ASUS C6H
Bios - 1501
Memory F4-3200C14D-32GTZ x 2
Stress test Tools : Prime 95 loop and techpowerup memtest
Attached Files
File Type: txt 64GBBest3200mhz3_setting.txt (18.9 KB, 234 views)

AMD Ryzen 1800x @ 4.05, EK waterblock
F4-3200C14D-32GTZ x 2 = 64GB,
Vega64 XSPC waterblock
Segate 2T + 5T + Samsung M.2.
LG 4K Freesync & Samsung 65KS8000 for gaming.

https://valid.x86.fr/njplmm
https://valid.x86.fr/asxytc

SKD007===================thumb.gif
SaiKamalDoss is offline  
Sponsored Links
Advertisement
 
post #2 of 19 (permalink) Old 08-04-2017, 09:32 AM
New to Overclock.net
 
harrysun's Avatar
 
Join Date: Dec 2014
Posts: 173
Rep: 36 (Unique: 16)
Note: As always, my current stable setup can be found in the signature!
Does memory speeds matter? (Click to show)
Configuration for F4-3200C14D-32GTZ @3333MT/s CL14-14-14-28-44 1.5T BIOS 1701.

My previous configuration with F4-3200C14D-32GTZ @3200MT/s CL14-13-13-26-42 1T 1.35000V BIOS 1701 can be found here.

I'm using G.Skill Trident Z DIMM Kit 2x16GB (F4-3200C14D-32GTZ):

(Created with Thaiphoon Burner Freeware Version Download)

AMD Ryzen R7 1800X, Stepping 1 Revision ZP-B1
CPU batch: UA 1734SUS (CPU exchanged since my last announcement for F4-3200C14D-32GTZ @3200MT/s CL14-13-13-26-42 1T 1.35000V)
ASUS ROG CROSSHAIR VI HERO
Motherboard Slots: DIMM_A2, DIMM_B2
  • BIOS Version: 1701 x64 AGESA 1.0.0.6b
  • Build Date: 09/22/2017
  • EC1 Version: MBEC-AM4-0311
  • EC2 Version: RGE2-AM4-0106

Toolchain used for testing CPU & RAM stability (Click to show)

Test protocol used to find stable settings can be downloaded here (Google Docs).
For all of you who want to see how find the right settings starts (Click to show)
Searching for the right settings is a quick and funny task, NOT. Here is my paper work before continue with Google Docs document:

I have to be careful with the RAM/DIMM temperature:
Quote:
Originally Posted by Esenel View Post

Quote:
Originally Posted by 1usmus View Post

I shot a jitter phenomenon on video. When the 52 degree memory module reaches the platform, errors appear. This video can be a huge scandal.

https://youtu.be/nrVbyg4Vstg
For me it looks exactly the same.
It is a reproducible phenomenon for me at 3466 Mhz CL14. At first I thought it was just my RAM not being capable of the OC, until I realized the errors just begin when the RAM is at 52.X°C.
Then I forced my fans to 100% during HCI Memtest and I passed the 400% without any error at ~47°C.


*) T_Sensor1 = Ambient temperature in the case


How stable is this setup: In a 30h run of Prime95 Blend 2048k-4096k one worker failed after 26h (Click to show)

*) T_Sensor1 = Ambient temperature in the case

Overview about settings F4-3200C14D-32GTZ @3333MT/s CL14-14-14-28-44 1.5T 1.41500V BIOS 1701 x64 AGESA 1.0.0.6b:
  • Advanced \ AMD CBS \ NBIO Common Options
    • CLDO_VDDP Control = 810
  • Advanced \ AMD CBS \ UMC Common Options \ DRAM Memory Mapping
    • BankGroupSwap = Auto (results automaticaly in Enabled)
    • BankGroupSwapAlt = Auto (results automaticaly in Disabled)
  • Extreme Tweaker
    • CPU SOC Voltage = Offset Mode
      • VDDSOC Offset Mode Sign = - (minus)
      • VDDSOC Voltage Override = 0.10625
    • DRAM Voltage = 1.41500
  • Extreme Tweaker \ DRAM Timing Control
    • DRAM ... = 14-14-14-14-28-44-5-8-30-4-12-10-Auto(0)-2-2-312-Auto(192)-Auto(132)-14-8-7-3-1-7-7-1-5-5-1
    • Cmd2T = 1T
    • Gear Down Mode = Enabled
    • Power Down Enabled = Auto (Auto = Enabled; Default) (I can not measure any change in latency with Power Down Enabled = Disabled)
      Resistance:
    • ProcODT_SM = 60.0 ohm
    • RttNom = RZQ/5
    • RttWr = RZQ/3
    • RttPark = RZQ/1
    • MemCadBus ClkDrvStren_SM = 30.0 Ohm
    • MemCadBus AddrCmdDrvStren_SM = 30.0 Ohm
    • MemCadBus CsOdtDrvStren_SM = 60.0 Ohm
    • MemCadBus CkeDrvStren_SM = 60.0 Ohm
  • Extreme Tweaker \ Tweaker's Paradise
    • VTTDDR Voltage = 0.70620
    • VDDP Voltage = Auto
    • VDDP Standby Voltage = Auto
  • Extreme Tweaker \ External Digi+ Power Control
    • DRAM VBoot Voltage = 1.41500




Setup:
Credits goes to @1usmus for Ryzen DRAM Calculator: Ryzen DRAM Calculator 0.9.9 v11 by 1usmus (Click to show)
Ryzen DRAM Calculator 0.9.9 v9 by 1usmus (Click to show)
Source of inspiration for 3333MT/s with F4-3200C14D-32GTZ (Click to show)
  • @The Stilt for the HQ B-die - 3333MHz "Safe" 1.350V settings: post #26178558
  • Post by @kaseki
  • Post by @Ramad/@kaseki (but @Ramad is using a different kit Patriot Viper Elite 2x8GB DR)
  • Post by @roybotnik
  • Post by @SaiKamalDoss
  • Post by @AlphaZero
  • Post by @R71800XSS
  • Post by @1usmus (but @1usmus is using a different kit F4-3000C14D-32GTZ)
    Quote:
    Originally Posted by 1usmus View Post

    I want to write a report on the latest tests 3333 dual rank I hope this helps many



    1. Memory is very sensitive to interference on the cad_bus. The decrease in the speed of response and switching of the phases of power help me. current power settings (Click to show)
    CPU Load-line Calibration [Level 4]
    CPU Current Capability [130%]
    CPU VRM Switching Frequency [Manual]
    CPU Voltage Frequency [300]
    CPU Power Duty Control [T.Probe]
    CPU Power Phase Control [Power Phase Response]
    Manual Adjustment [Regular]
    CPU Power Thermal Control [120]
    VDDSOC Load-line Calibration [Level 4]
    VDDSOC Current Capability [120%]
    VDDSOC Switching Frequency [Manual]
    Fixed VDDSOC Switching Frequency(KHz) [300]
    VDDSOC Phase Control [Optimized]
    DRAM Current Capability [120%]
    DRAM Power Phase Control [Extreme]
    DRAM Switching Frequency [Manual]
    Fixed DRAM Switching Frequency(KHz) [300]

    2. The most stable state of the system with an increase in frequency above 3200 is reached by CAD_BUS 30 30 40 60. At low values, there are a lot of mistakes and blue screens.
    CAD_BUS timings I did not touch, because the system did not start or gave a blue screen. Ramad rule (AddrCmdSetup = AddrCmdDrvStren ) not working on 3333 and 3466.I'm thinking of synchronizing these values is not worth it. I asked Elmor for information - he does not have it. I managed to run 3466 on these settings (20 40 20 + 30 30 40 24), even without a coldboot, but a lot of errors 8 in HCI 5.1.


    3. Rule VTTDDR (vdram * 0.5) not working for frequencies above 3200. Current value VTTDDR 0.69960 and vdram 1.410 (it must be 0,705, but it has errors)

    4. VDRAM. 3333 run even at 1.38, but only 2gb working without error, on 1.410 12-16gb works without error.

    5. Im trying to use Ramad CLDO_VDDP 425, works fine on 3200 and 3333, it turned out to reduce the voltage on SOC from 1.025 to 0.98. On 3466 not started. Voltage to other components could not be reduced, errors appear.

    6. VPP 2.5 - 2.52 greatly affects the stability of the system, has a wavy form, the above to lift the voltage is useless. PLL 1.77-1.83 also greatly affects the stability of the system. Step 0.01

    7. VDDP. Dual rank is very sensitive to this parameter, only 0,900 volts work perfectly, at 855 there are sometimes errors

    8. Rtt disable / rzq3 / rzq1 and rzq1 / rzq3 / rzq1 work better than rzq3 / rzq3 / rzq1.
    + procODT 68.8 = best couple smile.gif
    The worst performance was on procODT 80.

    9. tRAS tRC 28 42 there are errors with the code 2000000, removed them with tRAS tRC 30 44

    10. DRAM TUNE at a frequency above 3200 can not be touched, either the blue screen or the system is unstable

    probably did not forget anything
    all settings (Click to show)
    [2017/10/10 19:30:21]
    Ai Overclock Tuner [Manual]
    BCLK Frequency [100.0000]
    BCLK_Divider [Auto]
    Custom CPU Core Ratio [Auto]
    > CPU Core Ratio [38.00]
    Performance Bias [None]
    Memory Frequency [DDR4-3333MHz]
    Core Performance Boost [Disabled]
    SMT Mode [Enabled]
    EPU Power Saving Mode [Disabled]
    TPU [Keep Current Settings]
    CPU Core Voltage [Manual mode]
    - CPU Core Voltage Override [1.31875]
    CPU SOC Voltage [Manual mode]
    - VDDSOC Voltage Override [0.98750]
    DRAM Voltage [1.41000]
    1.8V PLL Voltage [Auto]
    1.05V SB Voltage [Auto]
    Target TDP [Auto]
    TRC_EOM [Auto]
    TRTP_EOM [Auto]
    TRRS_S_EOM [Auto]
    TRRS_L_EOM [Auto]
    TWTR_EOM [Auto]
    TWTR_L_EOM [Auto]
    TWCL_EOM [Auto]
    TWR_EOM [Auto]
    TFAW_EOM [Auto]
    TRCT_EOM [Auto]
    TREFI_EOM [Auto]
    TRDRD_DD_EOM [Auto]
    TRDRD_SD_EOM [Auto]
    TRDRD_SC_EOM [Auto]
    TRDRD_SCDLR_EOM [Auto]
    TRDRD_SCL_EOM [Auto]
    TWRWR_DD_EOM [Auto]
    TWRWR_SD_EOM [Auto]
    TWRWR_SC_EOM [Auto]
    TWRWR_SCDLR_EOM [Auto]
    TWRWR_SCL_EOM [Auto]
    TWRRD_EOM [Auto]
    TRDWR_EOM [Auto]
    TWRRD_SCDLR_EOM [Auto]
    Mem Over Clock Fail Count [2]
    DRAM CAS# Latency [14]
    DRAM RAS# to CAS# Read Delay [14]
    DRAM RAS# to CAS# Write Delay [14]
    DRAM RAS# PRE Time [14]
    DRAM RAS# ACT Time [30]
    Trc_SM [44]
    TrrdS_SM [6]
    TrrdL_SM [9]
    Tfaw_SM [34]
    TwtrS_SM [4]
    TwtrL_SM [12]
    Twr_SM [12]
    Trcpage_SM [Auto]
    TrdrdScl_SM [2]
    TwrwrScl_SM [2]
    Trfc_SM [277]
    Trfc2_SM [Auto]
    Trfc4_SM [Auto]
    Tcwl_SM [14]
    Trtp_SM [8]
    Trdwr_SM [7]
    Twrrd_SM [3]
    TwrwrSc_SM [Auto]
    TwrwrSd_SM [Auto]
    TwrwrDd_SM [Auto]
    TrdrdSc_SM [Auto]
    TrdrdSd_SM [Auto]
    TrdrdDd_SM [Auto]
    Tcke_SM [1]
    ProcODT_SM [68.6 ohm]
    Cmd2T [1T]
    Gear Down Mode [Auto]
    Power Down Enable [Disabled]
    RttNom [RZQ/1]
    RttWr [RZQ/3]
    RttPark [RZQ/1]
    MemAddrCmdSetup_SM [Auto]
    MemCsOdtSetup_SM [Auto]
    MemCkeSetup_SM [Auto]
    MemCadBusClkDrvStren_SM [30.0 Ohm]
    MemCadBusAddrCmdDrvStren_SM [30.0 Ohm]
    MemCadBusCsOdtDrvStren_SM [40.0 Ohm]
    MemCadBusCkeDrvStren_SM [60.0 Ohm]
    VTTDDR Voltage [0.69960]
    VPP_MEM Voltage [2.51500]
    DRAM CTRL REF Voltage on CHA [Auto]
    DRAM CTRL REF Voltage on CHB [Auto]
    VDDP Voltage [0.90000]
    VDDP Standby Voltage [0.90000]
    1.8V Standby Voltage [Auto]
    CPU 3.3v AUX [Auto]
    2.5V SB Voltage [Auto]
    DRAM R1 Tune [Auto]
    DRAM R2 Tune [Auto]
    DRAM R3 Tune [Auto]
    DRAM R4 Tune [Auto]
    PCIE Tune R1 [Auto]
    PCIE Tune R2 [Auto]
    PCIE Tune R3 [Auto]
    PLL Tune R1 [Auto]
    PLL reference voltage [Auto]
    T Offset [Auto]
    Sense MI Skew [Auto]
    Sense MI Offset [Auto]
    Promontory presence [Auto]
    Clock Amplitude [Auto]
    CPU Load-line Calibration [Level 4]
    CPU Current Capability [130%]
    CPU VRM Switching Frequency [Manual]
    CPU Voltage Frequency [300]
    CPU Power Duty Control [T.Probe]
    CPU Power Phase Control [Power Phase Response]
    Manual Adjustment [Regular]
    CPU Power Thermal Control [120]
    VDDSOC Load-line Calibration [Level 4]
    VDDSOC Current Capability [120%]
    VDDSOC Switching Frequency [Manual]
    Fixed VDDSOC Switching Frequency(KHz) [300]
    VDDSOC Phase Control [Optimized]
    DRAM Current Capability [120%]
    DRAM Power Phase Control [Extreme]
    DRAM Switching Frequency [Manual]
    Fixed DRAM Switching Frequency(KHz) [300]
    DRAM VBoot Voltage [1.41000]
    Security Device Support [Enable]
    TPM Device Selection [Discrete TPM]
    Erase fTPM NV for factory reset [Enabled]
    PSS Support [Enabled]
    NX Mode [Disabled]
    SVM Mode [Disabled]
    SATA Port Enable [Enabled]
    PT XHCI GEN1 [Auto]
    PT XHCI GEN2 [Auto]
    PT USB Equalization4 [Auto]
    PT USB Redriver [Auto]
    PT PCIE PORT 0 [Auto]
    PT PCIE PORT 1 [Auto]
    PT PCIE PORT 2 [Auto]
    PT PCIE PORT 3 [Auto]
    PT PCIE PORT 4 [Auto]
    PT PCIE PORT 5 [Auto]
    PT PCIE PORT 6 [Auto]
    PT PCIE PORT 7 [Auto]
    Onboard PCIE LAN PXE ROM [Enabled]
    AMD CRB EHCI Debug port switch [Disabled]
    Onboard LED [Disabled]
    Hyper kit Mode [Disabled]
    SATA Port Enable [Enabled]
    SATA Mode [AHCI]
    SMART Self Test [Enabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    Hot Plug [Disabled]
    ErP Ready [Disabled]
    Restore On AC Power Loss [Power Off]
    Power On By PCI-E/PCI [Disabled]
    Power On By RTC [Disabled]
    Super I/O Clock Skew [Auto]
    HD Audio Controller [Enabled]
    PCIEX4_3 Bandwidth [Auto]
    PCIEX16_1 Mode [Auto]
    PCIEX8_2 Mode [Auto]
    PCIEX4_3 Mode [Auto]
    M.2 Link Mode [GEN 3]
    SB Link Mode [Auto]
    Asmedia USB 3.1 Controller [Enabled]
    RGB LED lighting [Disabled]
    Intel LAN Controller [Disabled]
    USB Type C Power Switch for USB3.1_E1 [Auto]
    USB Type C Power Switch for USB3.1_EC2 [Auto]
    Network Stack [Disabled]
    Debug Port Table [Disabled]
    Debug Port Table 2 [Disabled]
    Device [WDC WD30EFRX-68EUZN0]
    Legacy USB Support [Enabled]
    XHCI Hand-off [Enabled]
    USB Mass Storage Driver Support [Enabled]
    Generic USB Flash Disk 0.00 [Auto]
    Generic-SD/MMC/MS/MSPRO 1.00 [Auto]
    USB3.1_E1 [Auto]
    USB3_1 [Enabled]
    USB3_2 [Enabled]
    USB3_3 [Enabled]
    USB3_4 [Enabled]
    USB3_5 [Auto]
    USB3_6 [Auto]
    USB3_7 [Auto]
    USB3_8 [Auto]
    USB3_9 [Auto]
    USB3_10 [Auto]
    USB2_11 [Auto]
    USB2_12 [Auto]
    USB2_13 [Auto]
    USB2_14 [Auto]
    USB_15 [Auto]
    USB_16 [Auto]
    CPU Temperature [Monitor]
    MotherBoard Temperature [Monitor]
    VRM Temperature [Monitor]
    PCH Temperature [Monitor]
    T_Sensor1 Temperature [Monitor]
    CPU Fan Speed [Monitor]
    Chassis Fan 1 Speed [Monitor]
    Chassis Fan 2 Speed [Monitor]
    Chassis Fan 3 Speed [Monitor]
    W_PUMP+ Speed [Monitor]
    CPU Optional Fan Speed [Monitor]
    AIO_PUMP Speed [Monitor]
    W_FLOW Speed [Monitor]
    W_IN Temperature [Monitor]
    W_OUT Temperature [Monitor]
    CPU Core Voltage [Monitor]
    3.3V Voltage [Monitor]
    5V Voltage [Monitor]
    12V Voltage [Monitor]
    CPU Q-Fan Control [Disabled]
    W_PUMP+ Control [Auto]
    Chassis Fan 1 Q-Fan Control [Auto]
    Chassis Fan 1 Q-Fan Source [CPU]
    Chassis Fan 1 Smoothing Up/Down Time [0 sec]
    Chassis Fan 1 Speed Low Limit [200 RPM]
    Chassis Fan 1 Profile [Standard]
    Chassis Fan 2 Q-Fan Control [Auto]
    Chassis Fan 2 Q-Fan Source [CPU]
    Chassis Fan 2 Smoothing Up/Down Time [0 sec]
    Chassis Fan 2 Speed Low Limit [200 RPM]
    Chassis Fan 2 Profile [Standard]
    Chassis Fan 3 Q-Fan Control [Auto]
    Chassis Fan 3 Q-Fan Source [CPU]
    Chassis Fan 3 Smoothing Up/Down Time [0 sec]
    Chassis Fan 3 Speed Low Limit [200 RPM]
    Chassis Fan 3 Profile [Standard]
    OnChip SATA Channel [Auto]
    OnChip SATA Type [AHCI]
    USB3_1 [Enabled]
    USB3_2 [Enabled]
    USB3_3 [Enabled]
    USB3_4 [Enabled]
    IR Config [RX & TX0 Only]
    SdForce18 Enable [Disabled]
    SD Mode configuration [AMDA]
    Uart 0 Enable [Enabled]
    Uart 1 Enable [Enabled]
    I2C 0 Enable [Enabled]
    I2C 1 Enable [Enabled]
    I2C 2 Enable [Disabled]
    I2C 3 Enable [Disabled]
    GPIO Devices Support [Auto]
    ESATA Port On Port 0 [Auto]
    ESATA Port On Port 1 [Auto]
    ESATA Port On Port 2 [Auto]
    ESATA Port On Port 3 [Auto]
    ESATA Port On Port 4 [Auto]
    ESATA Port On Port 5 [Auto]
    ESATA Port On Port 6 [Auto]
    ESATA Port On Port 7 [Auto]
    SATA Power On Port 0 [Auto]
    SATA Power On Port 1 [Auto]
    SATA Power On Port 2 [Auto]
    SATA Power On Port 3 [Auto]
    SATA Power On Port 4 [Auto]
    SATA Power On Port 5 [Auto]
    SATA Power On Port 6 [Auto]
    SATA Power On Port 7 [Auto]
    SATA Port 0 MODE [Auto]
    SATA Port 1 MODE [Auto]
    SATA Port 2 MODE [Auto]
    SATA Port 3 MODE [Auto]
    SATA Port 4 MODE [Auto]
    SATA Port 5 MODE [Auto]
    SATA Port 6 MODE [Auto]
    SATA Port 7 MODE [Auto]
    SATA Hot-Removable Support [Auto]
    SATA 6 AHCI Support [Auto]
    Int. Clk Differential Spread [Auto]
    SATA MAXGEN2 CAP OPTION [Auto]
    SATA CLK Mode Option [Auto]
    Aggressive Link PM Capability [Auto]
    Port Multiplier Capability [Auto]
    SATA Ports Auto Clock Control [Auto]
    SATA Partial State Capability [Auto]
    SATA FIS Based Switching [Auto]
    SATA Command Completion Coalescing Support [Auto]
    SATA Slumber State Capability [Auto]
    SATA MSI Capability Support [Auto]
    SATA Target Support 8 Devices [Auto]
    Generic Mode [Auto]
    SATA AHCI Enclosure [Auto]
    SATA SGPIO 0 [Disabled]
    SATA SGPIO 1 [Disabled]
    SATA PHY PLL [Auto]
    AC/DC Change Message Delivery [Disabled]
    TimerTick Tracking [Auto]
    Clock Interrupt Tag [Enabled]
    EHCI Traffic Handling [Disabled]
    Fusion Message C Multi-Core [Disabled]
    Fusion Message C State [Disabled]
    SPI Read Mode [Auto]
    SPI 100MHz Support [Auto]
    SPI Normal Speed [Auto]
    SPI Fast Read Speed [Auto]
    SPI Burst Write [Auto]
    I2C 0 D3 Support [Auto]
    I2C 1 D3 Support [Auto]
    I2C 2 D3 Support [Auto]
    I2C 3 D3 Support [Auto]
    UART 0 D3 Support [Auto]
    UART 1 D3 Support [Auto]
    SATA D3 Support [Auto]
    EHCI D3 Support [Auto]
    XHCI D3 Support [Auto]
    SD D3 Support [Auto]
    S0I3 [Auto]
    Chipset Power Saving Features [Enabled]
    SB Clock Spread Spectrum [Auto]
    SB Clock Spread Spectrum Option [-0.375%]
    HPET In SB [Auto]
    MsiDis in HPET [Auto]
    _OSC For PCI0 [Auto]
    USB Phy Power Down [Auto]
    PCIB_CLK_Stop Override [0]
    USB MSI Option [Auto]
    LPC MSI Option [Auto]
    PCIBridge MSI Option [Auto]
    AB MSI Option [Auto]
    SB C1E Support [Auto]
    SB Hardware Reduced Support [Auto]
    GPP Serial Debug Bus Enable [Auto]
    IOMMU [Auto]
    Remote Display Feature [Auto]
    Gnb Hd Audio [Auto]
    PSPP Policy [Auto]
    Memory Clock [Auto]
    Bank Interleaving [Enabled]
    Channel Interleaving [Enabled]
    Memory Clear [Disabled]
    Fast Boot [Enabled]
    Next Boot after AC Power Loss [Normal Boot]
    Boot Logo Display [Disabled]
    POST Report [1 sec]
    Boot up NumLock State [Enabled]
    Wait For 'F1' If Error [Enabled]
    Option ROM Messages [Enabled]
    Interrupt 19 Capture [Disabled]
    Setup Mode [Advanced Mode]
    Launch CSM [Enabled]
    Boot Device Control [UEFI and Legacy OPROM]
    Boot from Network Devices [Legacy only]
    Boot from Storage Devices [Legacy only]
    Boot from PCI-E Expansion Devices [Legacy only]
    OS Type [Other OS]
    Setup Animator [Disabled]
    Load from Profile [1]
    Profile Name []
    Save to Profile [1]
    CPU Core Voltage [Auto]
    VDDSOC Voltage [Auto]
    1.8V PLL Voltage [Auto]
    BCLK Frequency [Auto]
    CPU Ratio [Auto]
    Bus Interface [PCIEX16/X8_1]
    Quote:
    Originally Posted by Ramad View Post

    CAD Bus Timings are at Auto. Drivers impedance are 20 - 20 - 40 - 60

    I think it's my fault for not giving more detail on what I meant by systematic, here are the details.

    I would do it like this:

    Manipulating CLDO

    Constants:
    • Getting the processor out of the equation:
      I would set the processor to it's default frequency that's 3.6GHz, give a voltage at 1.25V, disable CPB and SOC voltage to 1.05V. (The CPU now is a constant and have no impact on the outcome).

    • Getting the RAM out of the equation:
      I have my RAM frequency at 3200MT/s with my stable timings (that I have been running for over a month and know is stable), voltage at 1.37, VTTDDR at 1.38/2, CAD impedance at 20 - 20 - 40 - 60(40). (The RAM now have no impact on the outcome).

    • Getting PROCODT of the equation:
      I would set it to the value that I have been using with my stable RAM settings. (PROCODT now have no impact on the outcome).



    1 Variable: Always 1 variable, never more than 1 variable.

    My 1 Variable is CLDO_VDDP: This is my variable, the value that I would change and see the outcome and its effect on system stability.

    Example: trigger 900mV
    • Trigger CLDO_VDDP voltage at 900mV
    • Boot to OS, start a a test for 30 min., if no error, then I would drop the RAM and VTTDDR to the voltage my RAM is rated at, that's 1.35V and VTTDDR 1.36V/2 (the board overvolts the RAM rail by 0.016V), then boot to OS and run a test again.
    • If CLDO_VDDP at 900mV allows me to drop the RAM voltage to the rated voltage, then it's a good value.

    Collecting DATA: This is where I look at the details and see which value had the least hiccups.

    Possible Outcome: More than 1 good CLDO_VDDP value

    The right CLDO_VDDP value is the value that lets me drop the RAM, CPU and SOC voltages without sacrificing stability.

    Manipulating PROCODT is the same way, but CLDO_VDDP must be a constant, means you choose a right value and stick with it.

    This is what I meant when I wrote systematic. smile.gif
    Quote:
    Originally Posted by 1usmus View Post

    I would reconfigure the power system with an emphasis on overclocking the processor + the current limitation on SOC/DRAM will allow for greater stability for system smile.gif

    CPU Load-line Calibration [Level 3]
    CPU Current Capability [130%]
    CPU VRM Switching Frequency [Auto]
    VRM Spread Spectrum [Disabled]
    Active Frequency Mode [Disabled]
    CPU Power Duty Control [Extreme]
    CPU Power Phase Control [Power Phase Response]
    Manual Adjustment [Ultra Fast]

    VDDSOC Load-line Calibration [Level 3]
    VDDSOC Current Capability [120%]
    VDDSOC Switching Frequency [Auto]
    VDDSOC Phase Control [Optimized]
    DRAM Current Capability [100%]
    DRAM Power Phase Control [Extreme]
    DRAM Switching Frequency [Manual]
    Fixed DRAM Switching Frequency(KHz) [300]

    by the way i come back again on 3101, he is pleasant to me more. At 1701 there are problems and a long start
  • About CLOD_VDDP:
    Quote:
    Originally Posted by The Stilt View Post

    Few suggestions regarding the controls allowed by the new (AGESA 1.0.0.6) bioses:

    - In case you run into a MEMCLK hole, adjust the CLDO_VDDP voltage. The VDDP adjustment window is rather narrow, usually < 100mV. Also the window is neither static or linear. Because of that the setting which is optimal for frequency x might not be optimal for frequency y. Also since the window is not linear, but more of a wave form e.g. VDDP at 975mV might work perfectly fine whereas 980mV won't be able to train the memory. The MEMCLK hole is both CPU and DRAM specific, but so far I haven't seen any evidence it being motherboard specimen specific. This means that swapping either the CPU or the memory (to another CPU or modules) might either introduce or the get rid of the MEMCLK hole. Personally I have 100% success rate in clearing the MEMCLK hole with CLDO_VDDP adjustment (1x R7 1700, 1x R7 1800X and 2x R7 1700X). All of the MEMCLK holes on these CPUs have been cleared using 937 - 1000mV setting. Do note that when you change the CLDO_VDDP voltage, saving the bios settings will not put the new CLDO_VDDP voltage into effect, since the CLDOs can only be programmed during a cold reset or a cold boot. Because of that I suggest that you save the new CLDO_VDDP value and press the reset button before the system has booted up again. Also CLDO_VDDP must be at least 100mV lower than the DRAM voltage at all times. Regardless it is not recommended to exceed 1050mV.

    - For Samsung B-die dual rank modules I suggest that 96Ohm ProcODT is used.
    Quote:
    Originally Posted by 1usmus View Post

    I decided to write a small article explaining why some systems work fine at 3200+ and others do not at all

    Influence of СLDO_VDDP on MEMCLK "holes"

    CLDO_VDDP is a voltage regulator for the module (physical interface) of encoding and decoding of the transmitted and received data stream. The purpose of coding is to simplify the process of restoring the data stream of the receiver. It determines the signals, signal ratios and time parameters necessary for transferring control information, reading and writing data to DRAM devices. In plain language, CLDO_VDDP is the voltage that regulates the memory access at a certain frequency. "Hole" in turn - the frequency gap on which the memory controller can operate with our RAM.

    Consider this simple picture:




    It shows 3 identical systems (motherboard + RAM + processor). All 3 systems were overclocked and received the following results:

    1) The system was perfectly dispersed to a frequency of 3333 MHz
    2) The system was accelerated to 2933
    3) The system did not start at all

    If all systems are the same, why such results? Let's understand. The bottom line is that each memory controller (IMC) has its own technical characteristics ("voltage" and time) and at the same voltage / frequency it will behave differently, namely it will have different access to memory. Red marked our MEMCLK holes, these are the very hole-mediators through which our memory controller communicates with RAM, and if there is no hole in the frequency range chosen by us - the system does not start or start, but the memory runs with errors. At you I think there was a question as these holes to move and expand - all is very simple, voltage CLDO_VDDP allows to spend the given manipulations. The only difficulty is that these holes can not be mathematically calculated. A vivid example of CLDO_VDDP 866 which is magical for many. The hole of this voltage is in the region of 3300-3500 MHz, but again not for all systems. As shown by our internal tests, not all of it works, I repeat all the IMC are different and require a different voltage CLDO_VDDP to achieve the same frequency.

    In view of the fact that the shape of the voltage CLDO_VDDP is wave, the minimum voltage change can drastically change the stability of the system. The voltage step is 1 mv. Borders from 700 to 975.

    I also want to publish a list of CLDO_VDDP, which can help stabilize your memory

    CLDO_VDDP list (volts) (Click to show)
    0.562
    0.568
    0.573
    0.579
    0.585
    0.590
    0.596
    0.601
    0.607
    0.613
    0.618
    0.624
    0.630
    0.635
    0.641
    0.646
    0.652
    0.658
    0.663
    0.669
    0.675
    0.680
    0.686
    0.691
    0.697
    0.703
    0.708
    0.714
    0.720
    0.725
    0.731
    0.736
    0.742
    0.748
    0.753
    0.759
    0.765
    0.770
    0.776
    0.781
    0.787
    0.793
    0.798
    0.804
    0.810
    0.815
    0.821
    0.826
    0.832
    0.838
    0.843
    0.849
    0.855
    0.860
    0.866
    0.871
    0.877
    0.883
    0.888
    0.894
    0.900
    0.905
    0.911
    0.916
    0.922
    0.928
    0.933
    0.939
    0.945
    0.950
    0.956
    0.961
    0.967
    0.973

    upd 1 : small addition-explanation

    The curve represente your dram voltage signal, changing cldo_vddp move back and forth this signal compared to your available frequency setting.
    The purpose to changing it is to make the curve crossed your setting line on the appropriate frequency setting.
    Whereas the zone where there is no curve present is a memory hole .
    Depending of your IMC or RAM the curve can vary in lenght or thickness.



    only the form is more oblate, in dozens of times
  • About DRAM Voltage and VTTDDR Voltage:
    Quote:
    Originally Posted by 1usmus View Post

    I want to share with you the results of my testing smile.gif

    In most cases, the memory works incorrectly because of incorrect voltage DRAM and VTT_DDR
    On this picture in green I selected the best options

    do not argue, they are not universal, to calculate their personal voltages, use my calculator, the tab VDRAM / VTT DDR Calculator

    Quote:
    Originally Posted by 1usmus View Post

    Quote:
    Originally Posted by Ramad View Post

    RAM and VTTDDR voltages

    I had time last week to take a look at a few things with BIOS version 1403. Among other things, I tried to figure out the reason for that random error we all know, which can hit my system with no warning, it could while running OCCT or IBT right after few hours of HCI memtest. Starting with a look at the RAM voltage I chose in the BIOS and the reported/read RAM voltage by the BIOS and HWINFO I was certain that the motherboard is applying higher RAM voltage than the value I choose.

    I did experiment with VTTDDR in earlier BIOS versions (9945/9943 and older) which did not provide CAD settings, that could help stabilize the system, however, with CAD and Rtt on 1401/1403, better stability is possible, but that random error still show up now and then.

    This week I tried configuring RAM voltages based on BIOS and HWINFO readings. In all of the tests is the following settings used:


    • CPU voltage: 1.238V + 0.1375V
    • SOC: 1.02500V
    • 1.8V PLL: 1.86V
    • CLDO_VDDP: 868mv
    • VPP: 0.960V
    • CAD: 20 -20 -40 - 60
    • Rtt: Disabled - RZQ/3 - RZQ/1
    • RAM voltage: As read by the BIOS/HWINFO
    • VTTDDR: 0.5 x RAM voltage (BIOS value and read value)
    • RAM tested: 12 GiB


    - Starting with default VTTDDR voltage = 0.6732V @1.35V set in the BIOS and read as 1.373V by BIOS and software: FAIL with 2 errors within 6 min.
    Warning: Spoiler! (Click to show)





    - Lowering RAM voltage to 1.335V will result the BIOS/software to read it at 1.352V, VTTDDR voltage kept at 0.6732V: PASS for more than 1½ hour and 300%.
    Warning: Spoiler! (Click to show)



    - Raising the RAM voltage to 1.35V will result the BIOS/software to read the voltage at 1.373V, VTTDDR voltage is raised to 0.6798V: FAIL with 1 error within 1 min.
    Warning: Spoiler! (Click to show)



    - RAM voltage kept at 1.35V, read as 1.373V by BIOS/software, VTTDDR voltage is raised to 0.6864V: PASS with more than 1½ hour and 300%.
    Warning: Spoiler! (Click to show)



    What does it mean?:

    I can only talk about my hardware and my experience with the BIOS. What it means for me is, VTTDDR needs to be tweeked based on BIOS/software read RAM voltages and not the value I test in the BIOS, means if I test 1.35V and the BIOS/software report it 1.373V, then VTTDDR should be 0.5 x 1.373V = 0.6864V and so on.

    What it does mean for you is based on your experience with your hardware, and if you are suffering of that random error, then this may be a solution for you too. But if your RAM does not care about the balance between RAM and VTTDDR voltages and you are content with your results, then this is not for you. smile.gif

    Edit: Corrections + new results.
Attached Files
File Type: txt harrysun41_3600_3333CL14_setting.txt (19.8 KB, 72 views)
File Type: zip harrysun41_UEFI1701_3600_3333CL14.zip (530.5 KB, 26 views)
File Type: zip harrysun41_3600_3333CL14_UEFI1701_CMO.zip (1.0 KB, 17 views)

AMD R7 1800X UA 1734SUS @4GHz/1.375V : ASUS Crosshair VI Hero BIOS 6401 AGESA PinnaclePI-1.0.0.6 : G.Skill Trident Z 2x16GB dual-rank (F4-3200C14D-32GTZ) @3266MT/s CL14-14-14-30-44 1.5T = Configuration: http://bit.ly/349w5L4 = Test report: http://bit.ly/2pUjEnS = CPU OC: http://bit.ly/2PIOElt
My Ryzen Star
(19 items)
CPU
AMD Ryzen 7 1800X UA 1734SUS
Motherboard
ASUS ROG Crosshair VI Hero
GPU
ASUS ROG Strix GeForce GTX 1080 Ti OC
RAM
F4-3200C14D-32GTZ G.Skill TridentZ 2x16GB dual-rank
Hard Drive
Samsung SSD 960 EVO 1TB, M.2
Hard Drive
Samsung SSD 850 EVO 1TB, SATA
Hard Drive
Western Digital WD Red Pro 6TB, 3.5", SATA 6Gb/s
Optical Drive
Plextor PX-LB950SA (BluRay)
Power Supply
Seasonic Prime Titanium 750W ATX 2.4
Cooling
Noctua NH-D15 SE-AM4
Cooling
5x Noctua NF-A14 industrialPPC-2000 PWM, 140mm
Case
Fractal Design Define R5 Blackout Edition w/ Window, silient
Case
4x BitFenix Alchemy 2.0 Magnetic 30cm, 15 LED RGB (BFA-RGB-30MK15N-RP)
Case
CableMod SE-Series XP2/XP3/KM3/FL2 cable kit for Power Supplies, white (CM-SS3-FKIT-KW)
Operating System
Windows 10
Monitor
NEC MultiSync PA301W, 30"
Keyboard
Cooler Master CM Storm Quick Fire TK, MX-Brown, USB, DE
Mouse
Roccat Kone Aimo, USB (ROC-11-815-BK)
Audio
FiiO K3
▲ hide details ▲
harrysun is offline  
post #3 of 19 (permalink) Old 08-04-2017, 09:33 AM
New to Overclock.net
 
neur0cide's Avatar
 
Join Date: Jun 2017
Location: Germany
Posts: 138
Rep: 13 (Unique: 11)
@ SaiKamalDoss
  1. Which motherboard and BIOS version are you using?
  2. How do you test stability?
  3. Is there a reason why you are disabling BankGroupSwap and enabling BGS alt? This contradicts recommendations by the Stilt.
  4. What's the difference between the three settings for 3200 MT/s? I compared the first and third dump file and the only difference I could find was that a bunch of subtimings was left on Auto in file 1. So there's no real difference that I can spot.
  5. According to your dump files your DriveStrength values are on Auto. Above you state, that you are using 40-20-40-40. Which is true?
  6. Have you tried tRDRDSCL and tWRWRSCL on 2? This will give you a significant performance boost.
  7. Your 3333 MT/s setting is missing the dump file. Anything special about those settings, since I can't get my F4-3200C14D-32GTZ to 3333?

I am running a kit of F4-3200C14D-32GTZ on my Crosshair VI Hero (BIOS 1401) with the following timings:



VDIMM = 1.35V
VDDSOC = 1.1V
ProcODT = 60 Ohm
RttNom = RZQ/3
RttWr = RZQ/3
RttPark = RZQ/1
DriveStrength values = Auto


This is one half of a quad kit. I sold the other two modules, but had briefly tried to make a all four work at 3200 MT/s to no avail. So congrats on your success.

AMD Ryzen 5 1700 (stock) -- ASUS ROG Crosshair VI Hero -- Arctic Liquid Freezer 240
4 x 8GB G.SKILL Samsung B-Die 3533-14-15-15-15-30-48-1T (GD on) 1.405v
2 x 16GB G.SKILL F4-3200C15D-32GTZ Samsung B-Die DR 3366-14-14-14-14-28-44-1T (GD on) 1.375v
KFA² GeForce GTX 1070 EX 8GB -- SSM Samsung SM951 500GB -- bunch of HDDs
PSU Corsair AX650 -- Phanteks Enthoo Evolv ATX TG -- Windows 10 Pro x64
neur0cide is offline  
Sponsored Links
Advertisement
 
post #4 of 19 (permalink) Old 08-06-2017, 01:42 PM - Thread Starter
New to Overclock.net
 
SaiKamalDoss's Avatar
 
Join Date: May 2017
Location: Florida
Posts: 42
Rep: 4 (Unique: 4)
Quote:
Originally Posted by neur0cide View Post

@ SaiKamalDoss
  1. Which motherboard and BIOS version are you using?
  2. How do you test stability?
  3. Is there a reason why you are disabling BankGroupSwap and enabling BGS alt? This contradicts recommendations by the Stilt.
  4. What's the difference between the three settings for 3200 MT/s? I compared the first and third dump file and the only difference I could find was that a bunch of subtimings was left on Auto in file 1. So there's no real difference that I can spot.
  5. According to your dump files your DriveStrength values are on Auto. Above you state, that you are using 40-20-40-40. Which is true?
  6. Have you tried tRDRDSCL and tWRWRSCL on 2? This will reduce performance significant .
  7. Your 3333 MT/s setting is missing the dump file. Anything special about those settings, since I can't get my F4-3200C14D-32GTZ to 3333?

I am running a kit of F4-3200C14D-32GTZ on my Crosshair VI Hero (BIOS 1401) with the following timings:



VDIMM = 1.35V
VDDSOC = 1.1V
ProcODT = 60 Ohm
RttNom = RZQ/3
RttWr = RZQ/3
RttPark = RZQ/1
DriveStrength values = Auto


This is one half of a quad kit. I sold the other two modules, but had briefly tried to make a all four work at 3200 MT/s to no avail. So congrats on your success.

I have updated the information on the main post regarding Bios version and stress test tools used. There is difference when we have 64GB of 2 kits.

RttNom = RZQ/3 for 1kit will boot, Auto need to be selected for 2kits or it wont boot.
RttWr = RZQ/3
RttPark = RZQ/1

[*] According to your dump files your DriveStrength values are on Auto. Above you state, that you are using 40-20-40-40. Which is true?

I am using 40-20-40-40 given by harrysun and only using that I can go down to 53.3ohms and if it is set to auto, it wont boot if I dont select 96ohms. I dont think you can see AMD CBS settings in that file as it wont export those for some reason.

[*] Have you tried tRDRDSCL and tWRWRSCL on 2? This will give you a significant performance boost.

I can run 2 if I run lose timing, If the timing is tight. then i end up getting errors. .

Sorry for the delay. I hate restarting computer with my HDD and I ended up ordering a 960 m.2.. I will install it and it will be easy for me to reboot. Will try out tRDRDSCL and tWRWRSCL on 2 and will update.. edit: update ( it is working but transfer rate went from 49k to 33 to 36k) bad performance.

[*] Is there a reason why you are disabling BankGroupSwap and enabling BGS alt? This contradicts

It's for stability and system won't boot with the timing if you don't set it the way I have for 64GB.

Mind you, 32GB 1Kit timing wont work with 64GB 2x Kit..

AMD Ryzen 1800x @ 4.05, EK waterblock
F4-3200C14D-32GTZ x 2 = 64GB,
Vega64 XSPC waterblock
Segate 2T + 5T + Samsung M.2.
LG 4K Freesync & Samsung 65KS8000 for gaming.

https://valid.x86.fr/njplmm
https://valid.x86.fr/asxytc

SKD007===================thumb.gif
SaiKamalDoss is offline  
post #5 of 19 (permalink) Old 08-15-2017, 07:14 AM
New to Overclock.net
 
Taylor121's Avatar
 
Join Date: Oct 2014
Posts: 52
Rep: 1 (Unique: 1)
Thanks for the thread.

Taylor121 is offline  
post #6 of 19 (permalink) Old 09-03-2017, 04:07 AM
New to Overclock.net
 
boooo's Avatar
 
Join Date: Aug 2017
Posts: 4
Rep: 0
Quote:
Originally Posted by SaiKamalDoss View Post

I have 2Kits of F4-3200C14D-32GTZ Kit and would like to share timing and some tips getting good memory speeds without errors.

I have tested 1Kit of 3200Mhz with some help from @harrysun on getting my Mobo boot back to desktop with lower Ohms setting on ProcODT_SM.

I was stuck at ProcODT_SM [96 ohm] for 3200mhz and even 3333mhz and changing it to any value will result in reboot loop.

Thank you @harrysun on CAD bus settings which really helped me tweak further.
Thanks to harrysun (Click to show)

Advanced \ AMD CBS \ DDR4 Common Options \ CAD Configuration
CAD Bus Driver Strenght User Controls = Manual
ClkDrvbStren = 40.0 Ohm
AddrCmdDrvStren = 20.0 Ohm
CsOdtDrvStren = 40.0 Ohm
CkeDrvStren = 40.0 Ohm

RttNom = Auto for 64GB and RZQ/3 for 32GB
RttWr = RZQ/3
RttPark = RZQ/1


Here are some settings that may help you.
Optimized Setting for 64GB 2 x F4-3200C14D-32GTZ Kit (Click to show)





64GBBest3200mhz3_setting.txt 19k .txt file


RttNom = Auto for 64GB and RZQ/3 for 32GB
RttWr = RZQ/3
RttPark = RZQ/1

3333Mhz 64GB No errors -
Optimized Setting 3333Mhz for 64GB 2 x F4-3200C14D-32GTZ Kit (Click to show)








Hope this helps and please do not post about other RAM kits or 16GB single Rank to avoid confusion. Lets keep this only for F4-3200C14D-32GB kit - smile.gif

Motherboard - ASUS C6H
Bios - 1501
Memory F4-3200C14D-32GTZ x 2
Stress test Tools : Prime 95 loop and techpowerup memtest

Also interesting in 64gb.

Are you running two separate kits 2X16 or one 4X16 64gb kit?

If two separate kits, no any issues with compatibility of two different kits?

Thanks!
boooo is offline  
post #7 of 19 (permalink) Old 09-04-2017, 07:27 PM - Thread Starter
New to Overclock.net
 
SaiKamalDoss's Avatar
 
Join Date: May 2017
Location: Florida
Posts: 42
Rep: 4 (Unique: 4)
Quote:
Originally Posted by boooo View Post

Also interesting in 64gb.

Are you running two separate kits 2X16 or one 4X16 64gb kit?

If two separate kits, no any issues with compatibility of two different kits?

Thanks!

Yes I bought the first kit when I bought Ryzen at the time of release and the second kit a day before I posted this thread.

AMD Ryzen 1800x @ 4.05, EK waterblock
F4-3200C14D-32GTZ x 2 = 64GB,
Vega64 XSPC waterblock
Segate 2T + 5T + Samsung M.2.
LG 4K Freesync & Samsung 65KS8000 for gaming.

https://valid.x86.fr/njplmm
https://valid.x86.fr/asxytc

SKD007===================thumb.gif
SaiKamalDoss is offline  
post #8 of 19 (permalink) Old 12-23-2017, 01:38 AM
New to Overclock.net
 
harrysun's Avatar
 
Join Date: Dec 2014
Posts: 173
Rep: 36 (Unique: 16)
deleted

AMD R7 1800X UA 1734SUS @4GHz/1.375V : ASUS Crosshair VI Hero BIOS 6401 AGESA PinnaclePI-1.0.0.6 : G.Skill Trident Z 2x16GB dual-rank (F4-3200C14D-32GTZ) @3266MT/s CL14-14-14-30-44 1.5T = Configuration: http://bit.ly/349w5L4 = Test report: http://bit.ly/2pUjEnS = CPU OC: http://bit.ly/2PIOElt
My Ryzen Star
(19 items)
CPU
AMD Ryzen 7 1800X UA 1734SUS
Motherboard
ASUS ROG Crosshair VI Hero
GPU
ASUS ROG Strix GeForce GTX 1080 Ti OC
RAM
F4-3200C14D-32GTZ G.Skill TridentZ 2x16GB dual-rank
Hard Drive
Samsung SSD 960 EVO 1TB, M.2
Hard Drive
Samsung SSD 850 EVO 1TB, SATA
Hard Drive
Western Digital WD Red Pro 6TB, 3.5", SATA 6Gb/s
Optical Drive
Plextor PX-LB950SA (BluRay)
Power Supply
Seasonic Prime Titanium 750W ATX 2.4
Cooling
Noctua NH-D15 SE-AM4
Cooling
5x Noctua NF-A14 industrialPPC-2000 PWM, 140mm
Case
Fractal Design Define R5 Blackout Edition w/ Window, silient
Case
4x BitFenix Alchemy 2.0 Magnetic 30cm, 15 LED RGB (BFA-RGB-30MK15N-RP)
Case
CableMod SE-Series XP2/XP3/KM3/FL2 cable kit for Power Supplies, white (CM-SS3-FKIT-KW)
Operating System
Windows 10
Monitor
NEC MultiSync PA301W, 30"
Keyboard
Cooler Master CM Storm Quick Fire TK, MX-Brown, USB, DE
Mouse
Roccat Kone Aimo, USB (ROC-11-815-BK)
Audio
FiiO K3
▲ hide details ▲
harrysun is offline  
post #9 of 19 (permalink) Old 12-25-2017, 05:49 AM - Thread Starter
New to Overclock.net
 
SaiKamalDoss's Avatar
 
Join Date: May 2017
Location: Florida
Posts: 42
Rep: 4 (Unique: 4)
What was deleted ?

AMD Ryzen 1800x @ 4.05, EK waterblock
F4-3200C14D-32GTZ x 2 = 64GB,
Vega64 XSPC waterblock
Segate 2T + 5T + Samsung M.2.
LG 4K Freesync & Samsung 65KS8000 for gaming.

https://valid.x86.fr/njplmm
https://valid.x86.fr/asxytc

SKD007===================thumb.gif
SaiKamalDoss is offline  
post #10 of 19 (permalink) Old 02-26-2018, 09:10 PM
New to Overclock.net
 
Join Date: Feb 2018
Posts: 1
Rep: 0
hey all need some input
I run an amd set up
Motherboard=ASUS Crosshair vi hero
Processer=AMD Ryzen 1800x
Processer cooling =Thermaltake aio 360 rgb
DRAM=G.SKILLS Trident z RGB 3200mhz 64 gig kit
and my son has the same set up except he has a 1700x so my question how come my ram doesnt run at 3200mhz no matter what I do or tweek ive tryed bios evereything .when I built my son pcs it was bios dead I had to force bios to update to get his pc to boot(post) .and my pc booted(posted) up no issues...but yet his ram runs at 3200mhz and mine is bare 2667mhz we both run 64 gigs of ram .the same type of ram but his timmings are cl14 and mine are cl 15.
kozHITNRUN is offline  
Reply

Quick Reply
Message:
Options

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off