Windows 8.1 x64 - Low memory while playing full screen games

Anonymous
2013-12-01T18:38:14+00:00

Info: This bug was fixed on August 12th 2014 with the release of the month's Patch Tuesday. Make sure to install every update available for your system, if you're having the problem described on this thread.


Hello, I've been facing a "tough" problem with my computer running Windows 8.1 x64. I did not upgrade from Windows 8, I did a clean install and for the past month, everytime I play some of the new 2013 games (Assassin's Creed Black Flag, Battlefield 4, CoD:Ghosts etc.), I'm constantly getting a "low memory" warning from time to time. 

So, giving that my laptop is capable of running these games (Asus N56VZ - Intel Core i7, Intel HD 4000 + Nvidia GT650 M, 6GB DDR3, 750GB 7200rpm, Full-HD 15,6" screen), I began searching for an answer. Here's what I've concluded:

When the game (eg: Battlefield 4) opens, the memory consumption begins to rise, and rise, and rise, non stop, until the system doesn't have more memory available and triggers the low memory warning. However, in the exact moment that I "alt+tab" out of game OR the memory warning does it for me, all of the occupied memory is emptied instantly, like magic!

I was able to "understand" this using Process Explorer by MS (sysinternals), heres a screenshot that shows the "climbing" and the sudden drops:

http://prntscr.com/2809xc

I cant really discover where all this memory is being allocated/used, and I have no idea on whats causing this. I also don't know if this is Windows-related, device-related or driver-related.

Is anyone facing this as well? 

[UPDATE DECEMBER 9th] This issue is triggered when the resolution in which the games are being played differs from the resolution configured on Windows.

If you are playing a game, say, in 1366x768, you need to change the system resolution to the same 1366x768 BEFORE opening the game. That will stop the excessive memory consumption and you'll be able to play the game fine.

My system is in Portuguese, but I think it's easy to get it:

This also concludes that the issue is Windows-related and not driver related, so we'll have to wait for Microsoft to patch it. Meanwhile, remember to change your resolution when you're going to play.

[UPDATE APRIL 26th 2014]

According to some Intel folks at communities.intel.com (http://is.gd/71Vha2), Microsoft has confirmed the issue with Windows 8.1 in an internal email. It resides - as it was explained - on the DWM (Desktop Window Manager) which triggers a memory leak when running fullscreen games with a resolution different than the desktop resolution.

The memory leak fills the system memory and page file with junk until there's no more memory available.

We assume Microsoft is already working on a fix for this, altough we never heard anything "official" from them regarding the issue. 

[UPDATE AUGUST 14th 2014]

The problem has been finally fixed by Microsoft with the release of the August updates on Aug. 12th.

Make sure to install every single update available - including the optional ones - and you'll no longer receive low-memory warnings when running fullscreen games/apps with different resolution/refresh rate.

Also make sure you're using the latest drivers available for your Intel and/or Nvidia GPU (it might be important).

Windows for home | Previous Windows versions | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-08-13T05:04:19+00:00

I might be a bit cynical but I looked through all the support KB's from the updates today and couldn't find anything that related to fixing this issue (unless I'm missing something)...

Yesterday i have made the update and i found via the link also no description, but...

Yah!, after nearly 10 months, microsoft have now solved this bug.

With the latest patches (Patch Day 12.08.2014, also install the optional Updates),

all different resolutions and framerates works well.

Was this answer helpful?

7 people found this answer helpful.
0 comments No comments

317 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-02-10T19:48:17+00:00

    I confirm everything stated in this thread. Memory leaks are evident and concern not only different-than-desktop resolution but also different-than-desktop refresh rate. 

    E.g. I first noticed that issue with XBMC. When I launch it full screen - it launches in 1920x1080@60hz, but as soon as I play video it switches to 29 or 24 hz according to video framerate (tv to video sync) and it all begins.

    I have 16gb RAM and system managed swap file usually sits around 1GB. In a couple of seconds I see that it grows up to 30-40-48gb (reserved, not filled, it stays empty actually) and then abruptly drops to 2-3gb and starts growing again.

    As soon as I stop the playback and XBMC switches back to 1080p@60hz everything becomes normal again.

    My system is Windows 8.1 Pro, Intel Core i7 4770k (hd graphics 4600), Asus Z87 Plus, Nvidia Geforce Gtx780ti. It is set in bios so that Intel HDMI out is treated as additional monitor not as that fancy Virtu thingy or whatever it is called.

    Also this issue occurs if only I use my Intel HDMI out. If however I connect TV to Nvidia HDMI out (without even uninstalling intel drivers) there are no such issues. Yet I can't comfortably use Nvidia HDMI due to windows monitor enumeration scheme being retarded, but that's another story.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-02-10T05:23:36+00:00

    I know, this is not the best solution to the problem. For me is anyway better than running the games at same resolution of the desktop or in windowed mode...

    For the stuttering you can try working on vertical synch and maximum number of fps... try to synch them with desktop 60 or 30 fps, it could help.

    You can even try downgrading nvidia drivers too but this could be last resort trial...

    It is surely disappointing such problem mainly for two reasons:

    1. it should have been easily detected during tests (if any);
    2. it is present and people are complaining about it since months!

    Hope this thread, having finally identified where is it shall help us receiving an official fix for it.

    Bye,

    S.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more