#206

Start here:
https://support.2k.com/hc/en-us/articles/360009266794–PC-General-Troubleshooting-for-2K-Games

For completeness, this link replaces steps 3-5 in troubleshooting for windows as the guide above is outdated (same link as above post):
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

If that does not work you can submit a ticket using the link here:
https://gearboxsoftware.zendesk.com/hc/en-us/categories/360002121592-Borderlands-3

Let them know you have already tried the above and attach your DXDiag, MSInfo, and any screenshots of the specific error popup. Instructions for getting these are here:
https://support.2k.com/hc/en-us/articles/201335133-How-do-I-attach-a-DXDiag-and-msinfo-file-from-my-PC-

#207

i crash in specific locations like crazy earls shop and the shooting range or when i use cov weapons but i mainly crash in sanctuary 3 i updated everything

  1. my drivers
    2.my bios
    3.my windows
    4.the game
    idk why i keep crashing i have a gtx 1080ti fe 16gb ram i7 8700 when the game runs ir runs awesome but then i will crash in thease locations
#208

Guys I think you should try to disable cloud saves on the epic launcher side. Since I did that, I haven’t experienced a single crash y many many many hours of playing. The issue doesn’t seem to be related to drivers nor anything more technical. This just did the trick to me.

#209

Makes sense. Whenever I install games via Steam the C++ and Redist files install as part of the game’s installation. I’ll do that and see where I’m at. Thanks for the heads up.

1 Like
#210

Not sure anyone still reads this thread or is having issues but I resolved my issue (though may be more niche) .

TL;DR : Ram Speed of 3200 MHz was causing the game to crash. Suggest changing values to 3000 or higher/lower.

The issue I ran into was running RAM at 3200 MHz.
I have a stable 3200 MHz configuration (been running it for ages), yet the game would crash on it.
Somehow my MOBO flashed and uploaded an old profile. When I was playing it wasn’t crashing.

My PC was a little sluggish so I was checking Task Manager looking for a RAM/CPU hog. I noticed the RAM speed was at 2400 MHz.

Since I wasn’t crashing I played another hour or so at those speeds and was fine. I put it back to 3200 MHz and crashed with-in 10 minutes. This lead me into a testing cycle.

I tested my RAM with 2666/2800/3000/3200/3600. The only one that crashed was 3200. Now I know some might say my 3200 obviously isn’t stable, but considering I’ve ran my PC at that with multiple games for years, I disagree.

I spent about 100 hours testing computer components, fresh installs and in-game testing. I have had 0 issues since not using 3200 MHz.

As I said, I might be a more niche case. I’m using an AMD Ryzen CPU with memory optimized for Ryzen. I do not know the EXACT reasoning behind it but I haven’t had any issues.

#211

I really hope the best for you and I do not want to take the hope for you, but since I myself thought several times to have found the solution, I tell you, give the whole at least two to three days to test. I’m more and more convinced that it has nothing to do with our machines, because almost everyone reports problems only in the context of BL3 where other games work on the same machines. Nevertheless, I hope for you that your problem was solved.
Regards

#212

Dont use nvidia experience thats the bug , just disable borderlands 3 in nvidia experience and then open borderlands 3 en set your settings self in the game .

#214

