dxdiag: https://pastebin.com/38t35eVK
dmp 1st: https://pastebin.com/hDW68HC5
dmp (after scf restore health, if this matters…): https://pastebin.com/Y3RqY9vC
I’ve been having these random freezes in game recently. It started maybe 2 or three weeks ago and it was happening somewhat… randomly. I was able to reproduce the freezing by quickly changing graphical settings, switching between directx versions, and quickly clicking through addons via options. It would randomly freeze during events like the community feast etc and zoning into instanced content as well as logging in from the character screen.
I went through all the common trouble shooting: deleting wtf/cache/interface folders, un installing and reinstalling battle net and wow, updating windows and gpu, rolling back gpu to a previous build, running diagnostics/malware and system maintenance, uninstalling Overwolf and all the programs giving my system errors in “Event Viewer” nothing worked.
I would like someone that can decipher those files more literately to tell me if there’s anything else I need to do or should look out for. It would be extremely helpful as I hope this post is to anyone else experiencing this issue.
Edit: nope… froze during dragon riding today. (No clipping) Ah well
Edit 2: reformated both ssd’s and did a clean OS install on its own ssd and reinstalled wow again. So far so good, still “freezes” on character login, so thats a blizzard thing- would be interesting to see blizz explain what that is exactly.
Edit 3: While dragon riding, camera and movement became un-responsive, while attempting to turn right via right clicking mouse, wow frooze and crashed. Somewhat new type of freeze for me. Different from the radom freezing or the crashes/DC loops that occur from clipping geometry will dragon riding (clipping geometry and accelerating geometry, while flying-dismounting causing crashes has been a bug in the game since flying in TBC btw). Not sure why I’m updating this anymore. There’s something seriously wrong with Blizzards coding.
1915075795594068823
5
RADAR_PRE_LEAK_64
Not available
0
Wow.exe
10.0.2.47213
10.0.19045.2.0.0
\?\C:\Users\david\AppData\Local\Temp\RDRE446.tmp\empty.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE456.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE457.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4C3.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4D3.tmp.txt
0
08af0b76-309a-4513-b058-995d109c1ac7
268435456
d5fec9ba106b29283a93b74a22554357
0
Also not sure if this has anything to do with it, but it’s the only only “warning” that occured that I can find… Even though it’s supposed to be a benign windows warning.
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user DESKTOP-AO8A5KH\david SID (S-1-5-21-2766957986-1457195905-2723898531-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1949_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
-----Account Unknown(S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681)—