Windows successfully diagnosed a low virtual memory condition.
I'm at my wit's end. This bug has bothered me since August.
A lot of programs, most recently Forza Horizon 4 crashes every couple of hours because apparently my virtual memory has ran out when it really hasn't.
I have tried with both automatic and manual pagefile (set to 32GB even!) and just an hour ago it crashed with the following information:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: ForzaHorizon4.exe (11552) consumed 10057064448 bytes, Spotify.exe (14260) consumed 303996928 bytes, and thunderbird.exe (13148) consumed 245481472 bytes.
I have only 8GB of DDR4 at the moment, but I ran some tests with 16GB and got the same crashes.
Any suggestions? 1809 upgraded from 1803.
Posted Oct 9, 2018, 7:36 PM UTC
Kinda looks like the stand-by memory bug.
Most reports say that the stand-by memory bug was fixed / alleviated in latest 1803 cumulative update but there are also reports stating otherwise.
It is something that has plagued all editions after 1607 with Microsoft not even acknoleging it and instead blame it on users or drivers or software or karma - anything but their fault. Only to couple weeks ago discover they have fucked up an advanced memory management parameter..
Might want to try the workarounds for the stand-by memory bug:
EDIT: Since this appears to still be needed, I have updated the script to work faster and more reliable. Way faster.
Re-download, run once to remove previous version, run a second time to get the updated one.
I think it helped, at least for now. I had a foolproof way of crashing Forza, and it doesn't do it anymore.
Thank you!
[removed]
It actually might be that, because when I reboot my computer that crash doesn't happen for several hours, sometimes even a whole day. I will look into that, thanks.
e: Downloaded and installed your .bat and will run some Forza tests now
Unfortunately compiling doesn't work for some reason: https://i.imgur.com/1JlK0Mb.png
u/9777, what about now: https://pastebin.com/Kj36ug5h
guess I'll have to fallback to older management if it's not there
Thank you, thank you, thank you for this. This seems to have fixed a problem I was having while running either Fallout 4 or Skyrim SE in Windows 10. I was able to go the entire hour I tested this fix without the entire system completely freezing up and Windows rebooting itself, only to have it completely freeze up again maybe 10 minutes, or some random interval, after restarting a game. I know Bethesda doesn't ship bug free code, but I've never had a problem with one of their games like this. I'm on Build 1803, and for me, it seemed to get worse with that update, even though the same thing has happened in previous builds, but it was a rare thing. I think there's only been one time I've been on 1803 where it completely stopped until I had to reboot Windows and then it came back again. And I tried all kinds of troubleshooting, from closing other programs that were running, disabling things in device manager that weren't necessary to running a game, uninstalling GPU drivers with DDU to update to newer ones, turning down the graphics settings, running in borderless windowed mode, and none of that worked. Now I might even throw caution to the wind and turn up the graphics settings again, or even try running a game full screen.
Glad it works for you! Not so glad it's not fixed by microsoft :(
You should definitely re-download it run it again (twice, once to remove previous version, one to update), because I have just updated it with performance in mind (compiling the c# snippet instead of on-the-fly slow powershell)
u/rpanknin - major script update, it is now blazing fast without depending on wmi, so it might help even more!
Another crash. Played Forza for an hour, alt-tabbed to check a couple of things out in Chrome, and what do you know:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: ForzaHorizon4.exe (13072) consumed 10407514112 bytes, chrome.exe (11108) consumed 352010240 bytes, and avguard.exe (3440) consumed 167776256 bytes.
That's almost 10GB, and you have only 8GB RAM. 20% starvation - no wonder it crashes. The standby memory bug was all about fixing stutters, not crashes. I don't think there is a magic solution for that (but the script should help squeeze a bit more time).
In my experience virtual memory only ever works for static apps, and has always been problematic for games that need to eat real RAM.
I'd say the issue lies with the game and your configuration of it / drivers / windows / bios. Definitely need to get 16GB and see if it leaks past that!
Like I said in OP, I had this problem a couple of months ago even with 16GB of RAM, where Chrome bluescreened my computer even when I had 50% of RAM free.
Come to think of it, maybe the culprit is Chrome? I posted about this problem here but thought they fixed it, because it hadn't happened for some weeks. Forza also only crashes when Chrome is running.
I need to run some more tests without Chrome in the background.
u/9777 - major script update, it is now blazing fast without depending on wmi, so it might help even more!