I finished building a new PC today and I’m trying to figure out why I’m getting very underwhelming frames even in Dornogal. I’m averaging maybe 35~ FPS with max graphical settings idling in Dorn on even off-peak hours, and I can’t figure out what’s going on. This is isolated to just WoW, and I’m able to play pretty much everything else maxed out with minimal issues. I’ve run benchmarks for both my CPU and GPU and everything looks to be fine, aside from WoW. I tried a clean install of the game a few times, and even without addons, my performance isn’t increasing.
My specs are below, any help at all would be appreciated.
AMD Ryzen 7 9800X3D
NVIDIA GeForce RTX 4070 SUPER
32 GB DDR5 RAM running at 6000hz
This has been happening to me since Tuesdays reset. I still don’t have a fix yet. drivers are updated, removed all addons, nothing wrong with ISP, I even uninstalled wow and battlenet. reinstalled them and it’s still a problem. everything is good for maybe 3 to 5 minutes but then horrible lag and frames, my frame rate gets down to 7.
Try a /console cvar_default after removing all addons. Some settings get saved serverside and could be tied to non-UI exposed graphical settings that are in a state above their defaults. So even if you delete the config.wtf and redo your settings to be the same, some of the hidden cvars might still be affecting your performance, since the client pulls them from the server.
Other than that, there’s probably something else going on with your system. Background apps, overlays in the 30000000 different apps that have them now, drivers, non-windows defender security suites, VPNs/firewalls, under/overclock settings, etc.
They know about it (I think), but for some reason they are not saying anything about it. I was watching a youtube video where this one guy was saying that blizzard put some experimental tech into the game without really testing it. Rather, we are testing it I suppose lol…
I don’t know… Sounds like some tinfoil hat stuff. But this is likely an Occam’s Razor kind of situation where the answer to your problem is likely the simplest one: There’s something going on with your system(potentially the most recent Windows updates) or the saved CVARS (either locally or on the server)
Ah yeah, the FSR bug has been around for years now. Started with the prepatch for DF, if I remember correctly and does cause issues with performance if enabled, even if you only have it set to 99% or 101% resolution scale. Causes a massive drop on the performance ceiling for the client. Like if you look straight up and the sky in some vanilla zone and get say 200fps, with FSR even at 99 or 101%, your fps will drop to like 140 or something.
Came to post about something similar I’ve been experiencing this past week and saw this…
I have things capped at 144fps and used to get around 80 at the lowest no matter how much was going on in a raid/Dornogal (which is still the case when I log in), but the moment I head a few zones away or go into an instance and return to Dorn? Sub 30 at best with horrendous stuttering…and it performs normally up until that point. The tipping point is always the moment I zone into a second raid/instance or return to Dorn.
Relogging fixes the issue but I’d love to know whats causing it in the first place because nothing else I play is affected and it’s consistently happening the same way after the same string of activities.
Adding my name to the list, game ran perfectly fine last night, Monday Dec. 9th, 60fps everywhere, tonight, Tuesday Dec. 10th, can’t even get above 30 anywhere and latency is borked no matter what I do. Tried disabling all add-ons, all drivers are up to date.
Post a DXDIAG report(start+r->dxdiag->enter->save all information) on pastebin and paste the link here and with it still selected, use the </> button above or press ctrl+e so that it.looks.like.this.
Your system has an integrated GPU, it’s possible that wow.exe is running on it instead of your 1650. This can also happen if the Nvidia drivers crash on your dedicated GPU and it falls back to your iGPU. When GPU drivers crash, they don’t always crash to desktop. The following is strong evidence supporting my theory:
+++ WER0 +++:
Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0
* Problem signature:
P1: Wow.exe
and
+++ WER2 +++:
Fault bucket 1773917269249850666, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
* Problem signature:
P1: NVIDIA Web Helper.exe
P2: 11.13.0.0
P3: 5ef97398
P4: NvShadowPlayAPINode.node
There are a bunch of other entries like this as well. So something is likely triggering a TDR on your GPU and chances are, it’s falling back to your iGPU.
I’d give it a shot on DX11 for a bit and see if the issues persist. You’ll likely have a lower overall FPS ceiling using DX11, but it might stop the driver crashes. But since you’re locking to 60fps anyways, you probably won’t notice a difference in max fps (if you disabled vsync, you might find you actually get much higher fps than 60, but since you’re locking to 60, the difference between DX11 and 12 likely won’t end up affecting you).
So I solved the problem, Windows decided to consider a firmware update that updated the system bios an optional update, installed that and everything is fine now. So dumb Windows considered something like that an optional update.
Moral of the story, look at what Windows considers an optional update, it might be something important.
Well BIOS updates can be fickle, so Microsoft tries to absolutely not update them for you unless the benefits outweigh the risks of bricking the system. But I’m glad you got it sorted out.
The 13/14th gen Intel CPUs had a microcode bug with voltage regulation and would slowly destroy your CPU over time. There have also been some critical security holes in BIOSs the past year or two as well. So that’s likely why Microsoft even had it as a suggested optional update.