ACCESS_VIOLATION - The memory could not be "read"

Support Technical Support
61

Have done everything in this forum apart from turning off E-Cores, had a look at the Task manager affinity thing, wouldnt have a clue which ones to turn on or off, still crashing although less frequent but still around 5 times a session, very annoying, close to quitting again, isn’t ideal considering i’ve just come back, thanks for the help, appreciate all the efforts

62

So, I actually ran my logs through grok and it told me my crashes had to do with my Turnleft keybind. I switched my A+D to strafe left and right and so far am fine. I recommend you guys running your crash logs through an AI and ask it for solutions. It helped me.

63

hehe thanks i just did the same with my log. grok told me:

Based on the log, here are the most probable reasons for the crash:

  1. DirectX 12 Issue:

  • The crash in D3D12Core.dll strongly suggests a problem with DirectX 12 rendering. This could be due to:

    • A bug in WoW’s DirectX 12 implementation, especially in The War Within (patch 11.1.0), which has been reported to cause crashes in certain zones.

    • An incompatibility between the NVIDIA driver (32.0.0015.7270) and WoW’s rendering pipeline.

    • Corruption in the DirectX 12 shader cache or game files.

  • Edit: Can also add that the AI(Grok) also added that i’ve been using 7200mhz XMP profile 1. In some ways higher frequencys could interfere or “affect” the async resource creation setting in some ways that could lead to crashing, even if my or ur system works just fine in other games, programs and apps with higher ram/dram frequencys doesnt mean that every single game will. So lowering the XMP profile closer to 6000mhz cuz that seems to be the sweet spot for 14900k cpu. So atm im sitting at 6400mhz which is the lowest xmp profile i can get. Hope it works and if not then i literally have no idea… x_ x
65

Didnt it recommend trying going with directx 11?

66

Yes it did. It recommended me to try DX11 but at the same time told me that people has reported that DX11 can be even more unstable and some graphical settings wont be available in DX11 that are available in DX12 and it also told me to try use DDU and clean install new nvidia drivers and lower my latency speed on my ram

67

UPDATE. I have as of today gone 1 week without crashing with async resource creation on after i lowered my xmp profile. idk if that helped or not and cannot “test” it because i have no idea how to trigger the crash. BUT If i crash any time soon in the future i will let u know but as of now so far so good.

68

I’m not sure what changed, but the last time I had this issue was two weeks ago when I posted here. Since then, it hasn’t happened again—even though I didn’t change any settings or update any drivers. So I’m not sure why, but I’m just glad the constant crashes have stopped.

69

Will try it again turn it on and will also let know here results

70

yea turned it on and crashed in dornogal after 1h playing . Im on xmp 1 already so this oen not helping me

71

damn… yeah i crashed aswell today. I guess we need to have it off lmao and it sucks… I agree with what u have said previously, that the game runs better with it on. idk what we can do to fix it(other than trning that setting off). We also almost have the same system with i9 14900k and rtx 4090 etc. we should be able to play the game without problems and it’s so frustrating. Is our only option left to just buy an AMD system instead? :joy:

72

Some deep reseearch from ai :stuck_out_tongue:

Recurring WoW DX12 Crash with “Async Resource Creation” Enabled

Issue Overview

