Borderlands 2

Borderlands 2

Statistieken weergeven:
Borderlands 2 crashing SOLUTION
All right:
1. Reinstall the game(for sure).
2. What helped for me: in folder with exe select compability with Win7. After that launch exe as administrator. All worked.
3. Then you can select off compability and just launch the game as usuall through steam.

I hope that'll for. Cheers.
< >
31-37 van 37 reacties weergegeven
Origineel geplaatst door Wiesshund:
Origineel geplaatst door Arid Drifter:
oh wow i didnt get the notification for your reply... now that you did that... does b2 run good on high graphics settings? do you see corrosive goo floating from barrels on the ground and when you walk through it it moves? does blood from enemies splooge on the ground? thats how you know its all on high

It does for me, and without all the stupid nonsense about disabling UAC or running in compat modes etc etc etc.

If you feel you need to tweak anything 1st backup willowgame.ini and engine.ini

WIllowEngine.ini tweaks


[MemoryBudgets]
AnimationMB=5000
AudioMB=5000
CodeMB=5000
LevelObjectsMB=5000
TerrainMB=5000
GameDataMB=5000
MaterialMB=5000
ParticleMB=5000
PhysicsMB=5000
ScaleformMB=5000
ShadersMB=5000
SkelMeshMB=5000
StaticMeshMB=5000
TextureMB=1000

[Engine.Engine]
MaxParticleResize=128
PhysXGpuHeapSize=512
PhysXMeshCacheSize=256


These reduce lag and help with FPS
You may find you dont need any help FPS
I still recommend the [Engine.Engine] section
It helps keep physX from overflowing and causing a crash
And you need PhysX running as some of the effects you ask about only happen with PhysX running.


WillowGame.ini tweaks
These are just for dead body decay, most people dont need but if you are doing something that generates a lot of corpses, they lay around for 10 minutes, normally no an issue, but if you are doing something that generates an abnormal amount of bodies

SecondsBeforeConsideringRagdollRemoval=5.0
SecondsBeforeVisibleRagdollRemoval=15.0
SecondsBetweenRagdollRemovalAttempts=1.0
SecondsBeforePhysicsShutsDown=10.0

That will greatly speed up them vanishing
You can adjust those numbers to your liking
The above is pretty fast, higher numbers = longer time before corpse decay.
Some people find it beneficial to have them vanish fast and not have corpses laying on top of loot etc.

Again, backup INI files before touching
and try playing with no tweaks except the [Engine.Engine] tweaks above
That one i recommend for everyone.

All the above tweaks, search the ini file
you will find the parts above, then you can paste in new values.

Run your PhysX set to medium
You can try high, i do not have any Nvidia hardware, so i have not tried high, and it seemed perfectly fine on medium.
so after uninstalling ultra texture pack or whatever the game worked flawlessly.... all the barrels had the goo floating around for a few days of playing no crashes at all... today the game just shut off and quit twice in the row within minutes of starting... idk i have 4060 rtx and i turned on turbo performance... just weird... no other game ever crashed just borderlands 2

i should also mention im on acer nitro 17 laptop rtx 4060 windows 11... yeah i tried getting win7 on a separate partition but that's impossible
Laatst bewerkt door Arid Drifter; 23 feb 2024 om 14:53
Im just gonna 'acquire' the version they released when they announced borderlands 3 and see if that crashes. For me current ver crashes with the pre rendered cutscenes.
Laatst bewerkt door Doom Sayer; 23 feb 2024 om 14:10
Origineel geplaatst door Arid Drifter:
so after uninstalling ultra texture pack or whatever the game worked flawlessly.... all the barrels had the goo floating around for a few days of playing no crashes at all... today the game just shut off and quit twice in the row within minutes of starting... idk i have 4060 rtx and i turned on turbo performance... just weird... no other game ever crashed just borderlands 2

i should also mention im on acer nitro 17 laptop rtx 4060 windows 11... yeah i tried getting win7 on a separate partition but that's impossible

1) Just double check that the game is in fact using DX11 and not 12
12 is just a spaz fest of i think i will crash here.
I do wish the devs would revisit BL in an act of love, and rewrite the DX12 implementation
and then compile the exe for 64bit


2) try a game files validation

3) If validation does not help, temporarily rename your documents\my games borderlands goty folder
What this will do is temporarily make the game start with blank configs and no previous save files, so you can check if one is possibly corrupt etc.

If that seems to work, then you can try to see which the problem was, configs or save game
by moving the save game back and testing if it still works.
Origineel geplaatst door Doom Sayer:
Im just gonna 'acquire' the version they released when they announced borderlands 3 and see if that crashes. For me current ver crashes with the pre rendered cutscenes.

Should not crash, we got 10 machines here (literally) ranging from potato machines that don't even have GPU's to actual decent gaming desktops, and it runs on all of them.

