thesmokingman
Supreme [H]ardness
- Joined
- Nov 22, 2008
- Messages
- 6,617
At 95c the chip throttles down.
That's kind of the point to the test.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
At 95c the chip throttles down.
That's kind of the point to the test.
maybe with prime but with real world usage (in my case rendering in cinema4d) the noctua does fine (if you dont overclock).Indeed, doesn't take long with the noctua cooler, really a custom loop seems to be the only option with these.
maybe with prime but with real world usage (in my case rendering in cinema4d) the noctua does fine (if you dont overclock).
i managed already to bring it down to 72/73C max by repositioning fans and i will replace them with more and better ones the next days.
hm, i doubt that davinci uses more resources than cinema4d, at least not in that amount. to me that looks like another problem...Only takes like 5 minutes of running the tracker in davinci resolve and mine throttles.
maybe with prime but with real world usage (in my case rendering in cinema4d) the noctua does fine (if you dont overclock).
i managed already to bring it down to 72/73C max by repositioning fans and i will replace them with more and better ones the next days.
hm, i doubt that davinci uses more resources than cinema4d, at least not in that amount. to me that looks like another problem...
thesmokingman :
just ran prime95 twice now (blend test) for about 20-30mins and i got a phase (maybe 3-4min) it peaked at 92C, but mostly it was under 80C.
all just stock here, asus zenith extreme 2, 3970x, noctua NH-U14S TR4-SP3 standard, mounted with conductonaut.
only two 120 case fans pushing the air out (underpressure). it is not even a great case (NZXT 510)
mikeo :
compared with this, your temps seem strange.
i ordered some nocuta fans with better performance / noise values than the two that came w the case
i will try a 2nd fan on the cooler, 2 fans out, 2 fans in. atm my goal is not to oc, but to get it as silent as possible at load / when rendering.
atm even when idle the fans always spin up and down a little... sounds like a neat summer breeze .-)
thesmokingman :
just ran prime95 twice now (blend test) for about 20-30mins and i got a phase (maybe 3-4min) it peaked at 92C, but mostly it was under 80C.
all just stock here, asus zenith extreme 2, 3970x, noctua NH-U14S TR4-SP3 standard, mounted with conductonaut.
only two 120 case fans pushing the air out (underpressure). it is not even a great case (NZXT 510)
... to me the test behaviour was a bit strange... it buildt up till ±80C and then after ca 10mins suddenly raised to ±90C for 1-2 minutes and then fell back to 80C again and stayed there for the next 20mins without any change ... cinema4d doesnt raise the temps that much, but i already ordered fans to get temps and noise down a bit...You only ran it for 30 minutes so you didn't give it time to heatsoak, yet it hit 92c anyways. That should reinforce the fact that you are already pushing it cooling wise. I would be wary of a long sustained load.
... to me the test behaviour was a bit strange... it buildt up till ±80C and then after ca 10mins suddenly raised to ±90C for 1-2 minutes and then fell back to 80C again and stayed there for the next 20mins without any change ... cinema4d doesnt raise the temps that much, but i already ordered fans to get temps and noise down a bit...
ok tx, i give it a longer try when i got my fans.
but i have another question... would you think custom watercooling with an external 9x9 radiator is a good/clean way to get a (very) silent system?
For a render monster you need Windows 7 pro or ultimate. It's still faster than Windows 10, on Blender. Even if Windows 10 is catching up.
Or Linux ! But you may not find the best graphics drivers on Linux.
thesmokingman :
how silent/noisy is your system?
do you have some advices to get the system as silent as possible?
"We have determined that many popular monitoring tools are quite aggressive in how they monitor the behavior of a core. Some of them wake every core in the system for 20 ms, and do this as often as every 200 ms. From the perspective of the processor firmware, this is interpreted as a workload that's asking for sustained performance from the core(s). The firmware is designed to respond to such a pattern by boosting: higher clocks, higher voltages," stated Robert Hallock, AMD's head of technical marketing for processors. "So, if you're sitting there staring at your monitoring tool, the tool is constantly instructing all the cores to wake up and boost. This will keep the clock-speeds high, and the corresponding voltages will be elevated to support that boost. This is a classic case of observer effect: you're expecting the tool to give valid data, but it's actually producing invalid data by virtue of how it's measuring," he added.
It has become a common practice for several years to report instant (discrete) clock values for CPUs. This method is based on knowledge of the actual bus clock (BCLK) and sampling of core ratios at specific time points. The resulting clock is then a simple result of ratio * BCLK. Such approach worked quite well in the past, but is not longer sufficient. Over the years CPUs have become very dynamic components that can change their operating parameters hundreds of times per second depending on several factors including workload amount, temperature limits, thermal/VR current and power limits, turbo ratios, dynamic TDPs, etc. While this method still represents actual clock values and ratios reported match defined P-States, it has become insufficient to provide a good overview of CPU dynamics especially when parameters are fluctuating with a much higher frequency than any software is able to capture. Another disadvantage is that cores in modern CPUs that have no workload are being suspended (lower C-States). In such case when software attempts to poll their status, it will wake them up briefly and thus the clock obtained doesn't respect the sleeping state.
Hence a new approach needs to be used called the Effective clock...
here some noctua fans received and with the first setup my 3970x is not cooler but louder ! ouch .-)
i get the feeling that a custom watercooling is mandatory to run a 3970x with acceptable noise :-/
mikeo:
did you get your parts ? it would be nice if you could report your experience and temperatures / noise after you built your loop !
thesmokingman :
how silent/noisy is your system?
do you have some advices to get the system as silent as possible?
The dual D5 pumps and 3x360 rads with noctua fans can definitely handle a 3970x.
i think i tried that, too... you have to uninstall, then install again... but i'm quite sure it did not work...The only real option is to reinstall RM.
Only takes like 5 minutes of running the tracker in davinci resolve and mine throttles.
Your really cooling challeneged then.
I can run a planar tracker in DR16 and I barely hit 50c.
Posting some leftover pics with comments.
Vray bench cpu+gpu, in sli. 48K and change on the cpu is pretty darn good imo
View attachment 212586
R20, cpu at 4.2 with stock memory timings vs tweaked
View attachment 212587
Memory timings... using safe settings. Fyi, Dram Calculator does not work on Threadripper 3, so swap yer ram to a Ryzen system to run it. If yer using same memory modules, u can just use these too.
View attachment 212588
View attachment 212589
View attachment 215075
If you don't have a loop filter, I suggest ya get one with some QDCs. This is from when the first fill up. Look at all that gunk.