Players of World of Warcraft Retail (build 11.1.5.60568) have encountered frequent client crashes (Error #132 Access Violations) when DirectX 12 mode is used with “Async Resource Creation” turned on. The crash typically produces an error like: “ACCESS_VIOLATION – The instruction at 0x00007FFB61A74EA8 referenced memory at 0x00000029000004C9. The memory could not be read.” These crashes occur in any location (even idle in cities like Dornogal) and cease entirely if Async Resource Creation is disabled, indicating a bug related to this DX12 feature.

Blizzard/NVIDIA Acknowledgment & Causes

While there hasn’t been a very direct official blue-post explicitly naming this bug, both Blizzard support and the community have identified likely causes:

  • NVIDIA Driver Conflict: Many players report the issue began after installing recent NVIDIA Game Ready drivers (e.g. version 576.28, released around Apr 27–30, 2025). A forum MVP noted that “a recent nVidia driver is causing issues” with WoW’s DX12 renderingus.forums.blizzard.com. In fact, some players pinpointed March 7, 2025 as the day crashes started, suggesting a driver update rather than a WoW patch triggered itus.forums.blizzard.com.
  • Outdated DX12 Libraries in WoW: One technically savvy player discovered that WoW’s bundled DirectX 12 runtime DLLs (d3d12.dll, D3D12Core.dll) were “very ancient” and possibly incompatible with newer NVIDIA driversus.forums.blizzard.comus.forums.blizzard.com. By manually replacing these files with up-to-date versions from Microsoft, that player eliminated the crashes entirelyus.forums.blizzard.comus.forums.blizzard.com. They concluded “NVIDIA’s latest drivers broke something in older versions of these DLLs… The WoW client is making requests that aren’t there (in the old libraries) with NVIDIA’s drivers as of the past two weeks.” us.forums.blizzard.com In short, the new driver expects a DX12 feature or call that WoW’s old D3D12 libraries don’t support, causing an Access Violation. This is a conflict Blizzard will likely need to address by updating those libraries or code.
  • Blizzard Awareness: Blizzard hasn’t yet published patch notes or official bug-trackers calling out “Async Resource Creation” crashes by name. Support responses initially focused on other factors (such as the known Intel 13th/14th-gen CPU stability bug). In one case, a support agent pointed to the Intel issue and “drivers” generallyus.forums.blizzard.com, but players quickly noted this affects AMD systems as well and is not the same CPU-specific bugeu.forums.blizzard.com. The sheer volume of forum posts suggests Blizzard is aware internally. A community manager encouraged submitting in-game bug reports with crash logs so the dev team can investigateeu.forums.blizzard.com. So while Blizzard hasn’t publicly “acknowledged” this exact bug in a Blue Post, they are being made aware through support channels and forum reports. Players have explicitly urged Blizzard to work with NVIDIA to fix it, instead of blaming only user hardwareeu.forums.blizzard.com.

Widespread Player Reports

This crash issue is widespread, as evidenced by numerous forum threads and community discussions:

  • On Blizzard’s official forums (EU & US), dozens of threads popped up once Patch 11.1.x went live. One user noted “This has been going on since patch day. Dozens of threads, hundreds of people reporting it… No mention on the known bugs [list].” us.forums.blizzard.com. The problem does not discriminate by system – players with high-end PCs (e.g. Core i9-13900K/RTX 4090) and others on AMD CPUs have all experienced the same Access Violation in D3D12Core.dll. Crucially, they report no issues in other DX12 games, highlighting that the fault lies with WoW’s engine or its interaction with driverseu.forums.blizzard.comeu.forums.blizzard.com.
  • Reddit and other communities (e.g. /r/wow and technical subforums) echo these reports. Players there confirm that after the 11.1.5 update (The War Within patch) their game became “unplayable” until they discovered the Async Resource Creation toggle. Multiple Reddit users found that disabling Async Resource Creation immediately stopped the crashes, calling it a temporary fix until an official patch arrives. Some also mentioned turning off “Advanced Work Submit” or other Optional GPU Features in Graphics settings alongside iteu.forums.blizzard.com.
  • Example Reports:
    • “I’ve tried every single fix… none have worked for me except for disabling ‘Async Resource Creation’ in the graphics options. My problem with this is it literally halves my FPS, but at least it stops the error.” us.forums.blizzard.com – (User on US Tech Support forum)
    • “After patch 11.1, I also had many crashes. I see many gamers have this problem recently, and believe our PCs are in good condition.” – (User comment acknowledging it’s a new bug, not a hardware failure)us.forums.blizzard.com
    • “Ever since the new patch dropped I can barely play… reinstalled Windows, WoW, etc. The issue persists. It’s not add-ons. People in the US forums also have this problem.” eu.forums.blizzard.com – (Users exchanging frustration that it clearly is a game/driver bug, not on their end.)
    • “This used to only happen when I was tabbed out while loading, but now it also happens while tabbed in… That makes 30+ crashes already.” eu.forums.blizzard.com【5†L2169-L2177} – (Players experiencing crashes in various scenarios, indicating how random and frequent it became).

In short, the community widely recognizes Async Resource Creation under DX12 as the culprit. Even those initially unaware eventually found the forum threads or tips pointing to this setting. One person mentions “with 11.0 there were new graphics options added to the game… I turned them all off and it fixed my client from crashing”, and another replied “All I turn off is ‘Async Resource Creation’ and the game seems stabilized now. Thank you so much.” us.forums.blizzard.comus.forums.blizzard.com. This shows that among the new “Optional GPU Features,” Async Resource Creation is the primary instability trigger.

