Constant Error 132 after minutes of playing

Support Technical Support
1

Hello everyone,

Since the official launch of Shadowlands started, I encounter constant 132 Error crashes. I tried the following but nothing worked :

  • Disable all addons
  • Uninstall all addons
  • Scan and repair WoW
  • Re-install WoW
  • Re-install Windows
  • SFC Disk Scan
  • Memory scans and stress test with MemTest86
  • Disabled Xbox/Game DVR Windows feature

I want to mention that currently I am in a fresh Windows install with close to none programs and drivers installed. Still getting the error.

The really odd thing is that with the with the old WoW installation files and with all addons enabled WoW don’t crash on my laptop that is worse spec wise. So it isn’t caused by any addons. I have managed to collect 9 crash error dump files since I uninstalled the WoW after and the Error folder got deleted :frowning:

Uploaded in pastebin :
DxDiag : https://pastebin.com/XD1PnRgm
MSInfo : https://pastebin.com/XH64M0Mj
Recent Crash from the reliability Windows reporter : https://ibb.co/y5BYywY (image)

Something I haven’t tried yet is turn of DEP (Data Execution Prevention) for WoW. I cannot see why that could be an issue suddenly but will check when I will be able to login on Draenor…

1 Like
2

Finally someone posted about this!
Launch night was flawless for me, but yesterday morning these crashes started happening to me too. I had them in the pre-patch, but new ram seemed to have fixed it.
Done the following:

  • Scan and repair WoW
  • Delete WTF, Cache, Interface folders
  • Reinstall WoW (on two different drives)
  • SFC disk scan
  • Run WoW in admin
  • Change from DirectX 12 to DirectX11. Worked for about 2 hours then the crashes started happening again.

DxDiag: https://pastebin.com/d9eq6tvE
MSInfo: https://pastebin.com/kTamizbD
Screenshot of crash: Error message

This started after the small download the launcher started Tuesday morning (24/11/2020). Was fine until then.

1 Like
3

The error stopped appearing for me due to a server hotfix prolly cause nothing changed on my end.

4

Still happening to me… :frowning: