Aller au contenu

Photo

Mass Effect 3 Crashing during Shroud Mission and/or Cinematics


  • Veuillez vous connecter pour répondre
Aucune réponse à ce sujet

#1
Wyldwraith

Wyldwraith
  • Members
  • 2 messages
Hello,
I've been struggling with this bug for over 3 weeks now. It turned up the first time during the cinematic in the Earth: London mission, when you leap aboard the shuttle after destroying the Hades Cannon with the M-920 Cain. At the exact same point in the cinematic cutscene the game would freeze, then drop to a black screen as a "Mass Effect 3 has stopped working" box popped up in the middle of the screen.

So, I bought a new graphics card because my GeForce 460 GTX had been giving me other problems before this. Got a Radeon R6770, updated to its latest driver after uninstalling and deleting Mass Effect 3. (Lost my Saved Game folder on my desktop thanks to poor instructions from one of the Live Chat techs, but that's another story.)

So I re-download ME3 (basic edition, digital download), reinstall and start from scratch after spending well over 40hrs on both the phone with Call Back Tech Support and online with the awful Live Chat support.

This time I get up to the Shroud/Curing the Genophage mission on Tuchanka and as I'm going through the old Krogan city ruins I come to the room with the pillar in the middle and the salvageable Krogan Art on the wall. Also tried the stairwell going down that bypasses that room. In both cases the game freezes, drops to a black screen and the "Mass Effect 3 has stopped working" window pops up in the middle of the screen, and eventually turns to a Close Program tab.

I've done everything I can think of. Tech Support has supposedly referred my problem to Tier 3 Tech Support, but that was 5 days ago and I've heard nothing since. I sent an email through the help page explaining all this again, because I was told not to use the ticket # again or it'd bounce the issue back down from Tier 3.

I'm at my wits end, and the game is COMPLETELY unplayable. Does anyone know of a fix for this bug?