As this issue seems to have been resolved with new drivers I'll mark this thread as solved now.
Seems like SOMEONE has finally GOT it. Battlelog forums page says "WE ARE WORKING ON A FIX FOR AN ISSUE ON PC THAT CAUSES THE GAME TO FREEZE, RESULTING IN A SOUND LOOP. WE WILL SHARE MORE INFORMATION ONCE AVAILABLE." 😉
@fetsnage wrote:
Seems like SOMEONE has finally GOT it. Battlelog forums page says "WE ARE WORKING ON A FIX FOR AN ISSUE ON PC THAT CAUSES THE GAME TO FREEZE, RESULTING IN A SOUND LOOP. WE WILL SHARE MORE INFORMATION ONCE AVAILABLE." 😉
Well, not really as it has nothing to do with this thread.
in my oppinion it is the same issue, people just have different outcomes. That soundloop (caused because game crashed due to memory getting filled and last audio gets looping) actually comes with some kind of error, i've never seen it, but pressing ENTER closes bf4. So if they fix THIS, whats most likely caused by the leak then we should be ok 🙂=
Logical? no ?
@fetsnage wrote:
in my oppinion it is the same issue, people just have different outcomes. That soundloop (caused because game crashed due to memory getting filled and last audio gets looping) actually comes with some kind of error, i've never seen it, but pressing ENTER closes bf4. So if they fix THIS, whats most likely caused by the leak then we should be ok 🙂=
Logical? no ?
Actually not.
If you look at your memory when soundloop crash occours it's not using more memory. Not in the normal memory and not in the non paged pool which this thread is about.
Also, the non paged pool area fills up your memory in a way which makes it not able to release it which means you have to restart your computer. All you need to do with the soundloop crash is press ctrl+alt+delete and close BF4 which makes you able to play again.
The Soundloop crash can happen right after you start the game, the NPP memoryleak mainly happens after mapchange.
The NNP memoryleak also has been there since beta and this new soundloop crash has only been there since Feb. 13.
The NNP memoryleak has specific hardware on which it doesn't work, the soundloop crash has not.
Lastly, the soundloop crash only affects the maps: Dawnbreaker, Parcel Storm, Operation Locker and Metro - the bug in this thread affects all maps.
So, to sum up:
No, it's not logical that it's the same, it's illogical.
The soundloop crash and the NPP memory leak are in almost any way totally different as bugs go. The only thing they really have in common is that they both affect BF4
Got both bugs. Soundloopcrash on Metro (cant play more than 20seconds) and NPPMemoryLeak
I have 8g of memory and when bf4 game for a while begins to pound the memory of the PC. I know this because the doll is slow and lowers the fps of the game affecting performance and becoming unbearable to play. then in device manager before the game wore on average 3GB is already using 7.3 Giga of memory. Fix this DICE.
Windows 8.1
Asus M4A79T Deluxe
8 GB Ram
ATI Radeon HD 6950 2GB Saphire
HD Samsung 250GB SSD
Really annoying... New computer.. And yesterday AND some days before tonight, I did not have this problem. Today, all my memory gets eaten... And need to shut down the computer to set it free.
