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
But note that you're not really going to see huge gains from overclocking ram in general nowadays (unless in very specific circumstances). What you're going to see the biggest gains from is switching from some automatic downclock (which does happen on some motherboards) to the timing and speed the ram actually should run at. Or else from a bad overclock to a stable timing.
This is the same between AMD and Intel.
Once upon a time, overclocking to get to 30fps, or to reach some 33ms on a thread response, was a huge challenge. And the payoff was there, right.. So it was worth it to burn a few k6s or 3dfx ram chips to manage a really good overclock.
Now, though - you don't need to overclock: you need to underclock, so the boost thresholds are higher, to better shave off the fps-drops at the fps-target. And the amount of just complete idiocy that turns up - even on OEM-specified boxes that come with specific overclocking tools set by the OEM - is just amazing.
It's like people are just getting inversely twice as dumb as tech gets faster or something.. Moron's Law..
So you just overclock your pc and got fps boost.
This not connected to ingame problems anyhow
My words of advice: it is futile to try to argue with reason with those kind of people, no matter how right you are.
Even my stuff gets ignored, where I tell people to clean up their cache, and people just reply with that the developers should do it. So ~ save your nerves. Not everyone can be saved.
Not all CPUs can run crazy high Infinity Fabric speeds, usually 1800-1900MHz, so 3600-3800MT/s is about as high as you'd probably want to aim for without going too deep down the overclocking rabbithole and potential issues.
3600MT/CL16 is usually the go to for Zen3. It's cheap and most CPUs will do 1800MHz Infinity Fabric out of the box. If you want more performance, just bump the voltages up and lower your timings.
No, the logic is sound, right. Because the car will run around on the back roads in second gear just fine. It's when you rev it up for the first time ever that it blows up, and that's going to happen at that same highway every time.
It's probably just wonky code that uses way too much CPU power for whatever reason and is made worse by the GameGuard crap.
A game that has a single thread running on one core (the back roads) is not going to run into as big issues. But everything else, any Unreal Engine game, anything running with multiple threads, anything with resubmits to gpu ram, anything with realtime physics - literally anything whatsoever made in the last couple of decades, with some notable exceptions (COD, for example) is going to run badly with a setup like that. The single-threaded wonders are also going to have issues if you then run screen-captures or discord on the side. Any amount of network issues will turn up if you suddenly get really low timing response on device drivers. Sound stuttering should be a regular occurrence, hilarious fps-drops, total lack of peak fps thanks to gpu never being saturated, etc., etc. These issues will happen. They might not be terrible and obvious right away in some cases - but they will still be there even if you run something really light.
I.e., the car will have been badly tuned. And it will blow up on the same highway every time, because that's where you rev the car.
I myself haven't done that in a while.
I see that people are talking about the advantages and what not. That's great. I see people not wanting to do what I got posted here and just blame and wait on the devs to fix it..
That's up to you. But you can potentially fix it yourself.
Then again it comes down to a lot of other issues that I have seen over the past.. say 5 to 10 years. People are getting damn lazy and do not want to do anything for them self and want someone else to fix it.
I gave people an option that may help, but are too lazy or stubborn to do it on their own.
I'm sure these are the people that just complain about something just to complain about something.
Anyway, I tried to help. But that's as far as I'm going.