Workarounds and Temporary Fixes

Until Blizzard or NVIDIA issues an official fix, players have been using several workarounds to mitigate the crashing. These are the recommended steps currently circulating in tech support forums and Reddit:

  • Disable Async Resource Creation: This is the single most effective solution. In WoW’s Graphics settings (under “Advanced” or a “Compatibility” sub-section at the bottom), uncheck “Async Resource Creation.” Virtually all reports confirm the game stops crashing once this is offeu.forums.blizzard.comeu.forums.blizzard.com. The downside is reduced performance for some – users report lower FPS and less smooth asset streaming when this feature (which asynchronously loads textures/models) is disabled. For example, one raider noted their framerate was cut roughly in half without itus.forums.blizzard.com. Still, it’s preferable to crashing every 5–10 minutes.
  • Turn Off Other “Optional GPU Features”: In the same menu, there are other related toggles (added in recent patches) such as Multithreaded Rendering, Advanced Combat Logging, Graphics Card Buffering, Frame Rate Smoothing, etc. One user recommended turning all of these off to be safeus.forums.blizzard.com. However, many found that Async Resource Creation was the main offender – they re-enabled the others one by one and remained stableus.forums.blizzard.com. Another setting, “Advanced Work Submit,” might be listed (or is similar to “Multithreaded Submission”) – players have tried disabling it as welleu.forums.blizzard.com. If you’re troubleshooting, you can start with everything off, then add back features except Async.
  • Roll Back NVIDIA Drivers: For those with NVIDIA GPUs, reverting to an older driver has proven helpful. Players have specifically cited driver v572.60 (late Feb 2025) or any 572.xx series as stableeu.forums.blizzard.com. Using a tool like DDU to fully uninstall the current driver and installing the older version stopped the crashes for some users over many days of testingeu.forums.blizzard.com. This supports the theory that something changed in the 576.xx drivers. (Note: If you try this, you may want to also block Windows Update from pushing a newer driver, until you’re ready to update again.)
  • Use DirectX 11 Mode: If all else fails (or you desperately need the performance from Async but can’t use it on DX12), you can switch WoW’s Graphics API to DirectX 11 in the System > Advanced settings. DX11 mode has considerably lower performance in WoW (especially in newer expansions/zones optimized for DX12), but it is far more stable in this scenarious.forums.blizzard.comus.forums.blizzard.com. Several players resorted to DX11 temporarily – one noted it “seemed to mostly solve it” aside from the performance hitus.forums.blizzard.com. This is truly a last resort workaround, but it guarantees no D3D12Core.dll crashes since the game won’t be using DX12 at all.
  • Miscellaneous Tweaks: A few other tweaks were reported with mixed success:
    • Disable Fullscreen Optimizations for WoW (via Windows compatibility settings on WoW.exe) – combined with Async off, one person had no crasheseu.forums.blizzard.comeu.forums.blizzard.com. It’s unclear if this actually helps or if Async was the real fix.
    • Limit Frame Rate (“Target FPS”) – ensure any frame rate limiters aren’t set too aggressivelyeu.forums.blizzard.com. And verify NVIDIA’s Max Background/Foreground FPS (if you use GeForce Experience) isn’t mistakenly capping your game in the foregroundus.forums.blizzard.com (this was a separate known issue).
    • BIOS/CPU Settings – Some with high-end Intel CPUs tried disabling Intel SpeedStep/Boost or ensuring their BIOS was up-to-date, thinking the CPU bug might be at faulteu.forums.blizzard.com. In general, that Intel issue (where certain 13th/14th-gen chips overdrew power and caused memory errors) has been mitigated by BIOS updates, and many affected WoW players were not on those CPUs or had already applied fixesus.forums.blizzard.comeu.forums.blizzard.com. So this isn’t the primary cause here. Still, running your CPU/GPU at stock clocks (no overclock) is wise while troubleshooting. Likewise, a few folks found disabling XMP (high-frequency RAM profiles) helped stability in WoWeu.forums.blizzard.com – this suggests WoW became very sensitive to memory errors with the new patch. It may not be necessary for everyone, but if you’re still crashing, try reverting RAM to default JEDEC speeds to rule out borderline RAM stability issues exacerbated by WoW’s behavior.
    • Repair or Reinstall WoW: Some players went to extreme lengths like fresh reinstallations of the game clienteu.forums.blizzard.comeu.forums.blizzard.com. In general, this has not solved the Async crash for most (because the issue is in the game code/engine, not a corrupt file on your PC). One user thought a clean reinstall helped, only to crash again shortly aftereu.forums.blizzard.com. So, reinstalling is usually not necessary – the problem will return unless you change one of the above variables.
  • Manual DX12 DLL Update (Advanced): As mentioned, one user (Aalliyah) directly replaced Blizzard’s d3d12.dll and D3D12Core.dll in the WoW directory with the latest versions from Microsoft’s official sourcesus.forums.blizzard.comus.forums.blizzard.com. This is a non-standard fix and not officially recommended (it could potentially cause other issues if done incorrectly). If you attempt it, make sure to use legitimate, signed DLLs (e.g. from the DirectX Developer Github or Windows SDK) us.forums.blizzard.com. After doing this, that user reported “Not a single crash” over many hoursus.forums.blizzard.com. Essentially, they performed on their own what we hope Blizzard will do in a patch. This confirms the root cause: WoW was running against outdated DirectX12 interfaces. We include this for completeness, but again, the safer approach for most users is simply disabling the Async feature until an official fix comes.

