It has resurfaced, somehow. I have no idea why, nor how to get rid of it. I have tried everything that has been suggested-to-death before, and none of it worked permanently.
Here is the pastebin to my latest error file: https://pastebin.com/BebwBT9f
The report shows a general access violation error. Perhaps a security setting is too high on Windows Defender or anything else you use for security.
Hi. Theronitus here. Illidood is my main for the foreseeable future. Anyways…
As per Btq’s suggestion, I found and altered Windows 11’s handling of virtual memory. Set it to 24GB (I have 16GB physical memory) so it should have more “room” now. I remember doing this for Windows 10, but I guess the OS upgrade reset the page file settings.
Elocin, I checked as many settings as I could in Windows Defender (it is all I use nowadays). None are set too high. WoW and the launcher both have exceptions.
Windows Security → Virus & threat protection → Virus & threat protection settings → Manage settings → Cloud-delivered protection.
Beyond that, we’re not going to know what’s blocking installs of software on your computer. It’s not a symptom of the Bnet launcher or game client, so you may need to take up with Microsoft Support.
Alright then.
In any case, it’s so far so good over here. I don’t want to prematurely celebrate just yet though, but so far, the game has remained stable after configuring the Pagefile (virtual memory) and allowing exceptions for the game through my firewall and AV.
No go. I recently reinstalled and it crashed after 3 minutes in. This is ridiculous. Nothing has changed, so WTF! Getting really tired of this crap.
Elocin, I’m at a loss for what to do next. I’ve tried EVERYTHING, and the game still crashes after a few minutes. On my system that can support intensive games like Elden Ring, I’m surprised that WoW is crashing again.
I recently reinstalled the game on a different SSD only for it to crash within 3 minutes of playing. On another attempt, it crashed while in the graphics settings menu - I hadn’t even started playing then!
There is the latest error log. Have at it! I’m becoming extremely frustrated with this nonsense!
Unfortunately, it’s just a general access violation in that report. Check your error reporting in the MSInfo AFTER exporting the report to a text file.
Pastebin says the file is too large for a free user. I don’t know how to paste so much text here that won’t take up an entire page or three. Update: However…if this helps, here are the latest errors from the msinfo file that pertain to WoW
17/03/2022 2:51 AM Application Error Faulting application name: Wow.exe, version: 9.2.0.42698, time stamp: 0x622aab93 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process ID: 0xa30 Faulting application start time: 0x01d839a97daa284f Faulting application path: D:\World of Warcraft_retail_\Wow.exe Faulting module path: unknown Report ID: 398e89be-053b-4b09-ae5d-5db73076a3a9 Faulting package full name: Faulting package-relative application ID:
17/03/2022 1:31 AM Application Error Faulting application name: Wow.exe, version: 9.2.0.42698, time stamp: 0x622aab93 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process ID: 0x1328 Faulting application start time: 0x01d8399e73455d8a Faulting application path: D:\World of Warcraft_retail_\Wow.exe Faulting module path: unknown Report ID: 0bc0238d-9bc7-40b6-a197-bd66ca17300a Faulting package full name: Faulting package-relative application ID:
17/03/2022 1:02 AM Application Error Faulting application name: Wow.exe, version: 9.2.0.42698, time stamp: 0x622aab93 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process ID: 0xaec Faulting application start time: 0x01d8399a476c40ff Faulting application path: D:\World of Warcraft_retail_\Wow.exe Faulting module path: unknown Report ID: ab0753d9-8a34-4516-a4ea-aead8e22f383 Faulting package full name: Faulting package-relative application ID:
Have at it. Let me know if more is needed.
What format is the D drive? And is it a partition of the main drive?
Blizz games only work on NTFS and sometimes partitions can cause issues.
Does the reliability history say anything?
Yes D drive is NTFS. As for reliability history, it has 3 critical events: all “stopped working” ones, all pertaining to WoW.exe. One of them reads as follows:
Description
Faulting Application Path: D:\World of Warcraft_retail_\Wow.exeProblem signature
Problem Event Name: BEX64
Application Name: Wow.exe
Application Version: 9.2.0.42698
Application Timestamp: 622aab93
Fault Module Name: StackHash_392d
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_84_FROM_unknown+0x0000000000000000
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 10.0.22000.2.0.0.256.48
Locale ID: 3081
Additional Information 1: 392d
Additional Information 2: 392d28d2a1ea92518b7b2643fc3dd49b
Additional Information 3: b302
Additional Information 4: b302d3714bc437d462e3f0aea5004f74Extra information about the problem
Bucket ID: b9927166ee541ed12daf318cf69cc58e (2138982829526926734)
I ran MemTest86 a few hours ago and it recently finished. All was green, no errors detected.
Yeah, general errors aren’t super helpful. I’ve used MemTest86 quite a bit, but it has failed to detect bad memory for me before. Most of your errors are saying memory problem. Did you have a DxDiag and MSInfo to share?
Not at the moment, no. Sorry.
Although I find it interesting that as soon as I add Agent.exe (there are two of them) to my AV’s exceptions list, the crashes have thus far not occurred. Thoughts, Elocin?
That’s one of the recommended steps from Blizzard, and I figured you did that already, lol. Sounds like your AV is blocking access 
I hadn’t before. But I have now. I’m using stock-standard Windows Defender btw.
So far, I’ve been through a quest in ZM (restoring the oracle person/construct) and not a single negative incident. I remain cautiously optimistic. 
Thanks for your help Elocin.
hopefully it stays that way
1 Like
Elocin, sorry to bother you, but it happened again.
Curious that it did so after I downloaded the Zygor addon 
Update: Happened again. It wasn’t Zygor. Also both instances of Agent.exe are still in Windows Defender’s exception list.
Update 2: And again with no addons active.
Update 3: Replacing Windows Defender with Malwarebytes might be the magic bullet I needed. The later program found some suspicious files that the former did not, and got rid of them. So I rebooted, added exceptions for wow-related files to MB, and played. I stayed on for more than 5 minutes without incident. Yet still I remain cautious, but this development has me curious 
1 Like
Not instances per-se. There are two Agent.exe files: one in the Agent folder, the other in the Agent.7661 foldier.
But it doesn’t matter anymore. The game inexplicably crashed on me AGAIN! No error, no log, no nothing! It just froze and then closed itself.
With that in mind, screw this. I’m done! 
Btq, what are you talking about? Share point? I have no such software installed on my PC. Not this share point, or any other backup software.
One what? One Agent.exe file? If that’s the case then why are there two??
This is my latest DxDiag. WoW has since been uninstalled (for the moment?).
And these are the important pieces of my system.
Operating System: Windows 11 Pro
Motherboard: MSI H370 Gaming Plus (MS-7B22)
Processor: Intel Core i7 8700 @ 3.20GHz 6 core
RAM: 16GB DDR4 (2x8GB)
Graphics Card: Nvidia GeForce GTX 1080
Resolution: 2560x1440 @ 144hz
Pagefile Space: 24GB (1.5x my RAM)
1 Like
Giving “what” a second email address?
I don’t let battle.net start up with Windows.
Those other 2 games are probably elden ring and risk of rain 2. If I push them too far, they crash. But it’s nothing like what WoW does!!