Has it truly ever been fixed? It was detailed here a lot. And while it happens in only a few games (GTAV, The Division, and a few others I can't recall), when I want to play them I'm forced to use my Win8.1 boot instead of Win10. If I still try to use Win10 instead, either the game will crash in some unspecified way, or Windows will minimize the game and ask me to close it to free up memory. And it happens with and without a pagefile, just like in the other thread. My problems are exactly the same as in the thread I linked, and it's been like this for as long as I can remember. It has never been different, since I've tried literally most of the drivers, including that old one which was supposed to fix this exact problem. GTA V I seem to only trigger it if I use DSR with SLI under Win10. The Division...it happens regardless of what's going on. In general, I can play on the lowest possible settings, and the problem still will occur for each game that is affected by this (which is only a handful). BF1 (alpha, NDA has lifted) also has a memory leak problem but since it's not final I can't say for sure if it's related to this (again which works fine under 8.1 and not 10). The following is from The Division a few months ago when I tried to report it for the umpteenth time to Nvidia: Win 8.1: Win10: GTA V on the other hand doesn't exactly hit the limit immediately like The Division, but it sits well above the 3.5GB partition of VRAM, eventually crashing when it hits 4GB. The problem isn't that it goes over that partition--it's that only under Windows 10 it remains well above it and stays there, causing problems, constantly growing. If I use a massive pagefile (such as 16GB), it just fills up immediately and it's like it doesn't even exist because VRAM usage shoots straight up. If I turn it off entirely, the games will usually crash within a few minutes. Otherwise, I only leave 2GB for the pagefile. Again, this applies to Win10. Win8.1 won't crash at all. I did install a test copy of Win10 on another drive to try it out there. I only installed the Nvidia driver, a few Intel drivers provided by Gigabyte for my motherboard, and let Windows 10 update itself. So I installed no software that could've conflicted with it there, yet it still occurs on that fresh test install. Am I alone in this? I'm just nearing the point that I'll give up with SLI since I can't get Nvidia to respond to me after many months of providing different tests, and this is becoming bothersome. Was there ever some fix I never heard of (tried that old driver which was to fix this)? Or is it likely my assumption that it's a, perhaps rare, driver problem that I can't do a thing about? Sorry for the long post. Just getting fed up is all and hoping to hear something.