Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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
add comment

2 Answers

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
show 6 more comments
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
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.