Overclock.net banner
1 - 20 of 3269 Posts

·
Meddling user
Joined
·
7,423 Posts
Discussion Starter · #1 · (Edited)
Notice: OP under reconstruction as forum change has borked it for editing/links/attachments. Any images to see at full size open in new tab.

Notice: Some boards have older firmware for the onboard OLED/AURA, which can cause some strange issues. Update to the latest version, V1.00.13 link. Run the .exe from within Windows
Super IO chip monitoring data being stuck and/or affecting fan header PWM is now fixed. This fix is "two fold" fix, it requires UEFI with ASUS WMI implementation and applications accessing Super IO chip must also use this, otherwise adverse effects will occur to fan header PWM.

UEFI 0001 (Superseded see UEFI spoiler in OP) found in this post is first publicly available beta with this implementation. Within HWINFO the heading named by motherboard model will change to ASUS WMI, readings with (VRM) will more accurately reflect actual voltages.

Updated software versions supporting ASUS WMI:

- HWInfo v5.88 or later
- HWMonitor Beta: http://download.cpuid.com/betas/hwm_b17.zip
- SIV 5.32 or later
- CPU-Z Beta v1.86.1 or later
- AIDA64 v5.98.4800 or later

Note: CPUID SW links, as of date of update to OP, are 404 :( .


Last update date:- 23/02/19
Last update:- Added info on UEFI 1701, link for electrified's ASUS WMI support for Linux HWMON (lmsensors).

ASUS ROG Zenith Extreme X399 AMD Threadripper
Overclocking / Support


ASUS Motherboards Microcode Update for Meltdown and Spectre, news link

UEFI (listing as latest at top)

Some older post links broken due to forum change, will be sorted ASAP

UEFI 1701 - Download from official support page, has ASUS WMI, AGESA 1.1.0.2, for other info see this post.

Modded UEFI 1601 with ASUS WMI by Elmor - see this post for further info/download link.

UEFI 1601 - see this post for further info/download link.

UEFI 1501 - see this post for further info/download link.

UEFI 0001 - see this post for further info/download link.

UEFI 1402 - see this post for further info/download link.

UEFI 9952 - see this post for further info/download link.

UEFI 1003 - see this post for further info/download link.

UEFI 9931 - see this post for further info/download link.

UEFI 1002 - see this post for further info/download link.

UEFI 0020 - see this post for further info/download link.

UEFI 1001 - see this post for further info/download link.

UEFI 0002 - see this post for further info and discussion in thread.

View attachment ROG-ZENITH-EXTREME-ASUS-0002.zip

UEFI 0001 - see this post for further info and discussion in thread.

View attachment ROG-ZENITH-EXTREME-ASUS-0001.zip

UEFI 0902 - see this post for further info and discussion in thread.

View attachment ROG-ZENITH-EXTREME-ASUS-0902.zip

SHA-256: 4F6A63E7FADD6DB5DD6D0F0F26AF9619D932C32AEFBBC7AFEB3C4D60FA47D845

UEFI 0006 - see this post for further info and discussion in thread.

View attachment ROG-ZENITH-EXTREME-ASUS-0006.zip

SHA-256: 3F5E1D01C9BC45E187C9E5D884F3C282E335759E8662229089E0121390862ED5

UEFI 0019 - see this post for further info and discussion in thread.

View attachment ROG-ZENITH-EXTREME-ASUS-0019.zip

SHA-256: BD4AA9AB2AFE081B675C6D9AB5D7949728C21DF857AAC30836D9F0BF005EDA94

UEFI 0901 - see this post for info.

View attachment ROG-ZENITH-EXTREME-ASUS-0901.zip

SHA-256: 479C8FC2467F5196114E868EB3D61F9399649E90286F0A3521FA6D7EE75AC7D1

UEFI 0012 - see this post for info.

View attachment ROG-ZENITH-EXTREME-ASUS-0012.zip

SHA-256: 48DFA8458A1B3E251DCDF2FC47BB620BD75A3D5E8855FBB8B19C822199860B80

UEFI 0804 - see this post for changes.

View attachment ROG-ZENITH-EXTREME-ASUS-0804.zip

SHA-256: 57465F569F40C2032AEA122F74019456B753772C3ABF9BB4D53E2D01346E8DBD

UEFI 0007 - Improves DRAM margins when using Hynix-based DIMMs in 2DPC configuration.

View attachment ROG-ZENITH-EXTREME-ASUS-0007.zip

SHA-256: 593B464D8B1F36AE8B235566B93A4D9664394C77812CDE0B847CB5EAB91350C5

UEFI 0801 - Revised memory rules, fixed CPU temp reporting issue after CMOS clear, UEFI RAID driver updated, Secure Erase string update.

(Notice: To avoid issues, do not update to this beta BIOS if you already have a SATA RAID configuration. For more details and instructions regarding the BIOS/RAID driver, please refer to the following link.)

View attachment ROG-ZENITH-EXTREME-ASUS-0801.zip

SHA-256: FAA5CABB5905A6BDA82E35D6997E3998FD1E745A3AC57B70EFED5C5FA1475808

UEFI 0603 - Includes previous Ai suite patch, RAID driver update, and a patch for Inateck 7-port KTU3FR-5O2U to solve POST issues.

View attachment ROG-ZENITH-EXTREME-ASUS-0603.zip

SHA-256: EB76E47385FB436520D31A67EB831D7A0EAA584D08AFE7701526BD9BFC52E301

UEFI 0046 plus updated AiSuite links in this post.

View attachment ROG-ZENITH-EXTREME-ASUS-0046.zip

SHA-256:84599CAE41B64B384C3C50A633E5FB289EBE522F72CC9BC8CAEC533BA62FEFDB

UEFI 9960 Beta - Automatically applies a 2T Command Rate for 2 DPC configs when above DDR4-2820.

View attachment ROG-ZENITH-EXTREME-ASUS-9960.zip

SHA-256: F3375608AF240F3A252BFE341FF8398DC38FADD3313C03B41F619828DA195E32

UEFI 0601 Official - Public release build. This will be on the support pages soon. Same as the 9910 beta. Please clear CMOS after updating (allow the update to complete fully before doing so!). For those of you still experiencing memory instability, try setting a 2T Command Rate.

View attachment ROG-ZENITH-EXTREME-ASUS-0601.zip

SHA-256: FA311F9B95B397340A1AF2F97016A9145B2C34B7631C18615E82F043F73B9CDC

UEFI 9910 Beta - Improved dual rank memory tuning.

View attachment ROG-ZENITH-EXTREME-ASUS-9910.zip

SHA-256: B97A061F8B9695267E6C55C2D900AD866FF532C2A326EFF6B91F73C71DEC1D72

UEFI 9906 Beta - More DRAM tuning for compatibility/OC, added CLDO VDDP Voltage under Tweaker's Paradise, also synchronized HWM CPU temp with monitor.

View attachment ROG-ZENITH-EXTREME-ASUS-9906.zip

SHA-256: 95D5764CD0838ACC8B43D8AD65128399981E88137A34CD54EDF5BAD6706996D2

UEFI 9980 Beta - Improves memory overclocking. Please note, some boards have older firmware for the onboard OLED/Aura, which can cause some strange issues. Please update to the latest version here

View attachment ROG-ZENITH-EXTREME-ASUS-9980.zip

SHA-256: 6158C4A25064CD72700D1A1B20A611F5B07F437DCA4AB54BDA7AD831D007752E

UEFI 9964 Beta - Improves memory overclocking, and adds 'Ln2 Tune' option to Tweaker's Paradise.

View attachment ROG-ZENITH-EXTREME-ASUS-9964.zip

SHA-256: 6054D525D4032AF2F6BC93DACE12C89B4E514430217EF3C468FE4FA5B07C6ED9

UEFI 0503 and Aura Firmware Update Tool - Updated AMD AGESA code and fixes some of the issues with 0501, Aura firmware update patches bugs that some users are experiencing.

View attachment ROG-ZENITH-EXTREME-ASUS-0503.zip

SHA-256: E58B8AF2E3E368AF928CC82D5F138F1BA19AF16E8D36039DFE9E1B47CA54F12A

AURA Update gain from support page, link.

The Stilt's ZE modified Unofficial UEFI

Quote: Originally Posted by The Stilt

The 0801 bios appears to be a significant improvement over the older ones (e.g. 0701), at least in regards of the maximum MEMCLK.
The board is now definitely 3466MHz capable, which definitely was not the case on the older bioses (at least on my setup). There still appears to be some shenanigans with the cold boots, but most of the time it is able to cold boot without hitting the recovery threshold. That will most likely be remedied as the platform matures.

I had some quad channel dual rank (64GB) B-die kits laying around, so I decided to give them a shot.

Reaching 3200MHz with 4x16GB config in this case was actually easier than on AM4 platform.
Cold boots are a major pain, but the memory itself works without any issues.





DRAM timings as seen in the SC.
1.3300V DRAM (boot & runtime), 1.0500V SoC (manual), 80Ohm ProcODT, everything else at "Auto".

ps. Don't touch tRDWR & tWRRD since it is not homogenous between the channels (CH A&C - B&D have different values).

I was using a modified version of the 0801 bios, with following changes in it:

- PMU FWs downgraded ("46" -> "42")
- "Memory Access Mode" brought back to AiTweaker-tab (in previous builds only available through CBS)
- Fixed AGESA build-string (0.0.6.0 to 1.0.0.3)

Most likely it won't make any difference, but feel free to try. If you're using 2 DPC config stick in the original 0801 build.
The bios is only updateable using Flashback.

Zenith Extreme 0801 SP42M (Unofficial)
Quote: Originally Posted by ReHWolution

Hi The Stilt, I always use your presets, those are amazing! May I ask what are the benefits in downgrading the PMU from46 to 42? Also, what's the PMU? Sorry for the stupid questions, but I'd love to learn more on the platform, as right now I'm on a 1950X/ZE too
Quote: Originally Posted by The Stilt

The newer PMU FW is targeted more towards 2 DPC compability and in some cases might not be the optimal choice for 1 DPC.
PMU (Phy micro-controller unit) is the memory controller inside the CPU.

UEFI Flashback
My procedure

i) UEFI filename as ZE.CAP, copy to USB stick root.
ii) Load UEFI defaults prior to doing flashback and let mobo repost and shutdown.
iii) Make sure USB stick is in Flashback port (marked in red box below image)



iv) Press and hold the Flashback button (blue box, above image) ~5secs. Blue LED on the button will flash slow for a few seconds and quicken as it starts update process. At the end of process it will extinguish, you are ready to boot up. If the blue LED stays constant the UEFI file was not found on USB stick, so check USB stick is correct format and filename is correct.

http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/

Known issues/Workarounds

Readings of BCLK in monitoring SW

Quote: Originally Posted by elmor

There is no such fluctuation, it's 100% a readout problem. Reference clock is not directly measured, but calculated using a suitable counter and prone to errors. The only platform which has hardware counters for reference clock is Skylake/Kaby Lake. Do you have any details on accuracy Mumak?
Quote: Originally Posted by Mumak

That's right - only very few CPUs allow true hardware measuring of BCLK (i.e. Skylake). For the rest we need to perform certain (often indirect) measurements to determine the BCLK and this can of course show slight fluctuations, especially under heavy system load.

HWiNFO has an option to disable BCLK "Periodic polling", so it will sample BCLK only once and don't perform periodic measurements and thus show fluctuations. I'm sorry, but there's no other way around this, as long as manufacturers don't offer a true measuring like in Skylake.
To set HWINFO to only take BCLK measurement one time set app in settings as below. This will mean you won't see erroneous shifts on BCLK, resulting in CPU/RAM clocks being shown incorrectly. These settings are accessed at launch of app by selecting settings.



