Blur Busters Forums

Posted: **05 Apr 2025, 13:47**

Expo can easily be unstable. Set 6000 32-38-38-80-118 1.35v as a test on how less stutters it have
Probably ram is super hot

Posted: **05 Apr 2025, 15:16**

While it may be fixed by tweaks, get ready for the hard stuff as Plan B. Pray you aren't afflicted.

Now that you say it may be system, check the oddball stuff:

- overheating rapid thermal throttling in CPU or GPU or SSD or RAM?
- does it improve during underclock,
- does it improve during component reseating,
- does it change over time (better on cold system that's just booted up),
- is thermal pastes and temps ok everywhere?
- bad component or loose connector generating error-correction spikes
- common causes of internal electfical interference: try to keep your power bricks and electric wires away from your computer & data wires.
- Check the PC power supply unit is high quality and not defective too. Random voltage noise can lead to random performance (etc) as the system ECC's or tries to compensate without crashing. Also try reseating and tightening the connectors
- Try an OS reinstall (use a disk swap if you want to preserve going back easily to your old setup; also doubles as opportunity to test SSD defects/overheating creating sudden temporary disk seek latency spikes. Where in 1 in 100 disk reads may suddenly take 10ms (like M.2 SSD under a hot GPU with GPU fan blowing at it)
- Maybe swap GPU's temporarily and see what happens too? NVIDIA uses memory-repeat-reread error correction in GDDR6, overheated GDDR6, try forced underclocks. Framerate caps often cools things down
- One person fixed things by changing fan flow layout. Air flow too can avoid computer part warranty claim if you find something mudane that's self resolvable
- or it may be just a bad component that need RMA
- it may not be temperature related, but at least verify
- It may not be electrical interference related, but it's still a good idea to at least check for loose connections (both power/data/ram/pci/edge connectors), too-close electrical stuff, bad power rail/port/cable on PSU to GPU creating power sag, bad internal electrical part like defective PSU or bad VRMs on your equipment (component swaps: ugggh)
- etc

Not saying any of it is it, but you're going to need to go left-field now. Focus on the real odd problems that still frequently or occasionally happens to systems.

Start with the easy stuff. Keep a paper or smartphone logbook.

Posted: **05 Apr 2025, 17:12**

There is no way around the shader compilations other than maybe a shader cache. Sure, getting the hardware right is a foundation for every game, but it can't fix a broken game. Competitive games should never compile shaders during gameplay to begin with (in the same frame they are used to render). Maybe they'll fix this in their dx12 version.

Posted: **06 Apr 2025, 07:14**

0xfffffffadc wrote: ↑
04 Apr 2025, 02:15
I play Overwatch 2 on very low settings (lowest graphical settings, 70% render scale, etc), and despite tweaking almost every setting in the game, my frametimes always seem to spike to around 6-10ms (despite an average of 1.5ms), resulting in unpredictable 1% lows.

My specs:
- 9800x3d
- 5070 Ti Ventus 3x OC
- X870 Tomahawk (7E51v1A3, before updating I had the same issues though)
- 32GB DDR5 Trident Z5 CL28 6000MHz (F5-6000J2836G16GX2-TR5NS)
- MPG A850GS 850W
- 1080p XG2431 240hz
- Windows 11 24H2
- Samsung M2 990 Pro 2TB

No matter what I've tried, my CapFrameX always has graphs like the following (attached), with somewhat consistent 1.6ms averages, but spikes to 6-10ms.

Essentially, my 1% lows are always around 200-300 FPS, despite my friends on worse hardware being 350-400. Additionally, there seems to be these somewhat aggressive spikes to 6-10 ms, every few ms.

My question: Are graphs like these normal? My friend sent me their CapFrameX and it was very smooth, with only one or two spikes (like the ones that show in mine) for an entire 30 second capture. What can I do to remedy these graphs? I've tried analyzing my entire system by starting a Windows Performance Analyzer capture at the same time as CapFrameX and cross-referencing spikes, but it's hard to find any culprits.

I've done a lot of tweaking and optimizing for my system to try to fix this issue. I'm at the top 5% of TimeSpy for my CPU/GPU. A list of some of the stuff I've tried:

BIOS / Overclocking
- pbo advanced, limits "motherboard", `-20` curve offset, `+200` clock
- ram: EXPO enabled (got mem latency from 92ns to 82ns), set trefi to 50k (got mem latency from 82ns to 72ns in AIDA 64)
- disable onboard wifi/BT
- disable SVM mode (make sure not using passkey in win11 or might get locked out due to TPM)
- update bios to latest version (A30)

OS
- remove MSI center stuff (e.g. mysticlight). u can set RGB and uninstall it
- disable a lot of services
- disable integrated graphics / wavetable synth / HPET / unused sound devices in device manager. basically anything unused should be disabled
- nvidia power max performance
- windows power plan: ultimate performance (with some stuff changed like 100% min processor state)
- remove xbox game bar
- disable unused network adapters
- disable cortana and web embed in windows search using group policy
- network adapters disable ipv6
- adjust appearance and performance of windows -> disable all except "smooth screen fonts"

And quite a bit more. My LatencyMon averages were like 3.0µs, 0.9µs for average interrupt to process latency and DPC latency, respectively. The only drivers that seemed to have the highest average interrupts were Nvidia ones. I can try NVCleanstall but I really think there's some larger issue here.

Ok friend. How do you take your measurements, I'm talking about these graphs. Is it raw gameplay or replay code? I'm talking about replay. It matters.
I suggest you take the replay code and take measurements (on minimum graphics settings). Do it with an FPS lock, for example 300 frames and no limit. Then give the replay code to yours friend and your friend and he will do the same. Then take your friend's performance graphs and compare them with yours.

Posted: **06 Apr 2025, 10:39**

i had the same issue with spikes in fortnite!
mine fixed when i enabled back the hyperthreading.
cpu i7 7700k
u can give a try if u have disable the hyperthreading.

Posted: **09 Apr 2025, 08:28**

Hi, just messaging to say that I encountered the same issue in OW2 on an RTX 3080 and 7800x3D CPU. I used EXPO1, no OC and generally I saw much lower 1% lows than the average fps (I was capping to 230 on a 240Hz screen and seeing dips to around 180).

I'm not sure if this is indicative of an actual issue or if it's just the game.

Posted: **10 Apr 2025, 05:57**

I've found a benchmark exhibiting the same behaviour that we're experiencing:
https://www.youtube.com/watch?v=gtv_RK1ecAQ

It's possible it's just a more common setup issue than we think, or it's possible that the X3D CPUs do just experience worse 1% lows in OW2. I'm not sure until I find a benchmark with competitive settings and 1% lows posted

Posted: **10 Apr 2025, 07:53**

Maelstrom wrote: ↑
10 Apr 2025, 05:57
I've found a benchmark exhibiting the same behaviour that we're experiencing:
https://www.youtube.com/watch?v=gtv_RK1ecAQ

It's possible it's just a more common setup issue than we think, or it's possible that the X3D CPUs do just experience worse 1% lows in OW2. I'm not sure until I find a benchmark with competitive settings and 1% lows posted

Have you tested with the replay code?

Posted: **10 Apr 2025, 09:43**

Maelstrom wrote: ↑
10 Apr 2025, 05:57
It's possible it's just a more common setup issue than we think, or it's possible that the X3D CPUs do just experience worse 1% lows in OW2. I'm not sure until I find a benchmark with competitive settings and 1% lows posted

No, it's because frame rate limiters are implemented subpar in a majority of games.
The only games which I've seen that do it right are Reflex & Diabotical.
It can also be caused by improperly set-up RAM timings which lead to severe frame rate issues in 1% & 0,1% lows.
As mentioned by a user here, even EXPO may lead to performance degradation (macrostuttering & microstuttering) due to no guarantee that the IMC & motherboard can sustain those specific timings.

The X3D CPUs can only be beneficial for any workload due to the larger L3 cache.

To touch on the RTSS UI that you use as gateway to evaluate performance, I hope you understand that it also causes performance degradation and that it doesn't capture the data in real-time.
To accurately evaluate how a game performs and whether there are any anomalies, one has to use PresentMon-based tools (PresentMon CLI / GUI, FrameView, CapFrameX,...) and rely upon either the built-in or custom graphing solutions to represent the data you've acquired.

rooy wrote: ↑
06 Apr 2025, 10:39
i had the same issue with spikes in fortnite!
mine fixed when i enabled back the hyperthreading.
cpu i7 7700k
u can give a try if u have disable the hyperthreading.

This is already well-known.
Disabling Hyperthreading leads to a reduction in total system latency, but it also leads to lower single-threaded performance due to a software bug in Windows
Enabling it restores the overall single-threaded performance back to it's original states.

All games scale up with core count, 8 core CPUs are the bare minimum to use in the modern esports scene.
Once the rumoured Zen 6 12C/24T X3D CPU gets released (11800x3d, I assume), you'll see what I mean.

Posted: **11 Apr 2025, 08:14**

kyube wrote: ↑
10 Apr 2025, 09:43

Maelstrom wrote: ↑
10 Apr 2025, 05:57
It's possible it's just a more common setup issue than we think, or it's possible that the X3D CPUs do just experience worse 1% lows in OW2. I'm not sure until I find a benchmark with competitive settings and 1% lows posted
No, it's because frame rate limiters are implemented subpar in a majority of games.
The only games which I've seen that do it right are Reflex & Diabotical.
It can also be caused by improperly set-up RAM timings which lead to severe frame rate issues in 1% & 0,1% lows.
As mentioned by a user here, even EXPO may lead to performance degradation (macrostuttering & microstuttering) due to no guarantee that the IMC & motherboard can sustain those specific timings.

The X3D CPUs can only be beneficial for any workload due to the larger L3 cache.

To touch on the RTSS UI that you use as gateway to evaluate performance, I hope you understand that it also causes performance degradation and that it doesn't capture the data in real-time.
To accurately evaluate how a game performs and whether there are any anomalies, one has to use PresentMon-based tools (PresentMon CLI / GUI, FrameView, CapFrameX,...) and rely upon either the built-in or custom graphing solutions to represent the data you've acquired.

Sure but I'm taking the OP at face value when they claim that they are aware of other users with significantly better 1% lows. If it's just a game specific issue then I'd not expect a discrepancy between systems. Your other suppositions fall under "it's possible that it's just a more common setup issue than we think", so I'm not sure why you start your comment disagreeing with me.

At this point I'd just like a single positive example where someone is benchmarking OW2 on an X3D CPU with good 1% and 0.1% lows before (recommending) spending significant time and effort diagnosing their system since it's more likely that there is nothing behaving incorrectly.

Blur Busters Forums

Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows

Re: Powerful system (9800x3d, 5070 Ti), but Overwatch 2 on the lowest settings has suboptimal 0.1% / 1% lows