[Possible solutions/INFO REQUEST] NP Pool Memoryleak [PC only] updated: Apr. 13

You have a lot of great information here, so I'm not sure if what I have to add is of any use, but it may save some folks some trouble if they decide they want to try something while working on this issue.

Here are my specs -

****************************************************

Summary
Operating System
Windows 8.1 Pro 64-bit
CPU
AMD FX-8120
Zambezi 32nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Motherboard
MSI 970A-G46 (MS-7693) (CPU 1)
Graphics
HL272HPB (1920x1080@60Hz)
3072MB ATI AMD Radeon HD 7900 Series (Sapphire/PCPartner)
Storage
465GB Western Digital WDC WD5000AAKS-00UU3A0 ATA Device (SATA)
55GB OCZ-AGILITY3 ATA Device (SSD)
111GB FM-25S3-120GBP3 ATA Device (SSD)
465GB Western Digital WD Elements 1042 USB Device (USB (SATA))
Optical Drives
ATAPI iHAS424 B ATA Device
Audio
AMD High Definition Audio Device

Computer type: Desktop
Installation Date: 3/17/2014 1:12:32 AM

****************************************************

I've had this problem since the game went live. During the (so called) two week BETA, I didn't have any sign of such an issue.  However, since the live release, I've had the issue usually after three or four rounds, and then every thing falls apart as per the other countless cases described in the thread.

I decided to try something and I dumped Windows 8.1 X64 completely, reinstalled the initial release of Windows 8 X64 along with the game, and tried that for a few days. During that period I also had the issue at various times, however not as often it seemed, nor as fast in going from playable to almost a full lockup.

My next experiment was to dump Windows 8 initial release, and I installed Windows 7 X64, and it happened just as frequently as with the installation of Windows 8 initial release, except it would happen suddenly more often than not.

I've now reinstalled Windows 8.1 X64 and I'm having the issue just the same as before I started all of this OS flip-flopping.

I can verify that all of the 'temporary fixes' in this thread, along with others in similar threads in various other forums, have not yielded any solution that is acceptable.

Basically, if anyone is thinking about doing something like I have, save yourself some time as it will not do anything to address the problem; it will happen (at least it did in my case) across all three OS's.

I also have another machine with the exact specs as this one, same hardware and same setup, except for the amount of RAM (8 GB on that one) and I run an Nvidia 660 SC graphics card.  On that machine, I can play the game for several hours at a time, and have yet to experience the problem at anywhere near the level I have had it happen on this machine with my 7000 series AMD card.

I 'have' had it happen, but I can most likely use the fingers on one hand to count the times it has happened.

Therefore, I pretty much feel it is a problem somewhere in the BF4 and AMD hadware interactions during the game. Drive problem or whatever, I don't have the technical knowlege to determine the who, what, where and how aspects, however, I do (as I said already) feel it is an AMD and BF4 related issue.

The only solution I've found to work for me, is after every two or three games is to exit the game, and do a full reboot of my system whether it's acting up at the time or not.  

Doing that, I seldom have the problem occur, unless the game play and screen action increases dramatically from one round to another - in short, the more 'busy' the game gets, the more likely I'll see the problem occur.

You're doing a great job here keeping this thread active and the problem in the open. Keep it up and maybe 'they' ... whom ever 'they' are .... will find and publish a solution and / or fix for the problem.