Nooooo ,Why? your like the 3rd person to cancel. I dont want to be in a CFL Builders club by my self LOL..
Threw a fit ? How about calling them liars, since I have one, and I know whats required, since EVERYONE can read the TR builders thread. And I wasn't quoting them selectively. I quoted (as I said) the final few sentences conclusion from the article VERBATIM.Do you remember when you threw a tantrum when some review sites needed relatively "high" voltages in their Threadripper review? How come you're so comfortable with this particular review you are even quoting them, albeit selectively?
Edit:
Generally how fast does tim dry up and need to be reapplied?Is this something I am going to have to worry about?
Thanks but I dont have the balls to de-lid a $400.00 CPU on my own. I for sure will muck something up. I will just leave that to the pro's..If you replace it, just be careful because some of the paste options will fail in that application. NT-H1 does *not* work between heat spreader and die. The Coollaboratory stuff seems to work fine. The liquid ultra will last years. NT-H1 required a re-application every 3-4 months. It was frustrating to figure out what was going on. It wasn't due to drying out. There is movement between the two during heating and cooling cycles that tends to push the TIM out and cause failure that doesn't occur between a heat sink and the heat spreader for whatever reason. That's really the biggest thing to consider when de-lidding.
Note: due to the solder vs TIM, sometimes it is listed as TCase and sometimes as TJunction where the processor throttles.
Core 2 is a little speculative. Later processors have an offset option for TCC Thermal Control Circuit so throttling may occur below Tjmax. Some processors enable Tjmax to be changed. Easy way to get an idea of how accurate Tjmax is or not can be to run the processor at low power (single Watts) without a heatsink and use a good infrared temperature gun to measure the external temp which shouldn't be more than 3C or so lower than core temp.8th Generation 14 nanometer i7 8700K / i5 8600K (TDP 95W / Idle 3W),
7th Generation 14 nanometer i7 7700K / i5 7600K (TDP 91W / Idle 2W),
6th Generation 14 nanometer i7 6700K / i5 6600K (TDP 91W / Idle 2W):
Tj Max (Throttle temperature) = 100°C
5th Generation 14 nanometer i7 5775C / i5 5675C (TDP 65W / Idle 2W):
Tj Max (Throttle temperature) = 96°C
4th Generation 22 nanometer i7 4790K / i5 4690K (TDP 88W / Idle 2W),
4th Generation 22 nanometer i7 4770K / i5 4670K (TDP 84W / Idle 2W):
Tj Max (Throttle temperature) = 100°C
Legacy Core
3rd Generation 22 nanometer i7 3770K / i5 3570K (TDP 77W / Idle 4W):
Tj Max (Throttle temperature) = 105°C
2nd Generation 32 nanometer i7 2600K / i5 2500K (TDP 95W / Idle 4W):
Tj Max (Throttle temperature) = 98°C
1st Generation 45 nanometer i7 860 / i5 750 (TDP 95W / Idle 12W),
1st Generation 45 nanometer i7 920 D0 (TDP 130W / Idle 12W):
Tj Max (Throttle temperature) = 100°C
Core 2 45 nanometer Q9550 E0 (TDP 95W / Idle 16W),
Core 2 65 nanometer Q6600 G0 (TDP 95W / Idle 24W):
Tj Max (Throttle temperature) = 100°C
It is not just the one bios setting. If you switch this settings you not only get all cores@4.7 but also massive overvolt which is in many cases completely unnecessary. This stupid setting needs to be disabled unless you set voltages manually.Their words. My only point was that other than stock, they run HOT, even just enabling that one bios setting that puts all cores@4.7, or a "factory" overclock and it was throttling. Other places here people said these run cool. Even at stock with an aftermarket HSF they were running 76c, which in my book is hot, none of my boxes, Xeons or otherwise get close to that temp.
It is not just the one bios setting. If you switch this settings you not only get all cores@4.7 but also massive overvolt which is in many cases completely unnecessary. This stupid setting needs to be disabled unless you set voltages manually.
Is that the only way to get all the cores to lock at the same speed turning MCE on?
No, you can set your frequency and number of cores to run at that frequency manually.
DO not forget "ULTRA" edition IHS-Silver
DO not forget "ULTRA" edition IHS-Silver
You are missing my point. My point is that 76°C is no longer a problem. Ever since Kaby Lake, everyone needs to take their "high temperature" idea and add ~20°C to it since we are now seeing CPU junction temperature instead of CPU case temperatures.You are missing the point. Without even a 5 ghz OC, and using aftermarket cooling, the chip was throttling at "factory OC" !! That's the point. Anything past stock requires a high end cooler. Do I have to quote the text ?
You are missing my point. My point is that 76°C is no longer a problem. Ever since Kaby Lake, everyone needs to take their "high temperature" idea and add ~20°C to it since we are now seeing CPU junction temperature instead of CPU case temperatures.
I understand your point, but I personally have no problem with overclockers being required to have a good cooling system.
One reason is that it's usually not possible to test a given setup in a worst-case scenario, say heaviest loads at highest ambient temps, so it's prudent to have as wide a safety margin as feasible. Another reason is that high CPU temps usually go hand-in hand with other component temps being high, like VRMs, since power consumption rises with temps, all things being equal. Excessively high temps are detrimental to the lifespan of these components and can contribute to their premature failure.What reason is there to care about CPU temperature as long as it is within specifications?
That said - Intel's max temps aren't for overclocked chips. Those of us who are overclocking, and hence over-volting, prefer a better safety margin on our temps than Intel's max. Shaving off 20C by delliding and running LC systems makes us feel better (for long term overclocking, especially when running DC projects).
I'm going to be frank here. If you're doing DC, you really shouldn't be overclocking. It's just not very responsible to contribute to these projects running things outside their standard parameters. It's fine for our personal stuff, but DC projects fall in to the actual work category, and as stable as it may seem to you, your calculations are still far more error prone than running something stock. Don't do this.
A caveat would be that running all cores at the max single core turbo should not be a problem, if cooling is adequate. That's technically overclocking, but in a relatively safe manner.I'm going to be frank here. If you're doing DC, you really shouldn't be overclocking. It's just not very responsible to contribute to these projects running things outside their standard parameters. It's fine for our personal stuff, but DC projects fall in to the actual work category, and as stable as it may seem to you, your calculations are still far more error prone than running something stock. Don't do this.
If cooling and LLC are adequate - voltage used for ST Turbo may drop bellow safe limit once all cores are under load. Should be treated like an overclock and tested for stability.A caveat would be that running all cores at the max single core turbo should not be a problem, if cooling is adequate. That's technically overclocking, but in a relatively safe manner.
Yes, true. I should have added that part for those not familiar with OCing, thanks.If cooling and LLC are adequate - voltage used for ST Turbo may drop bellow safe limit once all cores are under load. Should be treated like an overclock and tested for stability.
I'm going to be frank here. If you're doing DC, you really shouldn't be overclocking. It's just not very responsible to contribute to these projects running things outside their standard parameters. It's fine for our personal stuff, but DC projects fall in to the actual work category, and as stable as it may seem to you, your calculations are still far more error prone than running something stock. Don't do this.
I understand why you are suggesting this, but I am not sure the projects would agree. I believe that a large portion of their volunteer workforce are hobbyists who OC and enjoy seeing how high they can push their numbers. Over at folding@home, the names of the top teams by total work done suggest lots of folks that overclock. I expect the folks who run these projects are keenly aware that this is the case and welcome it rather than discourage it. Afterall, results are verified automatically - and usually before credit is awarded.
I'm not affiliated with any DC projects, just offering an opinion in response to this. Back to lakes full of coffee!