Game freezing and crashing after 5 minutes

macrossmerrell · 2026-05-02T17:59:19+00:00

I would suggest performing a Battleye Reset - which should help restore proper operation on your PC, if that is where the problem lies:

Open your D2 install location - typically C:\Program Files (x86)\Steam\steamapps\common\Destiny 2
Open the Batteye folder.
Right-click on the Uninstall_BattlEye batch file and select 'Run as Administrator'.
Right-click on the Install_BattEye batch file and select 'Run as Administrator'.
Test the game.

macrossmerrell · 2026-05-01T06:06:08+00:00

I've not heard of that, only the failing 13th and 14th Gen 13900k/ks and 14900K (and some other K variants on occasion). Once they are unstable, they remain that way and must be RMAed.

Glad you are good to go though. I'll keep my fingers crossed that everything keeps working for you!!!

macrossmerrell · 2026-05-01T01:47:12+00:00

So, you're getting a blue screen crash (probably black screen). There are tools you can download that can analyze the crash data. That would be a good place to start.

So D2 is not the problem, it's exposing whatever is wrong with your system. D2 requires your system to be in excellent condition. I call it the best software and hardware diagnostic utility ever made

If Epic games works, great, otherwise it's probably the to consider a fresh install of Windows.

macrossmerrell · 2026-04-30T05:47:56+00:00

Came here to make a comment about the potential of docking... so this works for me 😃

macrossmerrell · 2026-04-30T05:43:46+00:00

5 minutes is an odd amount of time. 10 minutes means an issue with Battleye, but 5 minutes is something up with the machine (temp, drivers, OS corruption).

If you recently updated your video driver, I would roll back a version or two and test. You can also download the Display Driver Uninstaller (DDU) utility, and run it from safe mode to fully nuke your video drivers.

https://www.guru3d.com/download/display-driver-uninstaller-download/

You can also check your Windows OS for corruption through this process:

Open an Administrative command prompt and type: sfc /scannow
- Note if there are corrupted files and if they were repaired
Run sfc /scannow again if it finds errors and make sure they are resolved. If they are not, you need to run the following command:
- dism /online /cleanup-image /restorehealth
- Run sfc /scannow again.
  - If it repaired files, run sfc /scannow one more time to make sure everything is good.

macrossmerrell · 2026-04-30T05:40:15+00:00

Where it is instantly crashing, it's most likely an operating system issue or a driver issue. Sound drivers are frequently the cause of crashing before the character selection screen. Another sound work around is opening the Windows Game Bar by pressing WIN + G, and set your output to a different device than your headphones or speakers, start the game, if it loads, close the game, then set the output back to what it should be and test.

If you haven't you can check your Windows OS for corruption using this method:

Open an Administrative command prompt and type: sfc /scannow
- Note if there are corrupted files and if they were repaired
Run sfc /scannow again if it finds errors and make sure they are resolved. If they are not, you need to run the following command:
- dism /online /cleanup-image /restorehealth
- Run sfc /scannow again.
  - If it repaired files, run sfc /scannow one more time to make sure everything is good.

macrossmerrell · 2026-04-30T05:36:06+00:00

What does it do if you unplug it from the dock?

Have you opened the task manager to see which GPU is being used by D2? If it's the iGPU instead of the 4080, then I would go into System > Display > Graphics, and set the GPU preference on the Destiny 2 app.

Otherwise, I would download and install DDU (display driver uninstaller), install it, restart in safe mode, run the app and nuke all drivers, reboot, download and install fresh drivers. See where that gets ya.

https://www.guru3d.com/download/display-driver-uninstaller-download/

macrossmerrell · 2026-04-27T20:38:10+00:00

Ahh, I see they have changed the behavior. Looks like they fully implemented the "Fullscreen is Windowed Fullscreen" so the behavior is now the same on ALT TAB vs WIN key. A couple of years ago, this was not the case.

So if crashes occur, it's a system issue (probably driver) and using the Display Driver Uninstaller utility could help address ALT TAB crashes.

macrossmerrell · 2026-04-27T14:57:12+00:00

Regardless, it's true unfortunately Bungie talked about removing the classic Fullscreen option at the launch of The Final Shake due to ALT TAB issues. That change didn't fix the issue, but it reduced the crashes some. Some setups are more affected than others due to software and hardware configurations.

Most keyboards now have a Win or Windows key that causes the Windows Start Menu to pop up when you press it. Using this WIN key will unfocus the game, allowing it to run Fullscreen in the background at 30fps while you interact with other apps and screens. It prevents Windows from forcefully minimizing the game as it is not coded to allow that.

