Borderlands 2 crashing SOLUTION

[Apollyon. Black Edition.]

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.

[Plankto-Ger-]

doesn`t work for me.

[Nekoji]

doesn´t work for me as well.

[Admiral]

I had a crashing problem after the shift ♥♥♥♥ update. The game just wouldn't start. Screen went to white for couple of seconds, then black couple of seconds and the borderlands2.exe just stopped itself and threw me back to desktop. Nothing worked. I tried running borderlands executive as administrator, compatibility mode, verified the files and all that good stuff. Then I noticed a crash error log file in c:\program files(x86)\steam\steamapps\common\Borderlands 2\Binaries\Win32\. I deleted it and got BL2 running again. I have no idea why that simple log file kept me from running my game. So if anyone is struggling with this ♥♥♥♥ and nothing else has fixed the problem, then try this trick! The log file name was long as hell and it had .log in the end. You can't miss it. I hope this helps.

[Nekoji]

Originally posted by Svängä:

I had a crashing problem after the shift ♥♥♥♥ update. The game just wouldn't start. Screen went to white for couple of seconds, then black couple of seconds and the borderlands2.exe just stopped itself and threw me back to desktop. Nothing worked. I tried running borderlands executive as administrator, compatibility mode, verified the files and all that good stuff. Then I noticed a crash error log file in c:\program files(x86)\steam\steamapps\common\Borderlands 2\Binaries\Win32\. I deleted it and got BL2 running again. I have no idea why that simple log file kept me from running my game. So if anyone is struggling with this ♥♥♥♥ and nothing else has fixed the problem, then try this trick! The log file name was long as hell and it had .log in the end. You can't miss it. I hope this helps.

i deleted that "borderlands2_1779011_crash_2020_1_13T17_33_39C0.mdmp" that u kinda mentiont but still dont working // i tried allot of ways till now

[sputzelein]

same here, deleting doesn`t help.

[Admiral]

Hmmph. Sorry guys. For me it did the trick. I hope gearbox fixes that ♥♥♥♥♥♥♥.

[sputzelein]

No problem, we have another chance:
Possibly the not starting problem occurs with windows users with non english characters under C:\windows\users
If steam is installed under such user the bifrost.dll creates a new user with kryptic characters.
2k support is investigating this, maybe they will patch bifrost.dll to support all usernames.
I hope.

[Admiral]

Originally posted by sputzelein:

No problem, we have another chance:
Possibly the not starting problem occurs with windows users with non english characters under C:\windows\users
If steam is installed under such user the bifrost.dll creates a new user with kryptic characters.
2k support is investigating this, maybe they will patch bifrost.dll to support all usernames.
I hope.

Damn. Never thought about that. I have non-english characters in my windows username and steam name as well.. But still weird that for me just deleting that crash log helped. Well, thanks for your input and good luck solving this!

[Plankto-Ger-]

lol for me the delete crashfile thing worked duno why but game is running again! befor that i tryed to rename the cryptik username to normal.......nevermind it just works! thx

[Admiral]

Originally posted by Plankto (V69):

lol for me the delete crashfile thing worked duno why but game is running again! befor that i tryed to rename the cryptik username to normal.......nevermind it just works! thx

I'm glad that it at least helped someone :D

[Flyfur]

Originally posted by Svängä:

I had a crashing problem after the shift ♥♥♥♥ update. The game just wouldn't start. Screen went to white for couple of seconds, then black couple of seconds and the borderlands2.exe just stopped itself and threw me back to desktop. Nothing worked. I tried running borderlands executive as administrator, compatibility mode, verified the files and all that good stuff. Then I noticed a crash error log file in c:\program files(x86)\steam\steamapps\common\Borderlands 2\Binaries\Win32\. I deleted it and got BL2 running again. I have no idea why that simple log file kept me from running my game. So if anyone is struggling with this ♥♥♥♥ and nothing else has fixed the problem, then try this trick! The log file name was long as hell and it had .log in the end. You can't miss it. I hope this helps.

Reached out to 2K support regarding this problem (February 28th), as I experience it in both BL2 and ThePreSequel. The haven't been able to identify the problem yet.

[sputzelein]

You know whats funny?
I did nothing and today both games tps and BL2 launch again as if there has never been any promlem. And there was no download for updating.
I didn`t anything with that strange windowss username folder.

[Flyfur]

Found a crash dump file between my Borderlands 2 files (created Feb 28th), when I opened it, the file said the the Application had thrown an Exception due to not being able to read/write to some location.

I then took a look at all the modules used by Borderlands 2 (also listed in the file) and their paths and found that 11 of them had paths that didn't exist on my PC (they were valid paths by format, but had wrong addresses)

The affected DLL were:
- Borderlands2.exe
- steam_api.dll
- bifrost.dll
- nvtt.dll
- dbghelp.dll
- bink2w32.dll
- PhysXExtensions.dll
- PhysXLoader.dll
- PhysXCooking.dll
- PhysXCore.dll
- cudart32_41_22.dll

(I also experience crashes with Borderlands: The PreSequel, but I didn't get any crash dumps there)

To me it seems that the update might have overridden some local config data, which disables the game from finding and successfully loading these extensions

[Sanctified Reach 420]

i had a crashing issue when i changed it to my resolution, so i started it in a window now no problemo at all....

[Flyfur]

I've tried most of the solutions suggested here on Steam Discussions unfortunately none of them worked for me. After almost two weeks of talking to 2K Support this is what the suggested to me, which fixed both Borderlands 2 and ThePreSequel:

1. Deleting the .inis in Documents/My Games/Borderlands 2/WillowGame/Config. We know some users make tweaks to those inis, so we suggest taking note of what tweaks you have made before deleting them.

2. Ensure that Windows Firewall is not blocking traffic from Borderlands 2

3. Deleting the Bifrost.dll in Borderlands 2/Binaries/Win32 and using “Verify Integrity of Game Files” through Steam to redownload the dll. Windows may prompt you about Borderlands 2 the next time you run the game; make sure to accept this prompt.

4. We believe there is an unwanted interaction between Windows 10 User Account Control and Bifrost.dll. To remedy this, for the time being, a number of approaches have helped some users:
- Disabling User Account Control (UAC)
- Reinstalling the game and accepting the prompt if Windows UAC asks about Borderlands 2
- Making sure your Windows 10 is fully up to date. It can be easy to fall behind on Windows
updates without realizing it so make sure to double-check.
- Run the game in Administrator Mode

I hope this works for you too.
(Note: Backup your .inis before you delete them)