Borderlands 2

Borderlands 2

View Stats:
GURN Jun 17, 2019 @ 1:39pm
Ran out of Video Memory Crash
I can't play more then 5 min and killing an enemy and game crashes with this error. I know I'm really not running out of VRAM so what is going on and how do I fix this?

I have turned physX to Med. Not helping.

Windows 10 Home 64bit
8700K
RTX 2080
PSU HX1000i
32GB RAM 3200
< >
Showing 1-15 of 29 comments
Laexas Jun 18, 2019 @ 11:42am 
same here

rtx 2070
ryzen 7 200 x
16gb 3200
w10 home
Scorpion Jun 20, 2019 @ 6:15am 
Same here and it only started happening for me after downloading the new DLC.

i9 9900K
2080ti
32 GB Corsair RAM
W10
SMACK Jun 20, 2019 @ 7:09pm 
I really hope they are looking into this issue, and the virtual memory has also been acting up saying I need to free up space for certain files. I ALREADY DID THAT. But nope the game just doesn't seem to like the latest drivers probably, that's just my thought.
Jedil Jun 20, 2019 @ 7:28pm 
I've been having the same "ran out of virtual memory" crash. I had a friend who guide me through increasing the virtual memory allowed to each drive, didn't work. Just reinstalled it on a new 4TB drive and still doesn't work, so needing more disk space cant be the issue. I've done everything that shows up when you search it, setting physX to low graphics on low etc..

Drivers aren't up-to-date but that's because it breaks a couple of my games

gtx 1070
i7-7700K
16GB RAM
W10 64bit
Smaug's Arrow. Jun 20, 2019 @ 8:15pm 
If I remember correctly that PhysX has always been an issue for this game.
This is ironic as Nvidia was a major contributor to BL. If I remember correctly it had something to do with a memory leak? Some may have completely disabled physX in the game files or by attempting to uninstall physX with mixed results.

I did some research into this and did find some clues that could point to a problem unrelated to the memory leak.

I found that people who upgraded their Win 7 32bit to the Win 10 64bit had an issue where their system is somehow still acting like 32bit leading to this issue.

Some people resolved the issue by increasing their VM limit to 1.5 times their ram instead of allowing windows control it.

Some by having their Windows, game and pagefile all on different drives.

Some may have resolved the issue by completely turning off the VM pagefile.

Some may have resolved the issue by re-installing the game as admin or re-installing the c+,vs dx files in the bl redist folder (also as admin)

Sry i cant help


Edit: Someone suggested turning your settings (resolution and graphics, everything) to default, running the game. And if its resolved the exit the game and change your setting to normal.


Last edited by Smaug's Arrow.; Jun 20, 2019 @ 8:24pm
GURN Jun 20, 2019 @ 8:35pm 
I have adjusted all sorts of settings. Even as far as running at 720p with all low settings and PhysX turned low...Still happens.

If any other those options are guaranteed solutions I would like to know which and detailed description on how to achieve the fix, please.

Originally posted by Atlas Shruggs:
If I remember correctly that PhysX has always been an issue for this game.
This is ironic as Nvidia was a major contributor to BL. If I remember correctly it had something to do with a memory leak? Some may have completely disabled physX in the game files or by attempting to uninstall physX with mixed results.

I did some research into this and did find some clues that could point to a problem unrelated to the memory leak.

I found that people who upgraded their Win 7 32bit to the Win 10 64bit had an issue where their system is somehow still acting like 32bit leading to this issue.

Some people resolved the issue by increasing their VM limit to 1.5 times their ram instead of allowing windows control it.

Some by having their Windows, game and pagefile all on different drives.

Some may have resolved the issue by completely turning off the VM pagefile.

Some may have resolved the issue by re-installing the game as admin or re-installing the c+,vs dx files in the bl redist folder (also as admin)

Sry i cant help


Edit: Someone suggested turning your settings (resolution and graphics, everything) to default, running the game. And if its resolved the exit the game and change your setting to normal.
Shakes Jun 20, 2019 @ 9:29pm 
It's not PhysX. Running the game through Proton, PhysX is completely disabled for me (not that I care) and yet I still get OoM crashes with the UHD pack installed.

The reality here is that BL2 is limited to 32-bit address space and with DirectX 9, any VRAM that is used is mirrored in system RAM. So with all of the extra eye-candy, you're going to be running up against that ~4 GB hard limit. A memory leak will just exacerbate the issue, but there's nothing you can do about it besides uninstalling the UHD pack since fixing it would require GearBox to ship an update and I'm pretty sure they're done with this game.
Last edited by Shakes; Jun 20, 2019 @ 9:29pm
winterplantkill Jun 20, 2019 @ 11:49pm 
Originally posted by Shakes:
It's not PhysX. Running the game through Proton, PhysX is completely disabled for me (not that I care) and yet I still get OoM crashes with the UHD pack installed.