On Extreme Tweaker page I would also set:-

Spread Spectrum [Disabled]

Due to the proximity of 1st PCI-E slot, large HSF like NH-U14S will be an issue on ZE, see the computerbase.de article, translated.

The PCH/M.2 heatsink screws have threadlocker. Warming them may help remove them with ease. In thread there has been discussion of members using solder iron to warm screwdriver/screw, mini blow torch and some have had no issue undoing screws.

HPET: Enabled has been highlighted as an issue on TR, patched beta version of AiSuite that does not enable HPET.

HPET can also be disabled by using a command prompt/powershell, opened as admin.

bcdedit /set useplatformclock false to disable
bcdedit /set useplatformclock true to enable

ASUS ZE UEFI currently does not have configurable HPET exposed.

- HPET disabled in BIOS: OS/software can't access HPET and has to fall back to the TSC-based timer
- HPET enabled in BIOS, but disabled by OS (useplatformclock false): OS will use TSC-based timer, but any software can still access HPET
- HPET enabled in BIOS, and enabled by OS (useplatformclock true): OS and all software will use HPET as primary timer
Quote source link.

NVMe RAID current current known issues in this AMD KB.

AMD Threadripper CPUs Info


AMD X399 Chipset Info/ASUS Zenith Extreme Block Diagram


