EDIT2: Guess it was more than just the config file. It had more to do with shaders needing to be recompiled or something. Once it was all done, the game boots fine and only lags out for the first 20 or so seconds, before running smooth again.
EDIT: Partially solved: If blues see this, it turned out to be super simple to fix. Deleted Documents\Overwatch\Settings\Settings_v0.ini and it resolved the problem entirely. I guess it didn’t automatically throw the typical “Hey we’ve detected hardware changes, would you like to reset everything?” that games do. The game is now running super smooth!
I recently upgraded from an Nvidia GTX1650 to an AMD RX 6600. Before the upgrade, the game ran 100% fine and I never had any issues. Buttery smooth, at medium settings, locked to 60fps. Since upgrading to the AMD card, OW2 bugs out as soon as I launch it. It goes into 100% CPU usage and the commit ram just keeps climbing and climbing. I can watch this with an afterburner overlay set to show it all. So it’s definitely a memory leak.
I’ve DDU uninstalled the drivers. I’ve tested both Adrenalin 22.5.1(recommended) and 22.11.1(optional) drivers, with DDUs between tests. I’ve fiddled with just about every setting in the drivers, turning everything extra off and doing a factory reset to the drivers.
I’m on Windows 11 22H2, fully up to date on everything. No excess softwares running, no background tasks, etc. I’m normally the person that helps people with this kind of stuff, so I’ve ran through all the typical tests. I’m not really seeing this issue in other games. Oh and I’ve also done a reinstall of the game and reset the settings to default, from within the game.
4 Likes
why would deleting that fix the problem i’m having the same problem:<
Because I think that it had my old Nvidia card stuff in there or something specific to Nvidia in it like Reflex+Boost or something along those lines. Maybe the GPU information was wrong as well, I don’t know, but it 100% fixed my problem and now I’m playing the game on ultra with buttery 120-144hz frame rates and the CPU/memory issues are gone.
On the afterburner overlay, when it was bugging out, you’d see a really nasty high speed square wave. The frame rate would say I was getting like 70fps or something, but it felt like 20. I’d almost bet money that it was some vestigial Nvidia setting still saved in there that doesn’t work on AMD cards, like reflex, that the OW engine was trying to use still.
1 Like
okay thank you i will try this later! 
The settings ini contains settings including GPU identification for example:
[GPU.6]
GPUDeviceID = “8583”
GPUName = “NVIDIA GeForce GTX 1650 SUPER”
GPUScaler = “6.000000”
GPUVenderID = “4318”
If you upgrade your GPU but the file still has saved settings from the prior GPU it can cause issues, this is most likely to happen if you switch from a GPU from one vendor to another.
u mean “vendor” is nvidia and amd?
I had a problem with certain graphical assets like cooldown icons appearing scrambled since last week’s patch and deleting Settings_v0.ini fixed my issue as well.
I haven’t upgraded anything recently, though.
During this quest of solving the issue, I found some other interesting stuff out:
I guess it’s not actually a memory leak, it just looks like it. I’ve this tested pretty heavily today and the main difference between the 22.5.1 and 22.11.1 drivers is how long it takes to saturate the commit load. Both will try to reach some amount total commit load of around 13GB(total for whole system that counts other things running as well). The difference is that the older drivers do this in like 20-30 seconds and the new ones take minutes to reach it. Once it reaches that allocation, the CPU usage drops to like 5% on both drivers. The game still takes a while to close fully from the task manager. It seems to boot faster the next time, but I’m pretty sure that’s just because there’s still some left over chunk in the page or something. I think it goes back to slow booting on the first launch after a restart, but I’d have to double check.
I’m not sure what it’s trying to saturate in there, maybe shared GPU reserve? Don’t know, but I sure as hell didn’t have this problem on my Nvidia card. Still seems like some kind of bug or something looping out of control.
Correct.
Typed this sentence because 20 characters are required to post.
Hey just as another update, after rebooting the PC multiple times, the game load time is still down to like 15-20 seconds again, even on the new drivers.
Guess it was just compiling shaders or something? Saw it doing stuff with the dxcache and was like oh… That makes sense… Though I will say it took much much longer to do with the 22.11.1 drivers than it did with the 22.5.1 drivers. At least it’s not like Warzone where it takes 10-30 minutes.
1 Like