As this issue seems to have been resolved with new drivers I'll mark this thread as solved now.
Hey folks,
I've spent A LOT of time on this and now I'm confident to say that I've eliminated the issue on my machine.
Specs: i7-920@3.8Ghz, 6GB RAM, 256GB SSD, Sapphire ATI 5850 1GB, Win 8.1Pro 64b (legit)
Drivers: 13.12
I've applied these 3 'fixes', and the issue is now gone for over a week (cca 20 hours played):
1) Disabling NDU monitoring
Open up "regedit" and find:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu
Change the "Start" value to 4
2) Launching the 32b version of the game
Open Origin, rightclick BF4, properties, set it to launch x86 version
3) Adjusting the page file
Go Control Panel\All Control Panel Items\System > Advanced System Settings
Advanced tab > in Performance section click Settings > Advanced tab > in Virtual memory section click Change
uncheck Automaticall manage, select Custom size
I currently have it set as 2048-4096MB (1/3 and 2/3 of total RAM) and I have no leaks and no 'low memory' popups/freezes.
This seems to had the biggest impact, play around with the values.
I've started on 256MB (the cache of my SSD) and the worked my way up.
I'm not certain if all 3 are required, but I'm not touching anything as it now works for me now 🙂
As I was testing the RAM as well and had different amounts of RAM in, the page file needed to be changed to different amounts for the game to stay stable.
I can't explain but for 20GB RAM a page file of 256MB has worked.
For my own 3x 2GB sticks the setting of Initial size = 2048MB and Maximum size = 4096MB works.
Have a go, change the value, restart and run the game to see if it works for you.
If you get the error messages, increase the page file size, if it leaks it is too much.
I hope you can find the balance 🙂
Thumbs up to people who came up with the tips.
Fingers crossed.
[this was also posted in this thread]
@yoshonesk wrote:Hey folks,
I've spent A LOT of time on this and now I'm confident to say that I've eliminated the issue on my machine.
Specs: i7-920@3.8Ghz, 6GB RAM, 256GB SSD, Sapphire ATI 5850 1GB, Win 8.1Pro 64b (legit)Drivers: 13.12
I've applied these 3 'fixes', and the issue is now gone for over a week (cca 20 hours played):
1) Disabling NDU monitoringOpen up "regedit" and find:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\NduChange the "Start" value to 4
2) Launching the 32b version of the game
Open Origin, rightclick BF4, properties, set it to launch x86 version
3) Adjusting the page file
Go Control Panel\All Control Panel Items\System > Advanced System Settings
Advanced tab > in Performance section click Settings > Advanced tab > in Virtual memory section click Change
uncheck Automaticall manage, select Custom size
I currently have it set as 2048-4096MB (1/3 and 2/3 of total RAM) and I have no leaks and no 'low memory' popups/freezes.
This seems to had the biggest impact, play around with the values.
I've started on 256MB (the cache of my SSD) and the worked my way up.
I'm not certain if all 3 are required, but I'm not touching anything as it now works for me now 🙂
As I was testing the RAM as well and had different amounts of RAM in, the page file needed to be changed to different amounts for the game to stay stable.
I can't explain but for 20GB RAM a page file of 256MB has worked.
For my own 3x 2GB sticks the setting of Initial size = 2048MB and Maximum size = 4096MB works.
Have a go, change the value, restart and run the game to see if it works for you.
If you get the error messages, increase the page file size, if it leaks it is too much.
I hope you can find the balance 🙂
Thumbs up to people who came up with the tips.
Fingers crossed.
[this was also posted in this thread]
This maybe early but I think this one WORKS for me.
Before I couldn't even play 3 rounds of TDM properly, but after I applied all this, alt-tabbing before map loads like puurlucky mentioned, I can run 5 whole Rush round without the leak.
I will try again tomorrow because this is getting pretty late where I am.
I've tried most of the fixes here and the alt-tab is the only one that shown any differences. It may be there are multiple issues that differnet people are seeing, but the AMD video related one seems the most prominent.
Changing the NDU is unlikely to have any effect as it's unrelated to the video drivers
Runningn the x86 version may or may not make a difference. For me it hasn't, and as the video drivers are independent of the version of BF you run, that could explain why this doesn't work for most (any?) people
Changing the page file will have absolutely no effect as the bug is happening with non-paged memory, i.e. memory content that specifically DOESN'T get sent to the page file. As for setting it to various random values that match other bits of memory numbers on your computer, there is no purpose behind that at all. if you really want to learn more about windows memory and page files, try this http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx
if you think you have a fix that has worked, and you would like to really help everyone, then please test that your fix really has fixed it, don't "get it working" by making multiple changes and then saying you're never touching it again. If you really want to help, you need to then undo each change until it breaks again, and using a process of elimination work out exactly which change is the one that fixed (or helped) it.
>> if you think you have a fix that has worked, and you would like to really help everyone, then please test that your fix really has fixed it, don't "get it working" by making multiple changes and then saying you're never touching it again. If you really want to help, you need to then undo each change until it breaks again, and using a process of elimination work out exactly which change is the one that fixed (or helped) it.
Agreed. I am trying the registry tweak as it appears this has an effect on windows in general outside of BF4. There's no way the paging method can work for the reason you have suggested lol.
What I don't understand is that I have two friends that have an R9 290 and an R9 290X and they dont get the same issue as me (I have an R9 290). It's extremely frustrating, but I literally dont get this with any other game. That said, I doubt there's a game out there as complex as BF4 to be perfectly fair to it!
I'll let you know if the registry tweak works.
guy's I have win8.1, 64 bits and ATI card5870 and as many of you, constant crash on BF4, so far I was using Windows seven and had never any problem with BF3 with w7 32 bits and same HW, then I moved to win 8.1 64bits for the beta and while I had no single issue with the Beta when they release the game I have started to get constant memory leak and 32gb of meme occupied at 95% up to 99% when the leak occurs
I'm playing 4 to 5 hours a day and I'm getting in average 2 reboot during this time.
I I dont play BF4, I can work days and night, watching TV playing other games, no single problem
All of this to say I had already used the tweaks mentioned some posts before about the :
-ndu
-run game in 32 bits
-and increase swap space
And it did not fix at all the problem
I can only say it is related to the combination of :
using win 8.1, most likely 64 bit edition only, an ATI card and driver, in conjunction with BF4
What I also did is to test almost all ATI drivers from the fresh install windows 8.1 up to the newest beta xx (all the releases) and strangely the occurences of symptoms differs from release to release but at the end always either :
- an error warning on Direct X when computer RAM memory is filling up "E8OUTOFMEMORY Direct3D could not allocate sufficient memory to complete the call".....
- a BF4 stall when playing and then memory filled up, sometimes requires a hard reboot (push button), because no access anymore to the system
- a blue screen reboot by Mr gates himself....
- Or a failure at map swap
The one I found most stable is finally the one that comes with a fresh install of windows 8.1, not the latest drivers.....unfortunately
Just one thing come to my mind, I never played with graphic options of the game, may be one of those is buggy and cause the leak by not releasing memory above 4GB (Driver reserved space, I understood), I'll try it, we never know.
I keep you posted but I dont believe anymore in ATI and/or Dice capability or willingness to solve it