Official/Unofficial RAM Info

ThreadRipper is using 2 IMC to have quad channel.



Samsung B die, single sided, single rank is what Threadripper favours, like Ryzen. In useful links section of OP is a thread with RAM IC info.

G.Skill announced a DDR4 specification for ThreadRipper, I believe this is more in tune with enthusiast (this is unofficial spec).



Some info on RAM timings in these posts, link 1, link 2.

Distributed (UMA)/Local (NUMA) memory mode can be changed in UEFI. Pick [Auto] or [DIE] for Distributed (UMA) and [Channel] for Local (NUMA).


PSA for quad channel RAM users


NVMe/SATA RAID



AMD Community NVMe RAID guide, please read known issues within AMD KB. Latest driver is not in KB but on chipset driver page.

AMD Ryzen™ Threadripper™ NVMe RAID Quick Start Guide RC-9.1.0 Release Version 1.0 PDF highlighted by VileLasagna
.

Also in extracted RAIDXpert2 Management SW (link in AMD KB), in directory AMD\AMD-Chipset-Drivers\Packages\Apps\RAIDXpert2_TR is a larger PDF. Page 43, section 5.4, Pre-installation steps maybe handy to view.

.


Flaxen Hegemony has shared testing of RAID 0 and ASUS RAM Cache II (
), discussion from onwards in thread. Please take note of Ljugtomten's [URL=https://www.overclock.net/forum/11-amd-motherboards/1636566-asus-rog-zenith-extreme-x399-threadripper-overclocking-support-35.html#post26414206]post.

Why do I not see RAIDXpert2 menu in UEFI?

Once SATA mode is changed to RAID, saved and mobo repost, the menu for RAIDXpert2 will be on Advanced page of UEFI. Also see this post.






Ryzen Master for Threadripper and Profiles

Download can be found on this webpage.




VRM Info

Quote: Originally Posted by The Stilt

Zenith Extreme: 8x IR3555M 60A (VDDCR_CPU), 3x TI 97374M 25A (VDDCR_SOC).
Both loops driven by their dedicated custom (ASP1405) Salem-series (IRF) controllers.

The inductors are most likely the same as on C6H, i.e microfine SMDs.
FPCAPs (10K) everywhere, VDDCR_CPU filtering is taken care by 12x 470µF FPCAP tantalum caps.
Quote: Originally Posted by CrazyElf

