Forum Discussion
Disabling NDU doesn't fix this as is already mentioned in this thread. The reason it's too much too read is probably because EA is too late to respond to this.
To get ahead of other non-contributing EA posts, and to give you a short summary:
- It's also not Battlelog related, because closing battlelog when BF4 launches doesn't make a difference.
- Also as you could have read thousand times most of the victims here are using the latest AMD 13.11 Beta v8 driver. However, the stable 13.9 driver has the same problem.
- The BF4 Beta didn't have this problem, it's only in the full version of BF4
- Disabling virtual memory in Windows doesn't fix the problem, it only caused a crash after the memory gets filled up
- Tried the BF4 in Win7 compatibility mode yesterday, didn't get a memory leak, yet. Somebody else who can falsify this as a possible temporary solution?
However, good to see that EA is finally looking into this. Hope you all had a peaceful weekend..
Yeah the NDU fix did turn out to not fix it for me, I had gotten lucky after applying it and the bug happened to not trigger after a very long BF4 session, so I was pretty sure I had fixed it because I had typically run into it after around an hour or so. A few days later it happened to me again (I alt tabbed out of a game and noticed 8 gigs of ram in non-paged pool memory usage so I was able to reboot before it used all my ram that time). One thing I noticed is the leak seemed to happen pretty quickly, starting at the end of the match. I had alt tabbed out during the match, towards the end and the mem usage was normal. alt tabbed out again at the very end, and 8 gigs were in non-paged pool all the sudden, so it doesn't seem like a very "slow" leak. All the times it happened previous to that I noticed the lag started near the beginning of a new map, so I suspect the leak triggers around the end of a map, and the symptons can begin on the next map once it fiils your memory. It doesn't appear to be map specific, at least not that I can tell.
So far after applying the win7 compatibility fix (and in addition I'm using the 32-bit exe) I haven't triggered it again after another long session and a few subsequent shorter ones, but its very hard to tell with this bug since its so random, and a few others have said this hasn't worked for them (such as the post right above mine!). I'll try playing more today.
This bug is tricky because you can't really reproduce it "on demand", it just kind of happens randomly ☹️