Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
He was reminiscing about how he hasn't had it enabled for years and how he hasn't used default motherboard settings for years.
We weren't talking specifically about LGA1700 and it doesn't matter, it's on topic because this has been an ongoing issue with Intel and its partners.
and the rule applies to comments like "no one asked you"... not peoples general unwillingness to participate in a discussion.
That's what we were discussing and it wasn't ongoing, you just jumped in to argue about how the way we choose to do things is wrong in your book.
So basically what you did was actually off-topic because you didn't pay any mind to what we were actually talking about and instead went on a rant about how overclocking is bad. And if you actually paid any attention to the thread topic then you'd know that stock settings are degrading 14th gen CPUs because of the eTVB bug, so tweaking is necessary to protect the CPU from itself, literally, until Intel properly fixes the issues with microcode updates.
Yes I've done that for basically every PC I have, and for others would wanted me to do that for them; from 12th Gen all the way back to the days of Core 2nd Gen. Little to no problems doing that. Mostly because of using decent Motherboards and Coolers; not junk.
But forget 13th/14th Gen junk, never going to have that crap in my house. If my customers want it, that's on them. But at least I have an official warning I can provide to them if they decide to want to go that route and if they ignore the warning, that's on them. I'm also going to let them know that if the CPU goes faulty, they themselves are going to have to duke it out with Intel cause I'm not taking any blame on it or dealing with Intel with this non-sense. The last time I've ever had to RMA a CPU was back in the days of Athlon XP. I think I had maybe 1x AMD FX CPU that was DOA and 1x Intel 3rd Gen 3770K that was DOA; other then that. Very little issues with CPUs over the years, until now. I have not had a single AMD Ryzen CPU come back to me. That's over 1500 system AMD Ryzen builds right there, since 2017.
Now on the subject of Motherboard RMAs, that's a different story. I've had to do quite a few of those over the years. If anything Motherboards and GPUs was the highest % of things I've had to RMA over the last 30 years.
Have an original Pentium and an i386 that still work last I was able to check, have 3rd and 4th gen Core chips that still work, as do basically millions of people.
Raptor Lake was just a colossal screwup.
Some keep saying that all apps and games use the CPU cache to the fullest without doing anything. That is not true at all. First off, your CPU will never perform like it was designed to until after you install the official Chipset Driver. And apps and games actually have to be designed to use that extra cache. Like many old games for example won't touch your L3 cache. Or may not actually benefit from having more, like many of the workstation CPUs have.
Cache only makes a difference based on the load, that's the fatal flaw of 3D V-cache in particular, reason why Ryzen 9 doesn't automatically be as good has less to do with the total L3 cache and more to do with the fact that only a certain portion of the cache can be accessed by each CCX, for example in sections of 16MB per CCX.
The same thing often goes for the lower tiers as well, they're never actually accessing 100% of their cache for a load unless all cores are active on the same load, and if the load actually needs all of that cache to begin with.
People don't understand cache, something like this was tried around two decades ago and it didn't go well, AMD managed to pull it off because the design actually works, and there are a lot more loads these days that can actually make use of it.
The reason some games see a benefit from CPU's with a larger L3 cache is they are coded to optimize their functions for the time in the pipeline when they are in the L3 cache and being processed. All games will use the L3 cache but only some were coded to fully leverage large L3 caches on processors.
We do not need a special driver, or special software to use the L3 cache on processors: Everything is already using it. What those drivers and software do is OPTIMIZE the code to favor the L3 cache. There is a very big difference in terminology there.