Co-Op Crashes in Loading Screen

Games Halo: The Master Chief Collection
1

I’m trying to play Halo 2 co-op with a friend of mine, on PC. We crash out of every campaign mission we try to load into. It crashes when the loading screen gets about 80% done with a 100% reproducibility rate. I get a numberless error message and get booted to my desktop while he is returned to the main menu after a bit. I am always the one who crashes. It doesnt seem to matter what the settings are, who’s lobby we’re in, or what mission we select. My computer is fully up to date to the best of my knowledge, and all the necessary content is installed. Neither of us have any issues loading into solo campaign missions. Trying to play CE together results in a crash back to the main menu, but not to the desktop. We had the same CE issue back when it first released on PC and just gave up trying to find a solution, we never could play it together.

I have searched around for an answer and see a lot of xbox players complaining about co-op crashes from in game without any solution, but nobody saying that they can’t get into the game at all. Does anybody have any idea what is going on with me here and how I can look to fix it? I just want to play co-op with my friend :frowning:

2

I’m also having this issue. The only mission I can load into on co-op is Cairo Station, the rest of the game’s missions will crash after loading and then remove us both from the party. Playing on Steam PC.

3

I also have this issue, could play Cario Station in coop, all the other missions DC one of us

4

same here. my roommate and I cant play together

5

I found a solution that worked for us in another thread from a few years back. Try making sure that you and your coop partner have the same in-game audiovisual settings and then start the campaign through the PLAYLIST mode. That got us in and playing fine, with rare crashes in the middle of levels. We have not checked to see if it fixes CE campaign too. Hope it helps you too!

This problem has apparently been around since at least 2016 on the xbox version, which makes me wonder why it hasn’t been addressed.