I usually get around 100 FPS at 1440p, Now I get about 10 and much less sometimes. What happened?
3080 TI
Roll back the update?
2 Likes
check the settings some times it sets settings to weird things. Remember there are three places Nvidia, Windows, and WOW any of these could be it. At one time the recommend settings from Nvidia gave me bout 10 fps too.
2 Likes
Nvidia’s Geforce Experience or the new app(does the same stuff) has a bad habit of randomly setting your foreground and background FPS limits to the wrong values. For some, it ends up setting the foreground to what the background should be, which is usually 8.
Check your WoW settings and you’ll likely see this. Go into the Nvidia app and disable it from automatically adjusting WoW, as it will keep trying to do this until you stop it or do some kind of manual override on it the profile.
1 Like
This is happening to me too. How do I adjust the Nvidia settings?
So what was happening to me is I was using a weakaura with a texture that was not supported by the new NVidia drivers. It was giving me a BSOD. Check weakauras. It was a DH metamorphosis animation texture. Took me forever to figure it out. Thanks for the suggestions everyone.
1 Like
i’m lucky if i can log in without the game crashing since last wow update.
things have been a train wreck for like the last 2 months. most of the time 1/2 the FPS i used to have.
apparently a $700 intel CPU makes games crash because intel has incompetent engineers
and apparently a $2,300 nvidia video card has incompetent driver & app developers behind it
apparently microsoft employs incompetent engineers who can’t stop breaking intel and nvidia running windows with updates
ENJOY!!!
a texture not supported? lol are you high bro?
Possibly a texture that was changed in the game client and the WA didn’t have the update for the new one or new location.
1 Like
Wouldn’t be the first time.
There was a change to how the nvidia driver dealt with .tif files not long ago that caused the 3D art program I use to CTD when you hit the render button to start the render engine.
They changed it again so all the textures or control maps that used .tif files had to be changed again cuz they started crashing again.
So 2x in row we had to change the way we work with .tif files for textures/control maps cuz of nvidia changes to the driver causing BSOD or CTD with them.
When it first started happening we went thru all the “it’s your hardware, you’re overheating the CPU or GPU or both, your drivers are too old, ect,ect.”
I found it one night by stripping an object of all its textures and methodically adding them back in one by one and trying to render between each step.
I got to be the hero of the day 
Was so proud of myself. We were all stumped for nearly a week.
Likely has to do with some kind of exploit prevention, but it could have also been some change or bug in how they handle some types of data precisions or operations. Tif files are a weird one because they are almost like a mini file system and you can do a lot of stuff using extensions. It would make sense that they would be sensitive to changes like that and it would also make sense from a security standpoint, why they’d have to patch out potential exploits.
Just so everyone knows
There’s a security issue with nvidia display drivers
https://nvidia.custhelp.com/app/answers/detail/a_id/5614/~/security-bulletin%3A-nvidia-gpu-display-driver---january-2025#:~:text=NVIDIA%20GPU%20display%20driver%20for,of%20service%2C%20or%20data%20tampering.
Read thru this and decide for yourself if an older driver is an acceptable risk for you or not before rolling back.
1 Like
And to think a technology so faulty controls so much
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.