Not what you want to hear but, it may be your OS install.
And yea, i have had people IRL insist, my PC is fine this game sucks it's broke, not touching my PC.
So i took an HDD of mine, plugged it in, did a clean windows and drivers install.
Installed current release of VC++ runtimes, then steam, then BL2 (minus HD textures DLC)
and it ran and ran and ran.

I said Welp, now you know what you need to do.

This is one reason why any game that recommends tweaking any aspect of the OS
or anything that does not pertain to only that game itself only when it is running, i say gtfo.
Just comes back to bit you later when if affects something else.
Origineel geplaatst door Wiesshund:
Origineel geplaatst door Arid Drifter:
so after uninstalling ultra texture pack or whatever the game worked flawlessly.... all the barrels had the goo floating around for a few days of playing no crashes at all... today the game just shut off and quit twice in the row within minutes of starting... idk i have 4060 rtx and i turned on turbo performance... just weird... no other game ever crashed just borderlands 2

i should also mention im on acer nitro 17 laptop rtx 4060 windows 11... yeah i tried getting win7 on a separate partition but that's impossible

1) Just double check that the game is in fact using DX11 and not 12
12 is just a spaz fest of i think i will crash here.
I do wish the devs would revisit BL in an act of love, and rewrite the DX12 implementation
and then compile the exe for 64bit


2) try a game files validation

3) If validation does not help, temporarily rename your documents\my games borderlands goty folder
What this will do is temporarily make the game start with blank configs and no previous save files, so you can check if one is possibly corrupt etc.

If that seems to work, then you can try to see which the problem was, configs or save game
by moving the save game back and testing if it still works.
thank you for helping...
Origineel geplaatst door Wiesshund:
Origineel geplaatst door Doom Sayer:
Im just gonna 'acquire' the version they released when they announced borderlands 3 and see if that crashes. For me current ver crashes with the pre rendered cutscenes.

Should not crash, we got 10 machines here (literally) ranging from potato machines that don't even have GPU's to actual decent gaming desktops, and it runs on all of them.

Not what you want to hear but, it may be your OS install.
And yea, i have had people IRL insist, my PC is fine this game sucks it's broke, not touching my PC.
So i took an HDD of mine, plugged it in, did a clean windows and drivers install.
Installed current release of VC++ runtimes, then steam, then BL2 (minus HD textures DLC)
and it ran and ran and ran.

I said Welp, now you know what you need to do.

This is one reason why any game that recommends tweaking any aspect of the OS
or anything that does not pertain to only that game itself only when it is running, i say gtfo.
Just comes back to bit you later when if affects something else.
I pirated the game version from when Borderlands 3 released and crashes went away. Also its possible devs ♥♥♥♥♥♥ the code for certain hardware. I run a 7800x3d and 3070ti. Its possible its placebo however ones i encountered were marcus pre rendered scene and the dr zed pre rendered scene. I loaded the old version and resulted in no crash during those scenes so i deleted steam install and continued playing. To be clear exhausted reasonable solutions like deleting game folder and removing config files.

Also both installs had HD texture pack. Another note is last i played i think I was using 2700x and 1660ti. (When HD pack released)
Laatst bewerkt door Doom Sayer; 26 feb 2024 om 18:11
Origineel geplaatst door Doom Sayer:
Also both installs had HD texture pack. Another note is last i played i think I was using 2700x and 1660ti. (When HD pack released)

HD texture pack will make it crash, guaranteed at some point you will begin getting crashes
Error will be out of video memory

Reason:

DX12 rendered is F'd.
BL2 has a very early implementation of DX12 and it was buggy as hell, and remained that way.

And DX12 renderer is the only one that can virtualize video RAM to make 4gb available to a 32bit app (doesnt matter if you 4gig patch the app, that only affects system RAM use.)

So that forces you to use DX11
DX11 is incapable of virtualizing VRAM to present 4GB of it to a 32bit app
And the HD texture pack spikes VRAM use to over 2GB.
Not always, it is sporadic, but it builds up and overflows

So, you ditch the HD texture pack
Which is actually fine because
Much of it is broken.
Animated textures, that are not animated
Textures that are just plain bad and devoid of detail etc.
So removing that is no loss at all, it is actually an improvement not to have it honestly.

DX12 sadly is just too jacked up.
It just randomly crashed with a DXGL_ type of error that basically means
Your GPU just disappeared, as if the driver crashed
Except the driver never crashed, the renderer did.

It is a shame because people with lower end GPUs could benefit from DX12

In your particular crash, i wonder if something was jacked with the cut scene media/data
that somehow did show up in file validation?
< >
31-37 van 37 reacties weergegeven
Per pagina: 1530 50

Geplaatst op: 4 mrt 2020 om 1:54
Aantal berichten: 37