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
https://www.radgametools.com/oodleintel.htm
https://community.intel.com/t5/Processors/Regarding-Reports-of-13th-14th-Gen-Unlocked-Desktop-Users/td-p/1575863?profile.language=en
https://www.reddit.com/r/intel/comments/1egthzw/megathread_for_intel_core_13th_14th_gen_cpu/
Ignore the game in link actualy , its an problem with Intel processors only...
--Update 2--
Thanks to djbatoradr here is a better solution.
Right-click on the game app executable, and then on properties, then under compatibility, disable full-screen optimizations.
It's a well known Intel problem at this point:
https://www.anandtech.com/show/21484/intel-raptor-lake-instability-faults-voltage-microcode-fix-in-august
Updating the UEFI does nothing, as it's a band-aid fix to lower frequency and power under low usage (desktop, web browsing etc..) to make sure the CPU doesn't really see issues till after the warranty period. It's a dirty underhanded move by Intel to save money at your expense.
The only solution is to lock your P-cores to the default frequency based on your CPU (14900K should be 57 for 5.7GHz, 14900KS 5.8 or 5.9GHz, as an example). In your BIOS/UEFI disable core boosting tech, enforce all limits, and set what you want for PLL1 and 2 (limit amperage a little higher at 500 since I'm direct die cooling and don't want power to limit my frequency, only temps which I've never seen above 83C during Cinebench). Set the Vcore in BIOS to 1.35 or use an negative offset to keep to safe voltage (I'm using an -0.08 offset) and benchmark your CPU with the Intel tuner and AVX2 along with Cincebench to ensure you're stable at a reasonable voltage (FAFO in BIOS till you find your sweet spot). Enable a power plan in Widows that doesn't lower core frequency so you don't have insane transients as cores lower and rise in frequency.
The entire problem stems from the VID tables being crap. They're often requesting voltages up to 1.6 Vcore for a single-core 6GHz boost and running all P-cores at or close to 1.5V 9which is substantially more than what's needed). All to boost a core or two to 6GHz for two lousy seconds so idiot tech tubers can drool over da 6Ghz (which they did for months).
Benchmark your CPU sometime and note how little 5.7GHz all core makes vs 5.7GHz with one core boosting to 6GHz for brief periods, it's a nothing burger. Even all core 5.8 or 5.9 vs 5.7 benchmarks are in margin of error territory with 1% and .1% lows in games. And those 1% and .1% lows are the critical thing for preventing hitching.
You can leave your E-cores alone and let them run as normal as there's no problem there. Just use something like CoreDirector to park the E-cores for games that benefit from such a situation due to weird scheduling issues. While getting the extra threads for other activities along with the games that don't have issues (there are some that see benefits with E-cores eneabled)
Do not however use the software fix listed buy the OP. That doesn't remedy the underlying issue of too much Vcore degrading the P-cores of your CPU causing irreparable damage over time. It's a placebo, because the pre-cache worked. The CPU will still be degraded and worsen as time marches on without applying the steps above.
The previous UEFI revisions fixed the out of spec settings on certain motherboards.
No, it doesn't. When boosting, the Vcore still exceeds recommended voltages. You're providing incorrect information. All Intel did is override Windows' Power Setting to force the CPU to downclock when idle or under extremely low usage scenarios.
If you don't set your Vcore and lock the P-cores. You're still going to end up with a degraded or dead CPU.
https://www.youtube.com/watch?v=pmpYyGWNd6w.
Good luck.