As this issue seems to have been resolved with new drivers I'll mark this thread as solved now.
Wait what? They don't read their forums? They don't have a community manager that participates?
What the?
Ok, so I went and had a look at the Crash Test Edition and apparently I can't register for it since i haven't upgraded to the premium version of the game?
So... I spend 90 bucks on a game, for 6 months I can't play it for longer than 30-40 minutes so I give up on it, but to help troubleshoot it, I need to shell out another 60 bucks on it?
I'm flabbergasted!
:manmad:
I've just answered this post on CTE.
For now, CTE is mainly focused on netcode issues, but there's a better interaction with developpers on the CTE forum since the community is smaller than on retail game forums (and more involved/less whining), so 2 developpers directly answer to the community (unlike retail game forums, that are only read by community managers).
It's a good thing a developper now directly looks into this issue but it doesn't mean he will have time to solve it...especially because there are many memory leaks causes (AMD HD5/6XXX, Realtek sound chips, Windows NDU, ...)
In my case, this solution reduced leak occurences to about once a week in x64, instead of every 2 rounds: http://forums.hardwarezone.com.sg/windows-8-338/awareness-thread-windows-8-memory-leak-ndu-sys-4309046.html
That does not fix the problem, so please go back to the CTE thread and say "This doesn't always work"
BF4 IS THE ONLY GAME THAT DOES THIS
I have about 20 games installed
NO OTHER GAME MAKES MY SYSTEM RUN OUT OF MEMORY
IT IS A BF4 PROBLEM
This in nothing to do with the NDU "fix"... as stated by many people after many other people have also suggested it. Thanks for having a go at helping though.
I know this thread is really really long now and it's unlikely people are going to read all the way through it, but the FIRST post in the thread already summarises the things that have been tried for the myriad fix suggestions posted.
To anyone else coming to this thread, please at least take the time to read through the first post. Carbonic has actually put a lot of detail about the issue and it's history there.
My game seem to have begun be affected by this immediately after the first map is loaded and not only after mapchange. Anybody else can confirm this?
