We've been working hard at building our second iteration of the RIPJAY bench, last featured in a livestream where we beat JayzTwoCents' score in TimeSpy Extreme, taking first place worldwide for a two-GPU system. Since then, Jay has beaten our score -- primarily with water and direct AC cooling -- and we have been revamping our setup to fire back at his score. More on that later this week.
In actual news, though, it's still been busy: RAM prices are behaving in a bipolar fashion, bouncing around based on a mix of supply, demand, and manufacturers trying to maintain high per-unit margins. Intel, meanwhile, is still combating limited supply of its now-strained 14nm process, resulting in some chipsets getting stepped-back to 22nm. AMD is also facing shortages for its A320 and B450 chipsets, though this primarily affects China retail. We also received word of several upcoming launches from Intel, AMD, and NVIDIA -- the RTX 2070 and Polaris 30 news (the latter is presently a rumor) being the most interesting.
We always like to modify the reference cards – or “Founders Edition,” by nVidia’s new naming – to determine to what extent a cooler might be holding it back. In this instance, we suspected that the power limitations may be a harder limit than cooling, which is rather sad, as the power delivery on nVidia’s RTX 2080 Ti reference board is world-class.
We recently published a video showing the process, step-by-step, for disassembling the Founders Edition cards (in preparation for water blocks). Following this, we posted another piece wherein we built-up a “Hybrid” cooling version of the card, using a mix of high-RPM fans and a be quiet! Silent Loop 280 CLC for cooling the GPU core on a 2080 Ti FE card. Today, we’re summarizing the results of the mod.
“How frequently should I replace liquid metal?” is one of the most common questions we get. Liquid metal is applied between the CPU die and IHS to improve thermal conductivity from the silicon, but there hasn’t been much long-term testing on liquid metal endurance versus age. Cracking and drying are some of the most common concerns, leading users to wonder whether liquid metal performance will fall off a cliff at some point. One of our test benches has been running thermal endurance cycling tests for the last year now, since September of 2017, just to see if it’s aged at all.
This is a case study. We are testing with a sample size of one, so consider it an experiment and case study over an all-encompassing test. It is difficult to conduct long-term endurance tests with multiple samples, and would require dozens (or more) of identical systems to really build-out a large database. From that angle, again, please keep in mind that this is a case study of one test bench, with one brand of liquid metal.
For today, we’re talking about volt-frequency scalability on our 8086K one more time. This time, coverage includes manual binning of our core, as we already illustrated limitations of the IMC in the overclocking stream. We’ve also already tested the CPU for thermal and acoustic performance when considering liquid metal applications.
The Intel i7-8086K is a binned i7-8700K, so we thought we’d see what bin we got. This testing exhibits simple volt-frequency curves as plotted against Blender and Firestrike stability testing. Note that our stability tests were limited to 30 minutes in an intensive Blender workload. Realistically, this is the most achievable for publication purposes, and 99% of CPUs that pass this test will remain stable. If we were selling these CPUs, maybe like Silicon Lottery, it’d obviously be preferable to test for many hours.
In case you missed it, we spent four hours live overclocking an Intel i7-8086K just a couple days ago. The OC effort was watched by about 2300 people concurrently, spanning all four hours, and was one of our most successful streams to-date. The viewership was beaten only, and unsurprisingly, by our #RIPLTT stream’s 5000 concurrent viewers.
As for the testing, it was all 8086K overclocking in Firestrike Physics, with some additional memory overclocking in the final two hours. Components used were varied, depending on what was happening at any given time, and the final frequency was high. We closed at 5.35GHz, running a 101 BCLK with 53x all-core multiplier. Some additional testing was done in effort to push individual cores to 54x, but we couldn’t get it stable. Despite our ultimate core limitations at just under 5.4GHz, the CPU itself – barring the IMC – is the best-binned 8700K we’ve had hands-on with yet. Our 8086K (which is a binned 8700K) managed to hold 5.1GHz at roughly 1.3V with relative stability in Firestrike, only running into exponential increases in voltage requirement upon pushing 53x multipliers. We even attempted 1.5V for a 5.4GHz overclock, but just couldn’t stabilize. Our plan is to return in the future with a bigger or more exotic cooling solution atop the die. Our X62 did admirably, and the delid with liquid metal (Thermal Grizzly Conductonaut) kept thermals in check, but lower is still better.
We visited EVGA’s suite for a look at the new OC Robot and built-in BIOS stress testing update for the X299 Dark motherboards. For the new X299 Micro 2 motherboard, we also learned the following of the VRM spec:
- VCCIN : IR35201(Controller1 - 5PH double to 10PH) + IR3556 x10
- VSA+VCCIO : IR35204(Controller2 - 1+1PH) + IR3556 (1+1)
- VSM+VPP_C01 : IR35204(Controller3 - 1+1PH) + TDA88240 (1+1)
- VSM+VPP_C23 : IR35204(Controller4 - 1+1PH) + TDA88240 (1+1)
At EVGA’s headquarters in New Taipei City, Taiwan, GamersNexus received a hands-on overview of the company’s new semi-closed loop liquid nitrogen cooling setup. The setup was created by K|NGP|N and TiN, both of whom work in the Taiwan office, to increase overclocking efficiency and reduce LN2 usage to only necessary quantities. Typically, extreme overclocking involves manual pouring of liquid nitrogen (LN2) from a thermos, which the overclocker can either manually refill from the LN2 tanks or can refill from the exhaust. With this new system, K|NGP|N is able to circulate LN2 based upon software input of desired temperatures, with used LN2 getting pushed through a series of flexible steel tubing and out of an exit manifold. The result yields somewhat reusable LN2 and eliminates the hands-on thermos pouring element of XOCing, allowing overclockers to focus on the result and tuning. Theoretically, you could run off of large LN2 tanks (~180L) at conservative temperatures for weeks on end, then swap tanks and use the collected “runoff.”
A few days ago, we ran our most successful, highest-watched livestream in the history of GN. The stream peaked at >5300 concurrent viewers for around 2.5 hours, during which time we attempted to outmatch the LinusTechTips 3DMark score submitted to the 3DMark Hall of Fame. This was a friendly media battle that we decided to bring to LTT after seeing their submission, which briefly knocked us out of the Top 10 for the Hall of Fame. As noted in this recap video, we're not skilled enough to compete with the likes of K|NGP|N, dancop, der8auer, or similar pro XOCers, but we can certainly compete with other media. We made a spectacle of the event and pushed our i9-7980XE, our RAM, and our GPU (a Titan V) as far as our components would allow under ambient cooling. Ambient, by the way, peaked at ~30C during the stream; after the stream ended and room ambient dropped ~10C to 20C, our scores improved to 8285 in Timespy Extreme. This pushed us into 4th place on the 3DMark official Hall of Fame, and 3rd place in the HW Bot rankings.
The overclocking stream saw guest visits from Buildzoid of Actually Hardcore Overclocking, who assisted in tuning our memory timings for the final couple of points. We think there's more room to push here, but we'd like to keep some in the tank for a retaliation from Linus and team.
Even when using supposed “safe” voltages as a maximum input limit for overclocking via BIOS, it’s possible that the motherboard is feeding a significantly different voltage to the CPU. We’ve demonstrated this before, like when we talked about the Ultra Gaming’s Vdroop issues. The opposite side of Vdroop would be overvoltage, of course, and is also quite common. Inputting a value of 1.3V SOC, for instance, could yield a socket-side voltage measurement of ~1.4V. This difference is significant enough that you may exit territory of being “reasonably usable” and enter “will definitely degrade the IMC over time.”
But software measurements won’t help much, in this regard. HWINFO is good, AIDA also does well, but both are relying on the CPU sensors to deliver that information. The pin/pad resistances alone can cause that number to underreport in software, whereas measuring the back of the socket with a digital multimeter (DMM) could tell a very different story.
As we await arrival of our APUs today, we’ve seen a few news stories reporting “4.56GHz” overclocks (or similarly high clocks) on AMD’s new Ryzen+Vega amalgamation. Seemingly, this significantly higher overclock is achievable merely by entering S3 (sleep) in Windows, and is even easily validated with higher benchmark scores.
In reality, we believe this is the Windows timer bugging out, which has existed on previous platforms and CPUs. The bug is easy to replicate because it only requires entering S3 state – another commonly problematic Windows setting, based on a previous life of lab testing – and waking from S3 causes artificially high clock reports.
We moderate comments on a ~24~48 hour cycle. There will be some delay after submitting a comment.