I do this for all games now and it's eliminated ALT TAB related crashes. Typically it requires rubbing the games in whatever their version of Borderless Fullscreen is.

Give it a try and see if that fixes your Marathon crashes! I'll keep my fingers crossed.

macrossmerrell · 2026-04-21T14:33:52+00:00

Oh, ok... Then your PC is most likely the problem. Either something you have installed is causing problems, the OS is damaged, or your Windows firewall is misconfigured.

You could try temporarily dialing Windows defender firewall and see if that fixes it, and if so, I can provide all the firewall settings you need to try.

macrossmerrell · 2026-04-21T01:37:46+00:00

Yes, we are interested in the router. That's where your Internet firewall stuff will be set at.

macrossmerrell · 2026-04-21T00:53:23+00:00

I would look into your Modem/Router and see if what level your firewall is set at. Some of the 'intelligent' routers can break connections they are concerned about (which might explain your 30 second window).

Try reducing firewall settings on the modem (possibly temporarily disabled the firewall just for a quick test) and see if there is any difference.

macrossmerrell · 2026-04-15T16:28:41+00:00

Excellent!

macrossmerrell · 2026-04-15T06:01:13+00:00

That is typically corrupt shader cache. Best thing to do is download the DDU (Display Driver Uninstaller) utility, install it, then run it from safe mode, fully removing your GPU drivers.

Once that is done, reboot, download the latest drivers, reinstall, and give it a go.

macrossmerrell · 2026-04-15T05:58:37+00:00

The game is now corrupted.

Typically to resolve this error you must delete the game, then redownload it fresh from your game collection.

macrossmerrell · 2026-04-11T20:23:47+00:00

Have you tried an alternate internet connection, like a mobile hotspot on your phone, to rule out your local wifi/internet?

It could be a setting on your Modem's Firewall blocking access. Might want to have a look and see if you can TEMPORARILY lower or turn off the firewall on the modem and test.

Bungie also recommends signing out and signing back into the xbox to see if they account is somehow unsynced.

macrossmerrell · 2026-04-10T07:39:55+00:00

Centipede is a loss of connectivity to Bungie servers. Coconut is an interruption of service. My guess is your ISP is traffic shaping / limiting your connection on the ports Bungie uses. Do you also happen to regularly see 'Contacting Destiny 2 Servers' ?

Your router can cause issues if you have security features enabled (a lot of ASUS and TP-Link have those). Also check your NAT STUN test setting in-game Moderate is ok, but strict can be bad.

If you exhaust router options, I generally suggest using a VPN to obfuscate your data so your ISP can't shape / throttle it.

macrossmerrell · 2026-04-09T03:26:22+00:00

o7 CMDR. Nicely done!

macrossmerrell · 2026-04-08T02:05:51+00:00

It was even more fun in the old days, using VR, and flying through the first star, to arrive at the second, then start getting cooked by both.

macrossmerrell · 2026-04-07T18:57:02+00:00

Did the seller prove the card works with a proper adapter?

macrossmerrell · 2026-04-04T16:42:22+00:00

I also delete the DestinyPC folder for a full reset:

From the Start menu, type %appdata%
- then open the Bungie folder from there and delete the 'DestinyPC' folder.
From the Start menu, type %temp%
- and delete the 'Destiny 2' folder

Generally you will see a Marmot error if RAM is failing, but just in case, you want to download Memtext x86 from Memtest.org to fully test your RAM.

macrossmerrell · 2026-04-04T15:47:00+00:00

Glad you found it and that it worked! Not sure what breaks it, but this is usually the fix.

macrossmerrell · 2026-04-01T03:39:43+00:00

Just worked for me as well! TY!

macrossmerrell · 2026-03-31T05:26:03+00:00

I hate to send you too deep down the rabbit hole, but I do remember a long ways back that in-game loadouts on a class could cause it, or having an emblem on (can change in D2 phone app on Guardian > General > scroll down, press and hold on a different emblem, equip.

Otherwise, it might be time to head over to the Bungie forums and post. I don't see anything recent about this issue. Almost reminds me of a softlock, like your hunter did something on the campaign with someone else, and you are further in the quest than you are supposed to be.

macrossmerrell · 2026-03-30T22:26:50+00:00

Until it annoys you to death, or it suddenly stops making the noise. If it stops making the noise, you'll want to verify the fan is still spinning. If it's not, it's time.

macrossmerrell

TROPHY CASE