Hello Kevin,
firstly thank you for answering more than once! That’s at least more than the guys at Microsoft did. Other than that I’m not trying to offend you or to be too harsh, but I think you’re wrong and I think you didn’t really understand.
The issue is caused by the Intel driver on a variety of systems of different manufacturers. Why, you ask? Well simply downgrading the driver to a version like 2875 or 2884 completely solves the issue for users of the HD4000. Unfortunately Intel keeps pushing updates that seem to be defective. The last one less than a week ago. I don’t think we should lay the blame on Nvidia. Also people who have a HD4400 or HD4600 aren’t that lucky because they simply can’t downgrade to a working version of the driver.
Anyways… Since you obviously did not read the thread on the Microsoft forums which Keleg posted I’ll happily summarize it for you:
The problem occurs:
- only on Windows 8.1
- only when playing on fullscreen or using a fullscreen application like XBMC
- only when the resolution and/or refresh rate of the fullscreen application does not match the resolution and/or refresh rate of windows
- mostly for Optimus users (I’m not sure if it also occurs for users of an Intel HD only)
- only for users of a new Intel graphics driver (the Nvidia driver doesn’t matter, trust me I’ve tried it), unfortunately this doesn’t give us much of a choice other than setting the Windows updates to “manual” and sort out all of the intel graphics drivers) - 2875/2884 driver versions seem to work, I can confirm the 2875 myself (HD4000).
What happens?
- The virtual memory / pagefile.sys gets bloated, and with bloated I mean about 25 gigabytes in my case (I’m pretty sure my SSD really LOVES all the write-cycles!)
- Soon after that the message telling you that you ran out of memory will pop up
- Again: for more details check out the thread on the Microsoft forums, it’s actually quite informative
The workarounds people came up with are also on the Microsoft thread.
So please do us a favor and read the thread on the Microsoft forum and stop laying the blame on game developers, Nvidia or Asus instead of redirecting the issue to a Intel division, which could actually try to reproduce the issue and determine that we aren’t actually telling you fairy tales. (And no, I don’t have an Asus!)
Thank you very much!