It actually looks like a serious heatsink as opposed to a solid block of aluminum.
I'm surprised they didn't use 12K caps which they use on their WS series of boards. Not a big deal though.

As expected though, it is 8x IR3555M. Thanks for confirming. They have used this on the X99 Rampage Extreme, the X299 Rampage Extreme I think, and now the X399 Zenith Extreme.
Quote: Originally Posted by The Stilt

As long as the capacitor itself is high quality (which obviously is the case with FPCAPs) anything above 2000 hours @ 105°C rating is essentially excessive, unless we're talking about hi-rel solutions such as medical, aerospace or space type of applications. The 10k rated caps will have a projected life time of ~178k hours at sustained 80°C.
Below is an photo showing the portion of cooling for CPU VRM under the shield. The heatpipe from the main heatsink goes to a fin array with the cooling fan, it makes no contact with PCB components. In that area is 2 phase VRM for DRAM slots on left side of CPU.



The SOC VRM does not have any cooling, just like both 2 phase DRAM VRM. I marked below image from and further info in @Sin0822 review of ZE on TweakTown.



The IR3555M mosfets used on CPU VRM have a temperature sensor inbuilt. So it's actual mosfet temperature and not a thermistor placed in the vicinity of VRM.

Cooling Threadripper

Quote: Originally Posted by The Stilt

Cool isn't exactly the term I would use to describe TR with


At 3.7GHz / 1.15000V my CPU reaches 95°C (tCTL) in less than two minutes on Asetek 570LC, when the pump and both of the fans are running at 100% duty. Asetek 570LC has a small 120mm radiator, however it's a thick one (49mm without the fans).
My opinion from nycgtr experience share is the XSPC Raystorm Neo and Heatkiller IV is the current front runners for best water block for ThreadRipper. The Bykski A-Ryzen-Th-X seems very close 2nd best, based on HardOCP review and my own testing of Bykski A-Ryzen-ThV2-X. EK TR seems adequate for stock operation, but not so great in comparison to the other blocks when overclocking. So this is trailing "the pack".

EK have released a updated coldplate for the EK X399 monoblock, nycgtr testing has shown it still does not beat the best TR blocks out there. They are offering 25$/€ to EK TR STD block owners.

PState OC
PState 0 default frequency will be 3400MHz on 1950X (Base clock as found in spec).

Set OC Mode to "Customized", Advanced page > AMD CBS > Zen Common Options.



Then go to Custom PStates / Throttling to see screen below.



When you increase MHz by editing PState0 FID (hexadecimal) it will be reflected in the greyed box Frequency (MHz). Using a frequency of 3425MHz+ will enable "OC mode". As CPU is in "OC mode" you will knock out PB/XFR and would need to start "overclocking" PState 0 to gain back higher clocks.

(Note: My recommendation is to set Core Performance Boost on Extremer Tweaker page to [Disabled] when doing a PState OC. This is so if AMD CBS is reset and the CPU enters PB/XFR on a post the additional offset set on Extreme Tweaker does not create overvolt, this was the case on C6H/Ryzen, I have yet to test on ZE/TR.)

What we see as Voltage (uV) (ie 116250) is a ceiling VID for PState 0, when CPU enters OC mode it will snap to 1.1625V.

When CPU is not in "OC mode" and we disable PB/XFR by disabling Core Performance Boost on Extreme Tweaker page and we load CPU, so it only go to PState 0 ceiling MHz, you will observe CPU does not use 1.1625V for 3.4GHz.



As you can see my 1950X sample uses VID: ~1.038V / VCORE (SVI2 TFN): ~1.056V.

PState0 VID is also hexadecimal, when you edit it the change will be reflected in greyed box Voltage (uV).

When you start to OC PState0 you will be doing an "All cores OC", just like when changing CPU Core Ratio on Extreme Tweaker page.

Changing Core/Thread count in UEFI

The menu you need to be in is located on Advanced > AMD CBS > Zen Common Options