Expected Resolution and Outlook

Will Blizzard or NVIDIA fix this? All signs point to yes, a fix is likely coming in the near future, though no exact ETA has been given. Here’s what we know and expect:

  • Blizzard Development: The WoW team has likely gathered enough crash reports by now to identify the issue. The fact that these new DX12 “optional” features were exposed to users in recent patchesus.forums.blizzard.com suggests Blizzard anticipated some problems and wanted an easy way for players to toggle them off. They’ve done this before when introducing DX12 or Ray Tracing – new graphics APIs can have teething issues. We anticipate a client-side patch (either a hotfix or the next minor patch) will address this. This could involve updating the packaged DirectX12 libraries or adjusting how Async Resource Creation is implemented so it doesn’t call invalid GPU instructions. There is precedent: previously, each WoW expansion’s new graphics features sometimes caused issues that later got resolved either by Blizzard’s code fixes or by driver updateseu.forums.blizzard.com. Given the scale of this bug, Blizzard “has to fix something on their side”, as one frustrated player put iteu.forums.blizzard.com, and it’s likely a high priority now.
  • NVIDIA’s Involvement: NVIDIA is also aware of widespread issues in recent drivers. Their 576.28 driver release notes mention fixes for various game crashes on RTX 50-series cards, and players in NVIDIA’s own forums have reported WoW-specific problems in the 576.xx feedback threadnvidia.com. It’s possible NVIDIA might make a driver-side change to improve compatibility with WoW’s current DX12 calls. However, since Async Resource Creation is a WoW engine feature, a game patch might be the more direct solution. Still, keep an eye on NVIDIA driver changelogs; they sometimes list game-specific fixes. As of early May 2025, no driver release notes explicitly mention World of Warcraft, but user reports indicate NVIDIA has acknowledged issues like black screens and crashes on the new RTX 5000 series which could be relatedreddit.com. For example, rolling back to January 2025 drivers fixed black-screen crashes for some, implying the newer drivers had multiple regressionsreddit.com. We might see a 576.40+ or 577.xx driver with stability improvements that indirectly help WoW.
  • Community Pressure: The community is certainly making noise. Posts on Blizzard’s forums continue to pile up, with users explicitly asking “how many people need to be affected before it becomes a priority for Blizzard to fix?”us.forums.blizzard.com. This pressure usually ensures the issue isn’t ignored. Also, gaming news sites and fan sites have started to take note – for instance, some have compiled “Patch 11.1.5 known bugs” lists that include the DX12 crashes and black screen issues as a top concern. Blizzard has already rolled out a few server-side hotfixes for other 11.1.5 problems, so a client fix for this crash could drop in an upcoming weekly reset or minor patch.

In summary: This Async Resource Creation crash is a known problem among players, and while Blizzard hasn’t published a formal acknowledgment at the time of writing, both the developer team and NVIDIA are very likely aware. The safest course for players right now is to keep Async turned off (or use DX11) to play stably. Monitor official patch/hotfix notes and NVIDIA driver updates over the next few weeks. The expectation is that an update (either WoW 11.1.6/11.2 or a new NVIDIA driver) will restore stability in DX12 with Async Resource Creation enabled, allowing players to enjoy the performance benefits again without crashes. Given the frustration in the community (even affecting high-end raiders and M+ players), we anticipate this issue “will be sorted out ASAP” through a collaboration between Blizzard and NVIDIAeu.forums.blizzard.com. Until then, the community-shared workarounds are the best path to keep Azeroth stable on your system.

