Seriously, I fully powered off the machine (not just reboot) and it stayed at same memory usage level as when BF4 crashed out to desktop. Being in the IT field for over 20 years I know this sound highly improbable. It was as if the computer was going to sleep and not actually rebooting.
I ended up manually uninstalling the C++ 2012 Runtime verison installed by the video drivers. I then uninstalled the video drivers as well. I shutdown and then installed the 13.11 Beta8 drivers. I figured I would go back to them since I didn't have the problem I mentioned with stuffed memory on reboot until Beta9 drivers and the last update.
Game can sometimes go about 30 minutes, a few maps before memory leak. However, maps like Dam and Flood seem to be a given that it will memory leak by the time the map changes over.
The next time I play and get the leak I'll post the non-paged pool. Right now with things idle it is at 396MB Paged Pool / 99.9MB Non-Paged Pooled. Memory is still steady at 18% utilization.
Using Catalyst13.11 Beta8 drivers. Memory leak occured mid-game about 30 minutes into play. When the game stopped and I was looking at the battlelog screen, I recorded my memory/page use.
In use 5.8GB / Available 2.2GB
Committed 6.7/20.0GB
Cached 944MB
Paged pool 526MB
Non-Paged pool 4.6GB
Previously with 13.11 Beta9 drivers it would get up to 90%+ memory utilization and the whole machine would slow to a grind. However, with Beta8 drivers it appears the leak isn't absorbing as much of the memory. With a sliver of memory left and the computer still responsive, I joined a game to see what would happen and to my suprise the game ran flawlessly for a couple hours. I exited the game under my own will, so it was nice to have a couple hours of play without issue.
In use 5.6GB / Available 2.4GB
Committed 6.6/20.0GB
Cached 940MB
Paged pool 527MB
Non-Paged pool 4.5GB
A quick reboot and the memory is freed up. I can live with one memory leak crash to the desktop over the span of about 3 hours.
