Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having intermittent issues with my gaming computer. Sometimes, while playing Battlefield 3 (only 2 times the problem has occured), my memory usage goes to 100% of my 16GB machine. I close down BF3 (which is unplayable at this point), open up task manager, and no process uses more than 25MB of memory. Process Explorer shows much the same thing.

The problem disappears aftera reboot.

Any ideas what can be going on here?

Task manager Process explorer Poolmon x86 Poolmon x64

share|improve this question

You may have a bad driver which leaks pool memory. Start the TasmkMgr and look at the non paged pool usage value. If this is several GB, you need to do the following:

Install the Windows Driver Kit, run poolmon.exe and look which pooltag causes the high memory usage. If you found the tag, open the cmd prompt and run

findstr /s <Pooltag> *.sys

and look which driver is shown. If it happens while playing games, update the GPU driver. The ATI 12.10 driver is known to cause it. Install the 13.1 WHQL driver to fix it.

share|improve this answer
I do have the 12.10 ATI driver installed. Upgrading now, hope the problem disappears. – Vegard Larsen Jan 14 '13 at 17:48
12.11 beta drivers crash whenever BF3 is started, unfortunately, so rolling back. – Vegard Larsen Jan 16 '13 at 17:31
run poolmon and look if the AMD driver is really the cause. – magicandre1981 Jan 16 '13 at 19:10
poolmon output added. Seems like MINI is the culprit. Potential matches: arc.sys, atikmdag.sys, crashdmp.sys, diskdump.sys. I am assuming atikmdag.sys is the issue, so I am trying another upgrade of the ATI driver. – Vegard Larsen Jan 19 '13 at 9:18
ok, this can be the AMD driver. AMD releaed the 13.1 WHQL driver. Try this one. – magicandre1981 Jan 19 '13 at 11:33
up vote 0 down vote accepted

This was an AMD video driver issue. The problem magically disappeared when a newer driver was installed.

share|improve this answer
So instead of accepting the answer from the guy who helped you resolve the issue, you accepted your own poor un-detailed answer? Classy. – b1nary.atr0phy Nov 20 '15 at 4:21

You must log in to answer this question.

protected by magicandre1981 Sep 3 '15 at 15:52

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .