Exactly what the headline reads. I’m trying to finish the Mongrethod quest but whenever I click to portal to at the Seat of Depravity, the client crashes at the load screen.
I’ve repaired the client, removed the necessary files, and finally reinstalled the game all to no avail.
Thoughts?
I’m having the exact same issue, I’ve tried 4 times already.
I’m having the same issue. Tried fixing with new Cache, WTF, and Interface folders and running that advanced command with no luck.
add me to the list. crashed about a dozen times because i’m stubborn
Glad to see I am not mad or the only one having issues with this quest. Thought my game files were ALL corrupted. So uninstalled and reinstalled and it didn’t fix it. It seems it has to do with the game code itself for the portal you click on to get to the fight.
Same issue as everyone else. Tried running game with no addons, tried repairing game, just can’t complete this quest. 
Same, keep crashing with an access violation every time I click on the gateway.
Same issue here, running on Mac. The loading screen shows and then it crashes.
I’ve abandoned the quest and picked it up again, but the same thing happens.
Yep, crashes for me, too.
I bet it was probably broken by 10.0.7, somehow.
I can also confirm that trying to enter Dreadscar Rift crashes the game as well, so the problem is most likely related to the type of portal used to load into these zones/instances.
Yes quest is bugged, I have crashed 6 times trying to complete.
Adding on a “same here” to keep the thread rolling. My poor druid just wants that sweet, sweet XP!
Is this an Error #132 crash to desktop? Because if so, there seems to be major issues involving portals and crashing. Priest, DH, Pally, Hunter and more are all affected by portal crashing to desktop error 132 during parts of their order hall campaign quests. I have had to use Blizzard’s stuck character service 3x now for my Priest because I get a crash loop when entering the portal during “Crossing Legion Lines” quest. Lots of others are having issues entering portals and getting error 132. Even saw someone post about it when trying to enter a WoD portal.
My issue seems to be resolved. I updated my Nvidia driver, closed all other applications, and re-attempted to use the portal. This worked. Could have been the driver update or applications, or the recent hotfixes but worth retrying now folks.
So I just tried it and it worked fine - I had to go to Chromie to go to the WoD timeline and it worked like a charm. It’s stupid but it just might be the trick
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.