Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This topic has been locked 
Discussions Rules and Guidelines
Report this post
Nope.
It's been broken on pretty much every type of drive you can have on a PC.
It's been on my OS SSD, a HDD bulk storage drive, and now resides on an M.2 SSD.
Files have been verified, the game has been uninstalled and reinstalled multiple times. I never tried to transfer it and just uninstalled and clean installed it onto whatever new drive I put it on, and it's still busted.
It's not hardware because, again, I'm running it on entirely different hardware than before, with a completely new install of Windows on a brand new drive.
The game doesn't like to run with DX12 on high end GPUs for some reason. I'm not the only one with this problem, and most of the complaints I've seen about it are people running high end cards, 2080ti, RX 5700 XT, 1080ti, etc...
It started when I went from my old 7970 ty my RX 5700 XT and has persisted across multiple driver updates.
It's not the card, because I'm not having problems with any other games, including several DX12 titles.
I can run the game at over 60fps on Badass settings, but DX12 is a performance difference. I pretty much always get higher framerates using DX12, which is the only reason I care. My monitor refresh rate is higher than 60hz, so I can take advantage of higher frames if I can get them.
I get a CTD after the splash screen when I try to launch the game and an error message that lists a bunch of .dll failures.
If I enable DX12, I have to go into the config files to change it back to DX11 to get the game to run.
It started when I upgraded from a Radeon HD 7970 to an RX 5700 XT.
I've seen other high end cards that have the problem, but the RX 5700 XT in particular seems to have problems running BL3 with DX12.
I'm probably going to replace my RX 5700 XT later this year or early next year. The card has been kind of a pain to deal with, even though when it works like it should it's great. More often than not it does at this point.
The drivers were plagued with problems for a long time after it came out. It's mostly cleared up, but is still more trouble than the other cards I've owned over the past fifteen years or so. Lots of small issues, with BL3 not wanting to run DX12 probably being the biggest remaining irritant.
Not sure if I'm going to go with a 3080, whatever "ti" card they make for the 3000 series, or whatever new thing AMD is supposedly putting out possibly later this year or early next year.
I'm not going to bother with trying to get a founders edition 3080 or anything, and want to wait and see what AMD is going to do, and how long before a Nvidia 3000ti card will be released, and what the specs will be on all of that before I buy anything.
I also want to see what MSI, Sapphire, HIS, etc... will be doing with their versions of the 3000 series as well.
We should know all that before the end of the year.
Same here. No issues whatsoever.
I'm running it with at RTX2080 Super, max settings on DX12, with no issues, installed on a Sata SSD.
What type of PSU and wattage are you using on your build?
People tend to look at the GPU, CPU and storage device when a game crashes, but there's one thing that is, currently, the new bottleneck in terms of hardware: the sound card.
Many motherboard (even some for gaming) have generic HD audio sound card which are compatible only up to DX11. The reason why I know about the sound card potential issue is because I had this issue with a game when DX9 came out back in the days. One game would get a BSOD whenever a certain amount of sounds plays in a certain way in a game that ran at a steady 30+ FPS. When I searched online, I found the 0X00 error to be specifically related to the motherboard returning a total fail code from the sound card (which was an integrated one). Back then, PC's integrated sound cards were pretty bad for gaming. This initiated me to know more about sounds cards and their actual uses in the game development.
Nowadays, motherboards with integrated sound card usually cover up to DX11, but not always up to DX12. "Why the F&CK would it be that massive of a deal" then?
Well, one of the first thing that comes with DX12 is a new library of full chucked codes that allow the GPU to basically manage a certain range of audio sounds registration for the sound card to handle. We're talking about twice as many layers (channels) as DX11. You might not know this, but DX11 is limited to 16 sounds channels to be handled at once. (If more sounds are played together, it usually involves a process of fusing sounds together in bit form to fit them in a single channel as a single sound source.) DX12 has 32 sounds channel by default. If you send 32 sounds channel to a 16 sounds channel compatible sound card, you ends up with either a CTD or a BSOD depending on if there's a process to handle such crash in the system or not.
Yes, the GPU handles sounds nowadays in modern games. It doesn't handle their output, but handle most of their 3D calculation such as position, orientation and strength such as with 3D surrounds.
In the past, that was handled by the Sound Card, but considering the low level of advancement for Sound Cards in gaming (in comparison to GPU and CPU), something had to be done so engines were made to use mostly the GPU and CPU to handle the sounds and convert it into a language that even a basic HD audio sound card can play. That is, prior to DX12 being a totally new beast that works differently than DX11 in that regards.
If you're crashing right up the front after the Splash screen while it was working prior to a patch, it's usually due to a core change in the engine's process. If they patched some of the DX12 libraries for more stable ones and one of such uses the latest DX12 sound-related libraries while the old one was using the DX11 version of it, it could explains why the game suddenly broke. (Yes, using DX12 in a game doesn't automatically means it's 100% DX12. If they were using a version from 2 years ago, it's mostly half DX12 and half DX11.)
I'm not pointing out that this IS the issue for you, but that's one thing to consider and seems to have evaded your mind up to now.
One great thing you can do to check what cause the crash is to open the Event Viewer app, go to Windows Logs > Applications and look up whatever code was registered when the game crashes. In case of application crash, it's usually a red circle with a <!> in it. It won't tell you anything you'll mostly understand, but it will allow you to know the error codes that results from the crash and with those codes, you might be able to Google the actual source of the issues more closely.
Remember, if a game crashes for many, but not everyone, it might be half the fault of the devs, but it's always at least half the fault of the user even if it's out of their control or knowledge. This is why so many games on consoles were never ported to PC as consoles have limited ranges of hardware possibilities which is easy to test and oversee in comparison to PCs which has over thousands of possibilities in every pieces of the machine.
This is good information that may help someone else, but not my problem. I have a brand new MSI AM4 PCIe Gen 4 Mobo. My current board's model was only just released a few months ago.
My current system was literally built about a month ago, and my previous build had the same problem with a different Mobo.
As I've said, I run multiple DX12 games without problems and usually get better performance with DX12 titles, this is isolated to BL3, so that does not explain it.
Found a workaround, which confirms it's the game and not my hardware.
I say workaround and not "fix" because the game is still broken.
What I had to do was delete everything in my C:/users/username/documents/mygames/borderlands3 folder but my save games.
The game then launches in DX12 mode and runs giving me about a 8-10 fps performance bump. I'm in the 65-75 range instead of 55-65 range on Badass settings.
However, I have to do this every time I launch the game, or I get the same crash again. Once it is launched it runs perfectly stable using DX12 on Badass settings using HDR.
This is a game end problem.
I have a 1200 watt Platinum EVGA. It's not my PSU.
Like I said in an earlier post, I have seen others with high end cards that have the same problems I do, but the AMD 5700 cards in particular seem to have trouble running BL3 in DX12.
Found a workaround, which confirms it's the game and not my hardware.
I say workaround and not "fix" because the game is still broken.
What I had to do was delete everything in my C:/users/username/documents/mygames/borderlands3 folder but my save games.
The game then launches in DX12 mode and runs giving me about a 8-10 fps performance bump. I'm in the 65-75 range instead of 55-65 range on Badass settings.
However, I have to do this every time I launch the game, or I get the same crash again. Once it is launched it runs perfectly stable using DX12 on Badass settings with HDR.
This is a game end problem.
Try to empty shader cache, from AMD drivers UI.
Try latest WHQL drivers, not latest drivers.
Try start your game from your game folder, with a right click, and "run as administrator"
Try to empty shader cache, from AMD drivers UI.
Try latest WHQL drivers, not latest drivers.
Try start your game from your game folder, with a right click, and "run as administrator" [/quote]
Not bad suggestions, but unfortunately I've already done all that with no results.
My page file is 32 GB and has been for a while. [Swap File is the same thing for Linux systems in case anyone is wondering, it can also be called virtual system memory.] I've got 16 GB of DDR4 RAM, and the "rule of thumb" if you set it manually is double your system RAM.
Even if you have 32 GB of RAM, you really shouldn't ever need more than 16 GB in the page file. Mine is overkill without being excessive enough to be a problem no matter how you look at it.
I've also had it set to allow the system to decide for a bit recently, which is around 5 GB, with the same results, so it's not that my page file is too big either.
Page file/Swap file is weird in that it is entirely dependent on the system, and there is no "rule" where a specific amount or formula works on every system. Even identical systems can vary more than you'd think with how much they actually need, just based on what the end user is doing with them.
GPU Drivers have been uninstalled and reinstalled several times since this started happening. I use DDU to uninstall, which automatically clears the shader cache.
The card has also recently been installed on all new hardware after being uninstalled with DDU, including a new OS drive.
I've had the card since near when they were released, it's the oldest component of my current PC and the shader cache isn't the problem.
Even though I'm not currently I've used several WHQL drivers and still had the same issue.
This isn't my first rodeo so to speak, and I've trouble shot this thing for quite a while with no results.
Basically, the only things that work are either launching with DX11 or deleting the cache folder in with the save files before I launch the game, which lets me run DX12 for that session.
So, if anyone is still having issues with DX12 today like I was then give it a go.
Don't just dismiss it as a possible cause because you have a fairly new system. The driver that windows provides automatically is from 2015! It's probably a cause for various crashes in more modern games.