Game mode: Both Online official | Online private Type of issue: Crashing and Resetting Modem after logging in to MP game Server type:PVP
**Region:**US-Mid
Same as this bug from last year, but it is PC, not Xbox
/crash-to-dashboard-now-includes-router-crashing/80080
After June 16 patch.
I had logged in before the hotfix so I had to wait till the June 18 patch. This was on a private server US_East. After 1 minute of being logged in it crashes to dashboard AND makes the cable modem drop the internet. After it resets I can use the internet again. This happened 4 times before I realized it was not just my ISP dropping. Biggest similarity, I have Charter Spectrum as well.
Tried to join Official servers to test mods. 2 different official servers #1766 was one of them. Same thing happened. Not a mod problem I am assuming.
I can get into a Single player game, however, I cannot get anyone to join me after they see my invite.
Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:
Log in to MP
Wait 1 to 1.5 minutes
Things get weird (falling through floor, things not responding, etc.) then crash to dashboard
Notice that all internet is out and the cable modem is resetting.
Welcome to the community.
You mention that you logged into an official server to test mods. Unfortunately, joining an official server with mods is not possible. Additionally, other players who want to join you in coop mode need to have the same mods, with the same version and load order in order to join.
Thank you, but you might have misread what I said. I checked the official servers for the reason that they did not have mods. Thus when my modem crashed it ruled out that it was a mod problem.
As for co-op servers, my buddy and I painstakingly have matched up everything and they are in the same order, yet we cannot connect to each other.
@Ignasi I found the exact same problem again on redditt, but from 3 years ago (cannot post links here but I would if I could). Can you please check into this. It looks like a problem that happened before and is now happening again after the June 16 patch. Thank you.