game freezing still when open inventory freeze is 2-5sec when i chenge weapons same total freeze.
in many location still FPS terrible drops from 120-144 fps to 25 in half sec adn back very very bad
this problém i have only in B3 and i think after last hot fix is this problem much harder:(

#215

Looks like there is a whole bunch of us having the same issue. I was able to run it fine before the patch and afterwards just crashes randomly. I thought my machine just wasnt good enought (i have an old build) but looking at forums it seems its something to do with the patch. Hopefully commenting here might promote this and get the attention of the people patching up stuff. If anybody has found something that works for them would appreciate sharing it since I wont like to miss the comings events :smiley:

#216

I have 2 machines, one with a 1080 and the other with a 1080i, both running the same drivers. Both machines have the same mobo, RAM, and processor. The machine with the 1080 runs mostly fine (just crashes once in awile when closing the backpack), while the 1080i machine crashes randomly and often, and sometime corrupts the save while crashing. Windows 10 actually blue screens after the game crash. This behavior was the same both before and after the patch. I have also tried every other “fix” in this thread with no improvements. At this point I am at the mercy of Gearbox to find and solve the crashing problem.

#217

My game was running fine the entire release until the last patch. Now I get random game freezes after about ten minutes of playtime. I tried default settings, removing GeForce Experience, and several other video settings, running on Ultra, Low, and default…Nothing worked thus far. I did a fresh install and will see if that fixes the issue…Any others with this problem? Is gearbox looking at these issues?

#218

I am having the same issue, was fine for me at the release of the game, now it is unplayable

#219

Still doing it after fresh install…anyone have any fixes? This time it was looting a chest playing solo. Yesterday it seemed to be swapping weapons. There seems to be a frame rate studder right before the crash and close of the program. Running 2060 newer comp with no issues on other games.

#220

I had this issue about a week ago:- during the GENIVIV fight the PC would crash and reboot. Then I would get the intermittent reboots after claptrap loading, sometimes on menu screen, and then always in the GENIVIV fight if I got that far. I played around with graphics settings/ windowed/full screen DX11/DX12 all the usual stuff but the only thing that got me through the fight was to disable my NVIDIA audio adapter. So I finished the fight and was able to cleanly quit the game and restarted with audio adapter enabled and I was good…for a few days. Then about 2 days ago (i’m guessing after the 10th Oct patch but maybe not) I am back to to getting random reboots of the PC, sometimes when generating a car at a Catch-A-Ride, sometimes after claptrap loading screen, or sometimes just playing randomly in game. Like everyone else I can get about 10 mins of gameplay before it reboots my PC again.

I’ve raised a ticket that is currently being ignored by 2K and I’ve provided profile.sav file and save game files. (I suspect maybe one or all of them are corrupted). Also provided msinfo and DXDiag as they requested.

I dont have much to offer other than to confirm I am another person this is happening to, and the game is unplayable.

#221

What I have found doesnt work (for me)

  • running Epic Games Launcher in Administrator mode (Win10) - still crashes
  • running DX11 - still crashes
  • running DX12 - still crashes
  • disabling audio adapter (literally playing without sound) - seemed to work at first but still crashes
  • Windowed mode / full screen / Borderless window - still crashes
  • Set graphics to Low - still crashes
  • Verify files n Epic Games Launcher - still crashes
  • Disable GeForce experience - still crashes
  • NVIDIA drivers and audio drivers up to date - still crashes
  • Disabled cloud saves - still crashes

My PC does not reboot/crash under any other software.

Whats especially annoying is I got a whole playthrough done under Zane with no issues at all, it was only after I started playing thru as FL4K that I started getting the crashes.

1 Like
#222

Same problem with crashes with moze after some of the recent patches
-crashes while in sanctuary ship running
-during cutscenes
-traveling to a new location with the space ship

Thanks for your summary though

#223

same problem here what specs do you have?

#224

A friend of mine has been getting the same issues as me, different rig…same issue that started on the 10/10/19 patch…what is the deal? Can they not fix the issue for a game that is less than a month old and unplayable?

#225

Same problem here. Got randow freeze crashes since the launch of the game, but since the newest patch it seems to be much worse. I can play between 30 and 60min now before crashing again. Before it was between 1 and 3 hours of gaming.

I also opened a ticket to 2k and gearbox with all needed info like dxdiag, msinfo, crash log, hardware and temps etc. But I got nothing but there generic “clear cache, reinstall game, blabla” answer.
The Error Log says:

LowLevelFatalError [File:Unknown] [Line: 200] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')

A quick google search didn’t reveal anything useful.

I tried the following things so far:

  1. Reinstalling Epic Games
  2. Reinstalling Borderlands 3
  3. Closing and disabling Overclocking (MSI Afterburner)
  4. Closing all programs in the background including anti virus software
  5. Clean Reinstall of Nvidia Drivers
  6. Updating Windows
  7. Installing the newest VC_redist.x86 and VC_redist.x64
  8. Starting Epic Games Launcher as Admin
  9. Trying DX11 and DX12. DX12 crashes 1min after getting into the game.
  10. Verifying the game date via Epic Games launcher.
  11. Setting a manual virtual memory pagefile size .
  12. Using Window Borderless or Fullscreen.
  13. Setting max FPS to 60.

Nothing worked so far. The freezing comes really at random: Sometime while a lot is going on onscreen, sometimes in the inventory menu, sometimes even in the game menu when pressing esc ingame.

So I’m out of ideas now, I don’t think it is an hardware problem, because the temps are looking fine and there doesn’t seem to be a memory issue anytime.

Anybody got any ideas left?

#226

What resolution are you running? I have noticed people with the problem (like me) are running at 3440 x 1400 (21:9). I’ve tried running in windowed mode at a lower resolution 1920 x 1080 (16:9) and actually haven’t had a crash yet so will keep going and see how it goes.