Game Crashes on Entering Sewers of Caldeum

Bug Report
21

Not true at all.
Crashing is all about the different systems every one of us uses.
There is no vanilla system like there tended to be pre 2000.

When Blizzard was old school they had a department with hundreds of different pc’s with different OS’s and drivers in date and out of date to test playinig D3 on.

This is gone.
They depend on us now to give the data, which does not work as well from home.

Everyone has a different system from the next guy.
This is why fixing the join bug took almost a whole year.
And it still is broken.

22

Well, since I posted those comments, it seems that several (reputable) players have experienced this issue. And there are exceptions to every rule.

There is a possibility that a game bug can cause, what appears to be, a technical issue. That may, or may not, be the case here.

All we can do is share our experience and hope that the information we provide helps to resolve the issue.

23

No crashes here. (Extra)

1 Like
25

After a Windows update (I’m now on 19041.630) I just checked and I crashed at the start of Act IV approaching Tyrael and Imperius in campaign. GTX1060 with 457.09 driver. Looks like there’s a driver update available, so I’ll update and try again.

EDIT: Updated GPU driver to 457.30 and still crashing at the start of Act IV as I get close to Tyrael. Don’t seem to be crashing in Sewers of Caldeum at least.

EDIT2: I seem to be crashing when starting a new game at the beginning of Act 4, but not when I start at the end of Act 3 and kill Azmodan and then progress into Act 4. I’ve crashed all 5 times I start a new game at the beginning of Act 4, and I haven’t crashed the 3 times I start the game at the end of Act 3 and progress through to Act 4.

1 Like
26

yes, campaign, act IV, start approaching Tyrael, crashes.
9FBDC830-45FF-4980-BE01-87A77A37C234 error code…

1 Like
27

Still happening 3 days later. No way to enter the sewers without being spit all the way out of the game to the start screen.

2E23BA1F-200B-4698-B6DD-D5D42A955A78

28

To all posters,

CM had replied on another thread. Please added information to that thread:

1 Like
29

UPDATE on Day 4 post-patch

Success! The game now appears to be working normally.

Steps taken:

  1. Complete uninstall of Diablo 3 from Windows Control panel
  2. Complete uninstall of Battle.net from Windows Control panel
  3. Full shutdown of rig (not a Restart) and then fresh boot up.
  4. Reinstalled Battle.net
  5. Reinstalled Diablo 3 (allowed a full install)
  6. Again did a full shutdown of rig (not a Restart) and then fresh boot up.
  7. Started Diablo 3, tested problem areas. Game working as intended.

Issues appear to be resolved with the fresh install.