Sources

1 Like
73

that pretty much confirms it then right? if wow uses outdated DX12 files as it states here,: “Outdated DX12 Libraries in WoW: One technically savvy player discovered that WoW’s bundled DirectX 12 runtime DLLs (d3d12.dll, D3D12Core.dll) were “very ancient” and possibly incompatible with newer NVIDIA drivers” if thats true all we can do is just wait for blizzard to update their dx12 game files and for nvidia to get it together and release stable drivers

74

Yea but so far their only official response i saw was them blaming intel 13/14 gen cpus

1 Like
75

Have “INT_DIVIDE_BY_ZERO” error after today update (60822) after login to char everytime. Cant login at all.
13900k

76

Same here! Any updates from Blizzard? Unfortunately, it feels like they have no interest in solving the problem.

77

aaaaand im crashing again even with async resources disabled:) weeks of no crashes and suddenly 3-4 a day even when relogging or afk

78

i installed armory crate 2 days ago will test if it was a problem: Meanwhile some ai research :stuck_out_tongue:

World of Warcraft players have reported that ASUS’s Armoury Crate software (and its related services like Aura Sync) can conflict with the game, resulting in frequent crashes or “memory could not be read” errors. While there’s no official Blizzard support article naming Armoury Crate specifically, numerous forum posts and user reports – including from Blizzard’s own Technical Support forum – suggest a link. In essence, Armoury Crate’s background processes (for RGB lighting, device monitoring, etc.) have been implicated in causing memory access violations or other instability in WoW. Many users found that disabling or uninstalling Armoury Crate immediately stopped these crashesreddit.comus.forums.blizzard.com. Below, we detail known issues, user experiences, and recommended workarounds based on available documentation.

Known Issues (Armoury Crate & WoW Conflicts)

  • Blizzard Forum Findings: Blizzard MVPs and support-oriented users have pointed out that third-party peripheral software like ASUS Armoury Crate can destabilize games in unexpected ways. In one WoW forum thread about access violation errors, a respondent asked if the player was running Armoury Crate or ASUS Aura, noting “Those can be unstable and lead to problems in what seem to be unrelated ways. We’ve seen it with Asus, Razer, Corsair – [their] peripheral software is just unstable enough to make the whole thing unstable” us.forums.blizzard.com. This indicates that conflicts between such software and WoW are a known concern in the community.
  • Aura Sync (RGB Lighting) Conflicts: Armoury Crate’s Aura Sync lighting service has specifically been called out. A Blizzard support agent observed error logs and saw ASUS Aura components crashing, remarking “I see you’re using AURA lighting and I’ve seen [it] cause problems with Overwatch, so it might be happening here, too” us.forums.blizzard.com. In that case the WoW client was erroring out with a generic error #132, and the only anomalies in the diagnostic were Armoury Crate/Aura crashes and a USB issue. The support suggested disabling Aura effects to test if it stops the crashingus.forums.blizzard.comus.forums.blizzard.com. This implies Aura Sync can interfere with games at a low level (possibly due to overlay, driver hooks or RGB memory mapping).
  • Performance and Stability Issues: Beyond outright crashes, Armoury Crate has been linked to poor performance or freezing in WoW. Another Blizzard forum post noted that an ASUS “NoiseCancelingEngine.exe” (part of Armoury Crate’s tools) was running and “often the culprit for frame loss and delays in WoW and other Blizzard titles” us.forums.blizzard.com. Likewise, on ASUS ROG forums and other communities, users have blamed Armoury Crate for causing system instability (freezes, black screens, even BSODs) during gamingreddit.comrog-forum.asus.com. These issues span multiple games, but the pattern holds: Armoury Crate’s background services can conflict with resource-intensive applications like games. In the context of WoW, this may manifest as the notorious memory could not be read error (a Windows access violation).
  • Crash Log Clues: Some players have dug into Windows Event Viewer or WoW crash logs and found Armoury Crate components mentioned around the time of the crash. For example, one user who experienced multi-second freezes in WoW discovered faulting module errors for ArmouryCrate’s “GridPlugin.dll” (part of the Aura/lighting service) with exception code 0xc0000005 (access violation) coinciding with the freezesus.forums.blizzard.com. The error log showed the crash path in C:\Program Files\ASUS\ARMOURY CRATE Lite Service\ArmouryCrate.Service.exe and its plugin DLLus.forums.blizzard.com. Another error signature that has appeared in DxDiag/MSInfo reports is asus_framework.exe (an Armoury Crate process) throwing a BEX error (buffer overflow), indicating a memory access faultus.forums.blizzard.com. In short, WoW crash diagnostics have on occasion flagged Armoury Crate processes, reinforcing the connection.

