On Thursday 12/1 was when my hell started, I got peppered with wow error #132s back to back. The #132 error is supposed to indicate a general hardware or software problem, but I cannot figure out what is going on. I’ve tried changing most every graphic setting, DX12 to DX11, back, this AA, that shader etc. Reinstalled wow, same errors.
Only thing that did seem to help for at least 2 days was fully disabling resampling. Im now back to where I started and it’s extremely frustrating, and I believe whatever issue has occured has also caused me to have a handful of BSOD occur (which yes, I know would point to a PC problem on my end, but this hasn’t happened with any other game on my PC)
At this point I just want some help if its possible.
In addition to reinstalling wow, ive fully uninstalled and reinstalled nvidia drivers (using DDU program in safe mode).
I stress tested my GPU using FurMark, cause I was also getting some loading screen burn/artifacting loading into the Dragon Isles.
I ran Windows Memory Diagnostic to test my ram, since I was having other programs on my PC crash, including Bnet, which would force wow to close.
I ran a disk check in cmd prompt to scan and repair corrupted files, and hopefully stop my BSOD (which so far, has worked, a small win)
I ultimately don’t know anything else I can do, so again I would really appreciate any help at this point, if I can provide anything else, let me know and thanks for reading.
Thank you for taking the time to reach out with these details as well as the DxDiag! The Windows Error Reporting section of your DxDiag shows a number of “LiveKernelEvent” errors with reference code 141:
These errors are also known as “TDR” errors (Timeout Detection and Recovery). TDR errors can cause a variety of problems not limited to a temporary system lockup, the game crashing, freezing, minimizing, or the screen going black since Windows loses communication with the graphics processor when it happens.
I can also see D3DDRED2 error entries in the Windows Errors. These errors most often indicate an issue with the video driver or the video card itself, but can also be caused by overheating components, faulty VRAM, insufficient power, or Windows corruption. This indicates that something deeper – possibly hardware-related – is causing the system’s instability, and sadly will fall outside of the scope of what we can diagnose or troubleshoot here. It may be best to contact a certified local computer technician to diagnose the system. Alternatively, NVIDIA or Microsoft’s Support may be able to pinpoint the issue using the Windows system or error logs.
I hope this info helps! Let us know if you have any questions going forward.