As shown in above screen shots when OC Mode is Normal Operation you will not be able to change core/thread count. So set Customised.






Power Plan editing in Windows for core parking

The registry edit in this thread has information on doing the same on Win 7.

How to Add "Choose Power Plan" to Desktop Context Menu in Windows 7 and Windows 8.

Windows 10: 'Choose Power Plan' context menu - Add in Windows 10

Example image from Windows 7 showing core parking disabled by using value of 100%. Lower values result in more cores being parked.


FAQ

Stock mode I see high core voltages?

This is normal for Ryzen/ThreadRipper. In stock mode due to how Precision Boost / Extended Frequency Range (PB/XFR) works the System Management Unit (SMU) controls voltages and sets them as required for boost clocks. At stock the CPU is power limited, the SMU through various on die sensors monitors "state" of CPU in this context and will determine how many cores can boost and to what level. As these transitions occur very quickly SW monitoring may not give a true picture of what is going on.

At stock CPU uses ~1.5V, why can I not use that when OC'ing for daily use?

When highest PB/XFR clocks occur the CPU may only be boosting low number of cores, so amps/power draw is lower, so it can take the voltage the SMU has determined for boost clocks.

When "we" OC, "we" do all cores boost, power limit is also removed, so amps/power draw is higher, so it could be detrimental for silicon to use voltages as seen when PB/XFR occur at stock.

When "we" OC, PB/XFR is disabled, so "we" OC base clock/PState 0, an increase of +25MHz above stock base clock/PState 0 will engage "OC mode".

Voltage recommendation

Quote: Originally Posted by The Stilt

=< 1.35V for sustained use, under full stress.
IMO anything higher than 1.250V on Threadripper is sheer insanity, considering the power draw of these parts.
My CPU at 3.7GHz / 1.150V is drawing 220W of power during Prime95. Considering the scaling of these parts at 1.250V the power consumption would be around 300W.

Temperature readings incorrect

i) make sure you have OLED FW update applied, linked in OP at top.
ii) Disable Overclocking Enhancement on Extreme Tweaker page and Sense MI Skew within Extreme Tweaker > Tweakers Paradise

What is Overclocking Enhancement in UEFI options?

It enables SenseMi Skew (artificially reading lower temperatures in order to trick XFR to boost longer and higher), Performance Bias and tweaks VRM settings to improve overclockability.
Quote link.

Duplicate setting in UEFI

Some of the settings with AMD CBS menu are duplicated in the Ai Tuner section of UEFI. Only a instance of setting needs to be changed, when one is changed the other will not reflect the change but change will apply. AMD CBS options could revert to defaults on failed posts when AMD "code" decides to reset them, Ai Tuner should hold the settings for them to be reapplied.

Erratic fan speed increase fix

In the UEFI is a fan smoothing option, increase value to delay fan PWM increase from temperature fluctuations. Right click below animated GIF and open in new tab to see at higher res.


Changing Memory mode in UEFI (Distributed (UMA)/Local (NUMA))

Distributed (UMA)/Local (NUMA) memory mode can be changed in UEFI. Pick [Auto] or [DIE] for Distributed (UMA) and [Channel] for Local (NUMA).


Useful Links

Some links broken, will be fixed ASAP.

Asus & X399 The ROG Zenith Extreme: A Complaint & Bug Tracking Thread

Please note there is bug report form in OP here, linked at top. This is viewed by ASUS reps, please do use that.

Der8auer -
.

Ryzen Memory IC Collection Thread

Overclocking Tips - Beginner and Advanced Guide to Overclocking by [email protected] (old guide but some pertinent info)

Ryzen Timings Checker by The Stilt

ASUS ZenStates by Elmor

HWiNFO by Martin Malik (Mumak on OCN)

SIV (System Information Viewer) by Ray Hinchliffe (red-ray on OCN)

Community Update #4: Let's Talk DRAM!

Memory OC Showdown: Frequency vs. Memory Timings

RealBench Leaderboard / Download link page

