This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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:
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).
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.
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.
I found here. But of course it's your business, what you are doin'.
Hi
Thanks for your contribution. I do however agree with Ray. Err on the side of caution with unofficial drivers. Particularly when we have proven a simple work-around to the reported problem.
I spent an hour or so searching the net both yesterday and today. There was NO OFFICIAL discussion about driver 15.33.12.3383 (10.18.10.3383). A search of Google, Bing, Excite, Yahoo search engine results so far in links to private hosting websites and personal cloud storage.
Nor was there any release announcement for version '3383' within the Intel Communities where Intel staff are still actively working through issues with v3345. Have a look for yourselves:
Intel HD 4000 ver 3345 discussion | https://communities.intel.com/thread/46588?start=0&tstart=0
Branched thread | https://communities.intel.com/thread/47028
....different reported issues but proves Intel staff are still in progress with the earlier release.
Intel Downloads search:
In any case this 'version 3383' could carry any nasty old registry hack. Do we entrust it with Administrator access on our PCs?
My advice: apply extreme caution.
There's NO LEGITIMATE MOTIVATION for this unofficial driver. The Intel HD platform is still actively developed and releases are free of charge - why be impatient and void any [warranty] support from Microsoft, Intel and your PC manufacturer?
Yes - it is possible v3383 is leaked from Intel's development/in-testing phase. My thoughts are: it's all too suss. If it were intended for distribution and implied installation onto NEW PC's then I have no doubt Intel would have fixed something like a 'wrong date' not to mention pressure from Microsoft plus a miriad of hardware manufacturers.
I know you are only trying to be helpful. :-) I'm also genuinely happy for you that the unofficial driver has fixed the issue.
Since there is a very easy workaround for this particular problem, even as a seasoned power user, I'll personally be sticking with that since I know what CAN go wrong.
Here's the _Official_ Intel HD Graphics 4000 Download link
I strongly suggest clicking on the above link every few days until the next official release appears!
As a techo, I don't want to be hearing stories of some poor Granny losing all her digital photos or throwing another good notebook into landfill simply because her Grandchild took some impatient steps a few weeks before an official fix......
I have now fixed the links in my previous post. Apologies for any inconvenience.
All-
While I understand about using drivers that are not sanctioned I went ahead and did it anyway.
I can report with 100% confidence that the 3383 driver in no way fixes the issue that we are discussing here. 3383 acts the same way that 3345 does. If i bring up a full screen WMC screen (even just sitting at the main menu works) and then I power off the monitor for 5-7 minutes I see the same sawtooth issue in System Commits that we are all familiar with.
I removed the driver completely and installed 3345 once again.
As some people have mentioned this really feels like a Microsoft issue, not an Intel, Nvidia, AMD issue.
i have figured out the cause.
Its DirectX 11.2 that comes with the windows 8.1
thats why it only happened to windows 8.1 user. DirectX 11.2 is exclusively Windows 8.1.
the directx 11.2 has a feature called "frame buffer scaling" which i think causes conflicts with the directx11.1 or 11.0 instructions that comes from todays games. because it seems that th WiIN 8.1 FORCE all directx 11.x application to run under 11.2 .
and the issue triggers when we try to view 3D applications in fullscreen with different resolution than the monitors native/max resolution.
so the only way to avoid that is to view fullscreen with resolution settings match your monitor max resolution. OR to play games in windowed mode.
some games can be set to "windowed" mode and then we can stretch it to fullscreen windowed by Alt+Enter. these also worked.
but not all games can be windowed and stretch fullscreen.
so you are right, this isnt Intel,AMD or NVidia issues. this is Windows 8.1 issue due to their new DirectX11.2.
but i hope AMD or NVidia could override it in their new drivers. that is to ignore Directx 11.2 and use the targeted directx used by the games instead.
because to my knowledge, there hasnt been any games that natively RUNS DirectX 11.2 to this day.
For Battlefield 4 players, if you need to increase performance by lowering resolution in Windows 8.1, the only solution to avoid the memory leak issue is as follows:
go to option, go to video tab, now set the resolution settings there to match your native/max monitor resolution.
BUT, lower the "RESOLUTION SCALE"(near the bottom of the video options) option LOWER THAN 100% .
100% means the GPU render the frame in your screen resolution size that you set in the resolution setting.
LOWER means the GPU render lower resolution and then upscaling it to your native resolution.
this has the same effect to lowering resolution, but without the MEMORY LEAK issue in windows 8.1 .
i hope this helps.