User Reports and Evidence

Numerous first-hand reports across forums and social media back up the Armoury Crate–WoW conflict hypothesis:

  • Reddit Community Feedback: In an ASUS ROG subreddit discussion, a user noted they began seeing random “Out of memory” errors in games (even WoW Classic) after an Armoury Crate update. Other commenters immediately pinned the blame on the Aura Lighting service, advising that “It’s the Aura Lighting. It can be uninstalled without removing Armoury Crate if you need [it] for something else” reddit.com. In that case, removing the Aura Sync component resolved the errors. Another Reddit user confirmed, “I had the same problem. Completely uninstalling Armoury Crate and installing G-Helper solved the issue,” referring to a third-party utility (“G-Helper”) as a replacement. Likewise, a thread titled “Armoury Crate and WoW… NOT A MATCH!” had the original poster follow advice to remove Armoury Crate – after which “WoW is working fine again” with no more crashesreddit.com. These anecdotes illustrate a clear pattern reported by players: disabling Armoury Crate stops WoW from crashing.
  • Blizzard Forum Reports: Similar stories appear on Blizzard’s official forums. One player struggling to even launch World of Warcraft eventually discovered Armoury Crate was the culprit. “I have an ASUS mobo and apparently I installed ASUS Armory Crate at some point. Seen it in my Task Manager and when I closed it, WoW fired right up,” they reportedus.forums.blizzard.com. In other words, the game wouldn’t even start until the Armoury Crate background process was killed. Other forum participants have chimed in that simply exiting or uninstalling Armoury Crate immediately ended their error#132 “memory could not be read” crashes in WoW (in cases where all other typical fixes – drivers, addons, etc. – had failed).
  • Broader Context: Outside of WoW, many ASUS users have documented similar problems in different games. For instance, a Microsoft Flight Simulator player who suffered constant CTDs (Crash to Desktop errors) – often with “memory could not be read” messages – finally solved it by purging “ASUS bloatware.” They uninstalled ASUS Armoury Crate, ASUS Aura, ASUS Fan Control, ASUS services, and some old drivers, after which the crashes stoppedforums.flightsimulator.comforums.flightsimulator.com. This lends credence to the idea that Armoury Crate (or its drivers) can cause memory access violations across various applications. While not Blizzard-specific, it underscores that the combination of Armoury Crate plus modern games can be problematic, and WoW is no exception.

Possible Fixes and Workarounds

