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..
- 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?
its works since bf3
- 12 years ago
@CowboysTR wrote:- 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?
its works since bf3
Well, this is BF4. Finding solutions is a deductive process, not just inductive.
I've read some reports about people on Win7 having the same symptoms. Don't know if the source of these symptoms is the same as with all these Win8 users. I don't have the time today to play BF4 long enough to trigger the memory leak (probably), but if there are users who have plenty of time to test today: could you please confirm or falsify the possibility of this Win7 compatibility solution?