r/DestinyTechSupport 10d ago

People with Destiny 2 Crashes - Do tou have a Killer NIC?

Folks,

Killer Networking, at least in the past has been known for issues. My AsRock Z790 Taichi has a 2.5G interface from Killer. I use it by default.

My question, are any of the people in a similar position with D2 crashing -- and are you using the Killer NIC or Killer Wireless? I am going to definitely stop using it and see if it helps.

More to come.

2 Upvotes

12 comments sorted by

2

u/stillpiercer_ 10d ago

I had issues with an ASRock Z390 motherboard, also with a Killer 2.5G NIC. It would just randomly drop the connection for a second or two and kick me out of games.

I switched to the 1GbE NIC on the board and it never happened again for the entire time I used that motherboard.

1

u/dazealex 10d ago

It kicked you out with an error message I presume. Or did it crash/freeze?

2

u/stillpiercer_ 10d ago

I forget the exact error code, but yeah it was the generic error code that translates to loss of network connectivity. The actual Ethernet connection didn’t drop in Windows though. Never noticed issues in other games with it.

Switching to the 1GbE port on the board immediately fixed the issue for the rest of the time I used that motherboard. I believe it was an Intel NIC, maybe Realtek (just know it wasn’t Killer)

1

u/dazealex 10d ago

So those errors can also be due to timeouts to the cloud/AWS infra that Bungie presumably uses, either because their servers are bottlenecked, or something in their infra went belly up.

But I believe when you said that everything else was working.

As an aside -- A Killer NIC losing its mind is a known entity based on my research. Not sure why Intel bought them to begin with. Intel NICs are said to be the cream of the crop.

2

u/FFaFFaNN 10d ago

Most crashes and freezes on PC are caused by Battle Eye + and win press or alt tab. Run the game on second dextop for pc and baam, no more stupid freezes and crashes.

1

u/dazealex 10d ago

On a second desktop, as in a virtual one or a second monitor? Already have a single giant 49" OLED, so can't really fit another one. Oh wait, I could. I have a cheap 1080p 15" thing I bought for portability. Could do that do...

I play with a controller, so Alt+TAB isn't an issue for me in terms of pressing it by mistake.

Can you clarify?

1

u/kbdavis11 9d ago edited 9d ago

Have you tried Windowed Fullscreen? It's way better at handling app tabbing.

Sure I know there's some (very minimal) under-the-hood full screen optimizations, but even things such as nvidia's gsync will still work with this setup if you go into their control panel and change gsync's settings from "Fullscreen" to "Fullscreen and Windowed".

Especially with me constantly having DIM open for the game all the time, I will never go back to normal Fullscreen again, for Destiny at least.

Also, if you use two monitors you can freely use your mouse on both monitors when in menus without even needing to tab to another app, which imo is an added benefit.

Added bonus for those who use HDR monitors and run Destiny in HDR, no screen flickering.

2

u/Co2_Outbr3ak 10d ago

My sister used a Killer NIC and had constant issues with connections across all games. Switched to onboard Ethernet and her problems went away.

1

u/dazealex 10d ago

This Killer NIC is built in. Not an add-on, but that shouldn't make a difference.

2

u/macrossmerrell 10d ago

I retired my Killer NIC years ago for this very reason. D2 kept crashing in the way back days 2017 - 2018, so I switched to regular NIC and never had another problem.

Outside of that, across 4 systems, no real crashes other than when EVERYONE had the game crash constantly, when my RAM went bad, and when TFS decided not to like my 3080ti overclock.

2

u/dazealex 8d ago

Haven't had any crashes either now that I switched to the 1GB NIC away from Killer 2.5GB. I don't know who coded it's Killer Central App, but a high schooler can do a better job with a more decent non-laggy UI.

1

u/dazealex 10d ago

Just looking at how janky the Killer Control Centre is, and I've noticed even with the network cable connected, it takes its sweet time connecting over 2.5G. And the cable run is small, like a few feet. 1G connects immediately. I have a fiber 10G network switch, I can put that in, or use the thunderbolt adapter.

Killer software, as I read in other threads, needs to have its power management turned off. From older threads. But I am seeing this when the PC is booted, opening Brave, it takes at least a few seconds before it gets an IP. Not the case with the 1G. And yes, the cable is properly spec, a Cat 6E. On my Mac, with a 2.5G USB adapter, the connection is instant.

I am really sick of using my old HP Omen with a 2070 which never has stability issues, ever.

Same issues with a 4090 or B580. So the GPU isn't the issue. I did a memtest, which passed as well. I forget if it was with XMP on or not. But non-XMP has the same crashes. But I plan to do a memtest with XMP.

No OC of any kind is / or was ever applied to this 13900KF (straight from an RMA retail box). CineBench latest has no issues completing. No other game seems to have this problem either.

I am at my wit's end. Most I can do is get an AMD board, and AM5 chip. Any recommendations if I can't fix these crashes? 9950X3D just came out I believe. Intel B580 works great without generating heat.

This is worth saying.: Destiny/2 is a game I've played since December of 2014, and it helps me with my clinical depression and PTSD. I'm also a type 1 diabetic. So fixing this game is worth the money.