If you suspect Armoury Crate is behind your WoW crashes, the community and support insights suggest a few actionable remedies:

  1. Uninstall Armoury Crate Completely: The most robust solution is to fully remove Armoury Crate from your system. ASUS provides an official Armoury Crate Uninstall Tool to ensure all components are cleaned up. Many users report that once Armoury Crate was gone, WoW stopped crashingreddit.com. (If you need certain functionalities back, consider alternatives like “G-Helper,” a lightweight fan/RGB control utility, or install only specific ASUS tools you actually use.)
  2. Disable Aura Sync / Lighting Service: If you prefer to keep Armoury Crate for other features, try disabling the Aura Sync (lighting) component. The Aura service is a known troublemaker for WoW. You can uninstall just the Aura Creator/Aura Sync module via Windows Apps settings or Armoury Crate’s installer. As one user put it, “It’s the Aura Lighting… uninstalling [just that]” can resolve the issue while letting you retain the rest of Armoury Cratereddit.com. At the very least, turn off in-game RGB integrations or lighting effects while playing WoW to minimize interference.
  3. Shut Down Armoury Crate Processes Before Playing: Armoury Crate runs several background processes (for device control, updates, overlays). Manually closing Armoury Crate and its related services prior to launching WoW can be a quick workaround. For example, terminating the ArmouryCrate.Service.exe task prevented a launch issue and allowed the game to runus.forums.blizzard.com. You can disable Armoury Crate’s auto-startup in its settings or Task Manager, so it doesn’t load at boot. This way, you only run it when needed (and keep it off during gaming sessions).
  4. Update System Drivers and BIOS: Some players initially experienced the memory error after a Windows or game update, which can exacerbate conflicts. Ensure your motherboard BIOS and drivers (especially for chipset, audio, and GPU) are up to date – either via ASUS’s support site or Windows Update. In one case, users had issues with an outdated ASUS Audio driver contributing to crashesforums.flightsimulator.com. Updating might not fix an Armoury Crate bug directly, but it rules out other factors. Conversely, if the problem started right after an Armoury Crate update, you could try rolling back to a previous version (or uninstall until a patched version is released).
  5. Disable Specific Armoury Crate Features: Armoury Crate is a suite with various features (RGB sync, device tuning, “Gaming Mode” optimizations, noise cancellation for mics, etc.). You might experiment with turning off features like In-Game Overlay, GPU stats, or the AI Noise Cancelation. For instance, the ASUS Noise Canceling Engine was flagged for causing frame drops in WoWus.forums.blizzard.com; disabling it or other Armoury Crate sub-services via the app or Windows Task Scheduler might improve stability. Essentially, try to minimize Armoury Crate’s footprint while running WoW.
  6. Use Minimal Alternatives: If lighting or fan control is needed, consider using alternative software. Tools like OpenRGB (for RGB lights) or BIOS-level fan controls can replace Armoury Crate’s functions without the heavy background processes. This isn’t a direct “fix,” but it allows you to keep functionality while removing Armoury Crate from the equation.

Finally, always back up your system or set a restore point before making changes like removing drivers or software. If the crashes persist even after dealing with Armoury Crate, you may need to look at other causes – but given the evidence, Armoury Crate is a prime suspect for WoW memory errors, and many players have regained stability by getting rid of it.

References

  • Blizzard Forums – “Access Violation ‘Memory could not be written’” (Technical Support thread) – discussion of Armoury Crate/Aura causing instabilityus.forums.blizzard.comus.forums.blizzard.com.
  • Blizzard Forums – Error #132 thread – Support identified ASUS Armoury Crate (asus_framework.exe/Aura) errors in user’s logsus.forums.blizzard.comus.forums.blizzard.com.
  • Blizzard Forums – “Blizzard Looking Glass down?” – noted Armoury Crate’s noise-cancel service as a culprit for frame dropsus.forums.blizzard.com.
  • Blizzard Forums – WoW 2boxing freeze thread – user’s Event Log showing ArmouryCrate’s GridPlugin.dll crash (0xc0000005) during WoW freezeus.forums.blizzard.com.
  • Reddit – r/ASUSROG discussion “Is this due to Armoury Crate?” – Aura Sync identified as cause of “out of memory” errors; uninstalling AC/Aura fixed itreddit.com.
  • Reddit – r/ASUS thread “Armoury Crate and WoW…NOT A MATCH! (SOLVED)” – user reports uninstalling Armoury Crate stopped WoW crashesreddit.com.
  • Blizzard Forums – “Is anyone having issues launching their game?” – user discovered WoW wouldn’t launch until Armory Crate was closed in Task Managerus.forums.blizzard.com.
  • MS Flight Simulator Forums – “Solved my CTDs after months…” – user removed Armoury Crate, Aura, and other ASUS software to fix memory read errors in MSFSforums.flightsimulator.com
79

oh god, really? i hope it was armory crate that caused it then. would not want to crash with async resources disabled. If it still keeps crashing with it uninstalled maybe try to disable all the settings under compatibility settings :sweat_smile:

80

But it worked well for weeks with just async disabled. Only thing that i did before new wave of crashes was installing armory crate. It was worse than ever. Crashes when changing characters , crashes when just logging in. Will see haven’t played yesterday so not sure if it helped yet.

81

Overall looks like everything can make this game crash:| overlays , armoury crate and million other things.

At some point, I’ll have to buy a second PC with only the essentials installed to run WoW and nothing else, just to be able to play ::upside_down_face:

Let’s keep this thread going—maybe in a couple of years they’ll finally fix it or at least acknowledge that something is wrong