The reality here is that BL2 is limited to 32-bit address space and with DirectX 9, any VRAM that is used is mirrored in system RAM. So with all of the extra eye-candy, you're going to be running up against that ~4 GB hard limit. A memory leak will just exacerbate the issue, but there's nothing you can do about it besides uninstalling the UHD pack since fixing it would require GearBox to ship an update and I'm pretty sure they're done with this game.
You're sure they are done with this game that they have released content for earlier this week?
Draekus Jun 21, 2019 @ 3:54am 
Originally posted by GURN:
I can't play more then 5 min and killing an enemy and game crashes with this error. I know I'm really not running out of VRAM so what is going on and how do I fix this?

I have turned physX to Med. Not helping.

Windows 10 Home 64bit
8700K
RTX 2080
PSU HX1000i
32GB RAM 3200

is your CPU and / or GPU overclocked ?

that's been known to cause some issues.
Shakes Jun 21, 2019 @ 4:15am 
Originally posted by winterplantkill:
You're sure they are done with this game that they have released content for earlier this week?
"Released" and "finished working on" are two different things. They had the new DLC finished for many months at minimum, but only recently did they actually ship it due to timing the release to land with E3 when hype levels for BL3 were sure to blow up. The game itself hadn't received updates for years before the UHD pack (which is probably just ported assets from BL3 anyways) was released, and I don't see development shifting back to it when BL3's release is right around the corner. Unless there's a critical security issue that they need to address, this game is done with updates.
Last edited by Shakes; Jun 21, 2019 @ 4:16am
GURN Jun 21, 2019 @ 6:34am 
Originally posted by Draekus:
Originally posted by GURN:
I can't play more then 5 min and killing an enemy and game crashes with this error. I know I'm really not running out of VRAM so what is going on and how do I fix this?

I have turned physX to Med. Not helping.

Windows 10 Home 64bit
8700K
RTX 2080
PSU HX1000i
32GB RAM 3200

is your CPU and / or GPU overclocked ?

that's been known to cause some issues.

Yeah they are overclocked. But, like others, I didn't start having these issues until after I downloaded the new DLCs. Never had issues before and I was overclocked.
GURN Jun 21, 2019 @ 6:36am 
Originally posted by Shakes:
It's not PhysX. Running the game through Proton, PhysX is completely disabled for me (not that I care) and yet I still get OoM crashes with the UHD pack installed.

The reality here is that BL2 is limited to 32-bit address space and with DirectX 9, any VRAM that is used is mirrored in system RAM. So with all of the extra eye-candy, you're going to be running up against that ~4 GB hard limit. A memory leak will just exacerbate the issue, but there's nothing you can do about it besides uninstalling the UHD pack since fixing it would require GearBox to ship an update and I'm pretty sure they're done with this game.

Uninstalling the UHD Pack doesn't fix it. I tried that and crash without fail everytime I even look at the Warrior.
Shakes Jun 21, 2019 @ 8:01am 
Originally posted by GURN:
Originally posted by Shakes:
It's not PhysX. Running the game through Proton, PhysX is completely disabled for me (not that I care) and yet I still get OoM crashes with the UHD pack installed.

The reality here is that BL2 is limited to 32-bit address space and with DirectX 9, any VRAM that is used is mirrored in system RAM. So with all of the extra eye-candy, you're going to be running up against that ~4 GB hard limit. A memory leak will just exacerbate the issue, but there's nothing you can do about it besides uninstalling the UHD pack since fixing it would require GearBox to ship an update and I'm pretty sure they're done with this game.

Uninstalling the UHD Pack doesn't fix it. I tried that and crash without fail everytime I even look at the Warrior.
Simply uninstalling won't remove it completely. You need to verify your game files after disabling the UHD pack to get the original files back since most of the UHD files are overwrites instead of additions.
trukr Jun 21, 2019 @ 9:34am 
I had this issue, I deleted WillowEngine.ini and then started the game.
I had to set my options after that, but have not had the issue since then.

When you run the game after deleting WillowEngine.ini, it will put the default WillowEngine.ini in, this is why you have to set your options again.

You can find it in this path.
Documents\my games\borderlands 2\willowgame\Config

You could also just delete the entire contents of that folder, all would be replaced when you launch the game.
GURN Jun 21, 2019 @ 2:08pm 
Originally posted by trukr:
I had this issue, I deleted WillowEngine.ini and then started the game.
I had to set my options after that, but have not had the issue since then.

When you run the game after deleting WillowEngine.ini, it will put the default WillowEngine.ini in, this is why you have to set your options again.

You can find it in this path.
Documents\my games\borderlands 2\willowgame\Config

You could also just delete the entire contents of that folder, all would be replaced when you launch the game.

Nope. Didn't fix it.
< >
Showing 1-15 of 29 comments
Per page: 1530 50

Date Posted: Jun 17, 2019 @ 1:39pm
Posts: 29