I keep getting this error after playing for a few hours. I have no idea what to do, and I am getting very frustrated. Can anyone help?
Process ID 8444
Thread ID 9168
Exception: Access_Violation
memory could not be read
1 Like
SAME!! I’m getting so angry. I completely uninstalled and deleted everything pertaining to battle.net application and WoW and reinstalled it still keeps happening repeatedly on my brand new gaming PC I just built and I’m ready to flip a table over it.
1 Like
What kind of graphics card do you have?
MSI GeForce 1660 Super. Never had any issues until this week
I have a Intel® UHD Graphics 600. Wonder what the problem is. It’s annoying being able to play for a while with no problem only to find myself crashing in a dungeon boss fight.
Do you notice when the crashing happens? For me it is seemingly most often in instances and battlegrounds
I’m having the same issues seemingly randomly. I’m never doing the same thing when it happens, had it happen just running around in open world and also in the middle of instances, fights, etc and then I load back in and I’m dead or no longer in the instance. Extremely frustrating. I even completely wiped my pc and put on a fresh windows install because it was also causing memory mangement blue screens during the scan and repair running in the battle.net app. As well as checking event viewer to make sure none of my pc components are erroring and nothing, just this game.
It’s especially frustrating that so many of the fixes posted online apparently don’t work either
Post dxdiag reports. No one can help troubleshoot without information.
Often, these are related to out of date drivers or out of date windows installs.
What is a dxdiag report?
15 seconds of Google…
Post a link to pastebin, we need the part after the /
Thanks. You’re right, I should have googled. I’m running a memory diagnostic on my PC, I’ll post do that next.
edit: What part exactly? I don’t see a “/” in any obvious place in this text file that is pretty large and full of a large amount of information.
1 Like
I’m seeing this pop up all over the forums. So I believe it might have something to do with the actual game rather then Individual PC’s.
2 Likes
Gosh I hope so. I was surprised to find my laptop could run WoW, I was so excited to be able to play again
You post the whole dxdiag to pastebin.
Then you post the link here, but since lots of people can’t post links due to the forum software, you post the part of the url after the /
We’d want the XXXXXXXX part.
Yep, I’m thinking this. I’ve one computer that still has Win 7 on it – been playing WoW fine til about a week ago. Now I get the 132 error. Have uninstalled and reinstalled; run Blizz repair and updated any driver I can think of that may not have been. I dunno. Guess cannot run WoW on Win 7 anymore. *Grumpy.
g1zzwze9
It didn’t get the whole report in the post - there should be cpu and os information before the gpu information, and crash information (maybe) after the power settings at the end.
That being said, the thing that jumped out at me was how old your sound card drivers are. Your via drivers are from 2012. If try looking for updates to those or testing if disabling then in windows gives more stability.
1 Like
Thanks much.
Maybe this is the other part:
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr_escrow.200102-1707)
Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: BIOS Date: 05/16/12 11:48:30 Ver: 04.06.05
Processor: Intel® Core™ i5-3570 CPU @ 3.40GHz (4 CPUs), ~3.4GHz
Memory: 8192MB RAM
Available OS Memory: 7898MB RAM
Page File: 4373MB used, 11418MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 64bit Unicode
DxDiag Notes
That’s the missing start, now if there was anything below the power settings, that would be helpful too.
Nope, when saving the dxdiag, there is no further text after the power info. ;o(
Thanks for your suggestion on the sound card driver. Will update that.
That’s actually good news - sort of - it means no crashes have been captures. Of course, it doesn’t help us troubleshoot either.