Been reading through the forums and haven’t seen much notice about the Error #132 Crash, but seems many users are having some insane stutters when playing their game, so here I am putting my grain of salt.
I came back to WoW recently, just got a new rig and wanted to play DF, everything was going well when I was just playing with integrated graphics from a Ryzen 7700x, but then when I upgraded to a dedicated GPU (6950 XT) there was this strange stutter that went into a black screen for like 10 seconds and then back into the game.
This started to happen every single time when I logged into the game and started to play for 5min, any type of content in DF, including the WoD Timewalking dungeons atm, after one stutter, there will always be another one after 2-5min, but the second one crashes the game and pops up the usual crash window and closes the game completely.
I saw another user having this issue and the recommendations made on that post, did them all, reinstalled the game, deleted WTF folder, removed all addons, disabled Discord Overlay, and stopped all background tasks when playing DF, downgraded/updated Graphics Drivers, chipset, BIOS, disabled/enabled MPO, but still the error is there, no changes at all.
I would like to know if any of you guys have found a solution for this error and the crashes or if this is being fixed by the devs.
Not looking forward to update to Windows 11 because of usual AMD struggles atm, but hopefully there will be a fix soon.
Here are the logs that where asked in the other post I saw
https://pastebin.com/0gYX4Z6V - Crash
https://pastebin.com/KkvUiAiZ - DxDiag
MSinfo32 is way too big for it to be shared as a Pastebin link.
I’ve been getting this often , between yesterday (Jan 7th) and today (Jan 8th). I’m hoping this will get fixed Tuesday, but I’d also like to know what is causing it.
Your Dxdiag sadly shows nothing but Timeout detection and recoverys (TDR) errors these occur when the GPU does not respond to Windows on time or reports back an error has been reported by the GPU. The goal of this process is to ensure the PC doesn’t crash so the program is crashed.
As for sources of this error it will require some troubleshooting the 5 main sources are:
Driver issue.
third-party software conflict(Think overlays, overclocking software, streaming software or any directx software in general.)
Overheating GPU gets to a point it starts to bit-flip data becomes incorrect.
Unstable Power Delivery from either the power supply or motherboard.
Faulty hardware of the GPU itself.
Your recent Error 132 reports are directly related to corrupted memory. That can be due to an unstable memory speed, faulty stick or ram or unstable overclocking.
Given the number of issues found, in this case I would recommend consulting with our tech support team by placing a ticket Here.
NOTE: If the MSinfo doesn’t upload via our site we provide steps on how to make it smaller so our team can still look at it Here.
Iceberg Your issue appears to be from a different source. Related to “RTSSHooks64.dll” so either an unstable GPU overclock or the actual overclocking software itself is causing problems like MSI After Burner just running in the background may cause conflicts. Please try reverting any overclocking software, remove it from the system and then retest with the system’s startup items disabled following the steps Here.
You appear to be crashing from RivaTuner Statistics Server. Try disabling it and see if it resolves the crash. If it does, check if there are any program or driver updates that might help keep it stable.
Error 132 is a generic crash that can occur from any number of things. Each error 132 needs to be diagnosed separately, since they can be caused by virtually anything.
If you’re still experiencing crashes, post a thread of your own and it will be much easier to troubleshoot.
You and Kodiack are insanely amazing, getting rid of Afterburner and RTSS got the issue away, was getting sick of trying things.
MVP is nothing close as what you both are.
Thanks a lot!
I was having a similar problem but the error only came up upon closing the game. However it was because rivatuner wasnt running. Having riva run when i close wow has solved my problem.
