Error #132 constant crashes

Customer Support collects the crash files/error logs through the ticket system. I don’t think they analyze Windows system dumps, though (and as a volunteer, neither do I).

On the forum we mostly deal with the DxDiag and sometimes the MSInfo if the player is comfortable with providing it. You can upload your choice of reports to a public website like Pastebin.com or Controlc.com (individually please) and link them here. If you can’t post those URLs, just provide the hash codes at the end and we can type the rest. :slight_smile:

1 Like

As requested. Here are some of the crash text files. I’ve attached only the most recent ones, however there are plenty more

I can’t link to Pastebin directly due to being a “Level 0” account, so the hash codes are as follows

zgvTYDjG

KxEWWg0U

SnAFzrT9

kcaiFzBw

How about a DxDiag, too? The error files are just littered with access violations. Usually that’s related to trouble accessing the memory or a portion of a drive. But maybe the DxDiag, or even MSInfo, would provide more solid clues.

MSinfo wMpymMMQ

DXdiag GFiRL7sj

Got nuked by Pastebin. Try controlc.com.

controlC hash ac49f18d

Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:
P1: NVIDIA Broadcast.exe

:thinking: Have you tried turning this off? Perhaps it’s not playing well with sound channels in Classic. It’s also appearing in the MSInfo.

That should have been disabled since I exited the application. However the Details tab in Task Manager shows “NvBroadcast.Container.exe” which restarts when killed (thanks, Nvidia!)

I went ahead and removed the Nvidia Broadcast application as a precaution and re-ran the test with all other apps closed. I also updated my system BIOS while waiting and manually configured the audio tab to select my actual sound card instead of just “Default”

Interestingly, I was able to bounce around between the major cities without crashing

I then went ahead and reinstalled Nvidia Broadcast (using a “clean” install of the software, just in case)

I also dove into Windows Sound settings and disabled all sound output devices (including Nvidia Broadcast) except for my physical sound card

At time of writing I’ve been able to fly from one side of Outland to the other without issue. So I’m cautiously optimistic that has resolved it

For anyone else who reads this, tl;dr

  • Clean Reinstall Nvidia Broadcast

  • Force WoW to use your actual sound card, not Nvidia Broadcast

:crossed_fingers:

Thanks for reporting back.

1 Like

super interesting, not using nvidia broadcast but having issues. wondering if it could be the sound, by “Force WoW to use your actual sound card, not Nvidia Broadcast” would i just change setting in game to not default?(game sound output to my headset, sound channels high(64) and sound cache large 64mb)