Y-Cruncher by Alexander J. Yee (Mysticial on OCN)

Statuscore by Dannotech (Handy app to test individual/multiple real/SMT cores for clocks/temps/etc)

RAM Test, this post, contains share by The Stilt on app. This is OCN thread on app and has author participation, Mustanaamio.

HCI Memtest

Program to launch many instances, etc of HCI Memtest by OCN member Frikencio

Program to launch many instances, etc of HCI Memtest by OCN member Bartouille.

Thaiphoon Burner by Vitaliy Jungle (Voodoo Jungle on OCN) (
)

electrified's ASUS WMI support for Linux HWMON (lmsensors)
 

Attachments

·
Registered
Joined
·
1,269 Posts
Just built my Threadripper rig with this board and first boot up won't post, I get post code B2, Load VGA bios... any thoughts here?
 

·
Registered
Joined
·
14 Posts
Quote:
Originally Posted by alucardis666 View Post

Just built my Threadripper rig with this board and first boot up won't post, I get post code B2, Load VGA bios... any thoughts here?
I had this issue on early UEFI versions. You need to wait longer, it should progress past B2 eventually - or use flashback to upgrade to 0401 or 0503 UEFI.
 

·
Registered
Joined
·
14 Posts
UEFI 0401 and later don't have Memory Access Mode in UEFI (UMA/NUMA switch) - impossible to switch modes if you don't have Ryzen Master, especially on Linux
frown.gif
 

·
Meddling user
Joined
·
7,423 Posts
Discussion Starter · #6 ·
@alucardis666

Do as xoqolatl has advised
smile.gif
.

Use Flashback, there is also latest beta 9964 in OP
smile.gif
. If you have repeat issue please state Q-LED status as well
wink.gif
.

 

·
Registered
Joined
·
121 Posts
Got it last week and had flashbacks of the earlier C6H days. As of BIOS 0502, I'm unable to run my Sammy B OEM modules higher than 2933MHz, no matter the timings or voltages. I was using the known stable settings from C6H to no avail. Maybe BIOS 9964 helps.

Edit:

I just flashed 9964 and still couldn't post with my 3066MHz C6H settings (ProcODT 53.3), however I just got a post when using 96ohm. I wonder if the quad channel interface needs different resistances than the dual channel AM4 setup?
 

·
Meddling user
Joined
·
7,423 Posts
Discussion Starter · #8 ·
Dual rank Samsung B die was 80/96Ω or 43.6Ω on C6H.
Quote:
Suggested ProcODT values from Elmor/The Stilt for C6H:-

Samsung B (SR) 2x8GB 53.3Ω / 60.0Ω
Samsung B (DR) 2x16GB 80Ω / 96Ω
Samsung B (DR) 4x16GB 43.6Ω
Hynix A (DR) 2x8GB 53.3Ω
Hynix A (DR) 4x8GB 40Ω
You may also need to tweak RttNom,RttWr and RttPark, some users of C6H had good sucess with DR by changing those values, also CAD bus config.
 

·
Registered
Joined
·
1,269 Posts
Quote:
Originally Posted by xoqolatl View Post

I had this issue on early UEFI versions. You need to wait longer, it should progress past B2 eventually - or use flashback to upgrade to 0401 or 0503 UEFI.
Will try flashback now. Thanks!
 

·
Registered
Joined
·
121 Posts
Quote:
Originally Posted by gupsterg View Post

Dual rank Samsung B die was 80/96Ω or 43.6Ω on C6H.
You may also need to tweak RttNom,RttWr and RttPark, some users of C6H had good sucess with DR by changing those values, also CAD bus config.
Gup,

Neither of these settings worked for me on C6H, 53.3 yielded the best results when doing 3000MHz+. 53.3 on ZE didn't post at all, neither did 43.6. 80 allowed me to post but wouldn't boot Windows. I went with 68.6 now and after a brief Memtest, it seems stable with 3066MHz.
 

·
Meddling user
Joined
·
7,423 Posts
Discussion Starter · #11 ·
Sweet, those are just suggestions for ProcODT. The Stilt and [email protected] repeatedly stated in C6H thread that really what is right is what you test and need. Yeah real pain but it's price we gotta pay if OC'ing/Tweaking
redface.gif
.
 

·
Registered
Joined
·
121 Posts
Quote:
Originally Posted by gupsterg View Post

Sweet, those are just suggestions for ProcODT. The Stilt and [email protected] repeatedly stated in C6H thread that really what is right is what you test and need. Yeah real pain but it's price we gotta pay if OC'ing/Tweaking
redface.gif
.
That's ok. Happy to pay that price
smile.gif


I'm just surprised it differs from X370 that much. BTW, in case anyone was wondering, RTC works on X399 as well.
 

·
Meddling user
Joined
·
7,423 Posts
Discussion Starter · #13 ·
I guess the mobo/CPU creates the variation if you are using same RAM kit.

I know on same C6H/RAM but differing CPU I needed differing ProcODT to attain highest RAM clock compared with another CPU, upto ~3500MHz was what I went for.
 

·
Registered
Joined
·
38 Posts
Quote:
Originally Posted by lifeisshort117 View Post

I was able to achieve a 4.1ghz overclock on my 1920X at 1.33v

I set power delivery settings from Standard to Optimized, which may bump voltage to 1.35v to maintain stability, as well as throughput from 100% to 110%



What type of G-Skill Trident Z RAM are you using?
 

·
Registered
Joined
·
121 Posts
My 24/7 settings from the C6H (3066, 16-16-16 2T) are now stable with 68.6ohm. 3200 seems tricky and may require Bus tinkering, as I always get an occasional error in Memtest sooner or later.

tr_3066pss50.jpg
3066x4skc.jpg
 

·
Registered
Joined
·
513 Posts
Quote:
Originally Posted by Poloasis View Post

What type of G-Skill Trident Z RAM are you using?
Those are F4-3200C16_-8GTZR, if I read the label correctly. Waiting for more board comparisons to dive in, and a binned CPU, but then will join and am transplanting my 4133 Trident Z (CL19 21-21). I've gotten 3733 on a Maximus VIII Extreme with CL14. I had 4K working, but no improvement in performance with the looser latency. So, those 4 dimms are making the move and that build is being retired to another project!
biggrin.gif
 

·
Registered
Joined
·
1,269 Posts
Up and running. Using the X62 to cool, anyone else getting high temps? Like... I'm sitting @ 65C @ idle?! CPU @ 3.9ghz...
rolleyes.gif


EDIT: So idk to go by cam software or HW monitor, maybe it's an offset thing here that's throwing me off?

 

·
Registered
Joined
·
513 Posts
Quote:
Originally Posted by alucardis666 View Post

Up and running. Using the X62 to cool, anyone else getting high temps? Like... I'm sitting @ 65C @ idle?! CPU @ 3.9ghz...
rolleyes.gif


EDIT: So idk to go by cam software or HW monitor, maybe it's an offset thing here that's throwing me off?

27C offset from the junction to get the die temp. The new HWinfo should have both listed.

Edit: Cam is correct and the HWinfo is showing the junction temp, which is made to kick the fans up higher. If you subtract 27C from it, you get the cam temp (actually 36.5, but close enough).
 
  • Rep+
Reactions: alucardis666

·
Registered
Joined
·
1,269 Posts
Quote:
Originally Posted by ajc9988 View Post

27C offset from the junction to get the die temp. The new HWinfo should have both listed.

Edit: Cam is correct and the HWinfo is showing the junction temp, which is made to kick the fans up higher. If you subtract 27C from it, you get the cam temp (actually 36.5, but close enough).
Just updated. It's now showing both. So just disregard the higher one? lol.
 
  • Rep+
Reactions: ajc9988
1 - 20 of 3269 Posts
Top