Error #132 after patch 10.0.5

I wanted to chime in here with some clarifications on the #132 crash error message. Because these threads can end up a jumbled mess of various issues that just happen to show that very generic error message and have folks thinking its all the same thing. (Mostly to expand on what Jambrix posted shortly after this thread started)

132 is a generic message. usually some sort of driver conflict, software conflict, client corruption or potential bug with the game.

With the recent patch we saw a major increase in the number of 132 crash reports and the causes of that are being investigated.

Now, 2 major trends have appeared in these crash reports.

  1. Supported AMD systems with severely outdated OS/GPU Drivers.
  2. Unsupported AMD systems.

(There was also a major crash issue with Macs but that was not the 132 crash, that was a different crash code)

Those are the bulk of reported crashes by a very large margin.

What this means is if your situation does not match either of those two situations then you have something likely specific to you happening and the best course of action would be to submit a direct ticket with system files so our technical staff can begin troubleshooting with you directly. (Be aware response time is currently about 48 hours to technical tickets)

Now as for the 2 situations I mentioned above.

If your system meets all requirements for Dragonflight, then updating your OS and drivers should solve the issue. You may also need to disable/remove 3rd party software that interacts with the game client (profilers, overlays, performance enhancers etc…) but the issue is typically resolvable for you through troubleshooting.

If your system does not meet minimum requirements for dragonflight then you won’t likely have workable drivers you can update to because AMD no longer makes drivers for your hardware. This means that the game may never be playable for you again.

Now as I said, the developers are aware of the situation and are investigating the causes. It is possible there is a fix they can implement that would make the game playable again on unsupported hardware.

BUT (and this is important) that does not make your hardware supported again. Any future patch to the game or even a change/update to Windows can break compatibility again and permanently.

The only long term solution is to upgrade or replace the system so that it meets at least the minimum requirements if not the recommended specs for the game. (and keep in mind that system requirements do change typically with new expansions or as Windows changes or as support for specific hardware changes by the makers of that hardware.)

As the game continues development to add new content, new features, and compatibility for new hardware and systems, older systems will become unsupported. The life cycle of a gaming pc is typically 2 years though we try to remain compatible with older systems for as long as possible.

Now I have seen reports that some folks with the 132 crash are able to get around the issues by changing which directx version they are using with the game (system>graphics options) If you can switch from Directx 12 to Directx11 or Directx11 Legacy, you might be able to stop the crashing but this appears to be hit or miss at the moment.

We of course are leaving this thread open and the investigation is ongoing for potential solutions but there is no ETA or guarantee that a solution will be found for unsupported systems. I can only say that it is being investigated.

4 Likes