machofreek, sounds like you're suffering from something other than the memory leak (or more than just the memory leak). There is no way BF4 can use up your memory on a fresh reboot when it hasn't even been loaded yet.
You're doing a full reboot, what is your Non-paged pool at before loading anything?
Just to recap, I've been going strong for 4 days now I think, no crashes at all (besides servers crashing, great $100 investment EA, god forbid you give us some money back on your bloated server prices when you exclude us from quick join just to be able to move people to squads and use team balance mods)
I did the registry edit mentioned here, that didn't help, then I did the Windows 7 compatibility mode and disabled the display scaling in the compatitiblity tab for BF4.exe and haven't had the leak since.
Windows 8.1 Pro with WMC
XFX Radeon 6970 with 13.11 Beta 9.2 drivers
8GB DDR3 1866
Intel i7-2700k @4.7GHz
Asus P8z77-V LE
Corsair Force GS SSD
Page File is disabled
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.
Running BF4(x64) in windows 8 compatibility mode seems to do the trick. Now if only AMD would do something about it.
I'm using a 6970 on windows 8.1.
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.
@machofreek wrote: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.
I have an Sapphire 6850.
I've had the same memory usage problem... if I immediately shutdown, and I mean totally shut down my machine, and wait only a half minute or so before booting my machine back up, the memory usage is still at the same 80%+ that I left it when bf4 slowed to a slow stutter. Very odd. If I shutdown and don't touch my machine for a good long while after a bf4 memory spike, the computer boots up with the memory usage being fine.
I am on guard now; whenever I play bf4 (when it lets me play for more than 7 minutes before crashing with a bf4 has stopped working error) and I start to see even the slightest choppiness, I exit the game and check my memory usage. It is usually at about 80% at least (of 16 gigs). I have seen it go to 98%. tonight I was able to play one full map and most of the way through a second round of conquest before the memory usage became a burden.
It has to be because we all have 5000 or 6000 series ATI cards. If anyone is having this problem who DOES NOT have a 5000 or 6000 series ATI card please respond.
I spoke to EA today and tried to get my money back on my premium and bf4 pre-order. That was a fail... I will repost when I get my new ATI card from newegg and try that out.
We have to report the error so that they know
http://www.amdsurveys.com/se.ashx?s=5A1E27D25AD12B60
@AskEASupport
@AMDRadeon
@thegaze wrote:
@machofreek wrote: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.
I have an Sapphire 6850.
I've had the same memory usage problem... if I immediately shutdown, and I mean totally shut down my machine, and wait only a half minute or so before booting my machine back up, the memory usage is still at the same 80%+ that I left it when bf4 slowed to a slow stutter. Very odd. If I shutdown and don't touch my machine for a good long while after a bf4 memory spike, the computer boots up with the memory usage being fine.
I am on guard now; whenever I play bf4 (when it lets me play for more than 7 minutes before crashing with a bf4 has stopped working error) and I start to see even the slightest choppiness, I exit the game and check my memory usage. It is usually at about 80% at least (of 16 gigs). I have seen it go to 98%. tonight I was able to play one full map and most of the way through a second round of conquest before the memory usage became a burden.
It has to be because we all have 5000 or 6000 series ATI cards. If anyone is having this problem who DOES NOT have a 5000 or 6000 series ATI card please respond.I spoke to EA today and tried to get my money back on my premium and bf4 pre-order. That was a fail... I will repost when I get my new ATI card from newegg and try that out.
What you're describing is very easy to explain if you are using Win8 or 8.1. Although if you are in IT for 20 years you should already know that. Windows 8 does not really 'shutdown' if you shutdown instead of restarting. It's made for quick booting and preferrebly touch devices so what they did is replace the shutdown function with sleep or standy in some ways, even if you unplug the machine. If you shutdown and start the PC again the kernel is not restarted anymore and it's pretty much as if you never shutdown, so you have to restart instead of shutdown to clear the memory. That's also the reason why you have to restart the computer after important updates and it is not enough anymore to shutdown in the evening and start in the morning and all updates are happy...
Yep, and you can disable windows 8's "hybrid shutdown" feature in the control panel:
Control Panel > Hardware and Sound > Power Options > Choose what the power buttons do > "Change settings that are currently unavailable" > and uncheck "turn on fast startup".
