I haven’t started having this issue until recently where after playing for about 10-30 minutes, the game crashes with error message "The memory could not be “written.” I have disabled addons, deleted the cache and WTF folders, updated BIOS and drivers, and reinstalled WoW. I haven’t made any changes to my hardware and any overlay software apps are turned off while playing WoW. Not sure if anyone has had similar issues to assist.
Is the drive overfull? (less than 20% free)
I had this same issue but I had no issues on my PC and my ram was fine. This error usually went away for me with a restart of my pc but i doubt this is the case for u
If your hard drive isn’t full, and a restart doesn’t stop it, try running OS diagnostics on RAM or a diag tool by a trusted 3rd party. If that returns no issues you can try increasing the virtual memory allocation. System restore may also work, or an SFC scan.
At the time of creating this post I had only about 20% free in the drive. I deleted some folders and applications and got it down to about 40% free and am still facing the same crash issues…
1 Like
I am having the same issue starting today. Was running mythic plus and raids with no issues before. Tried everything that people have recommended and believe this is something on blizzard side.
2 Likes
What was the exact error?
Most of the errors are windows related, and not “Blizzard’s side”
Blizzard does not want to take accountability for anything. My game has been crashing every 2 minutes it is basically unplayable and the sad part is I paid 1 year of subscription. I have a brand new RTX 4090 alienware MR18 and when I contact tech support , they tell me to do all these troubleshoot that i have already done. They want to blame people’s computer instead of taking accountability and fix the game people are paying to play.
1 Like
If it is not blizzards side explain to me how I can play all other games without getting a crash except this one?
2 Likes
Ran a memory diagnostic to identify any issues with RAM and it detected no errors. I then ran DISM.exe for a scan and the operation is completed successfully. The drive that WoW is running off is only about 60% full. Regardless of the following I’m still having the same error message. 
The same question could be asked why you’re having issues but the majority of players are not. Blizzard does keep logs of how many people are online and how many get disconnected, so they would know if there was a “widespread issue.”
Tech support is just that — a troubleshooting resource. They are not developers; they didn’t make the game. They provide assistance as a courtesy — it’s not something you’re paying for with your subscription.
By Blizzards side I mean server more than client. Unfortunately not everyone is affected by a given crash, hard to yell what your crash is caused by. Submitting those crashes through the reporter might help more. Unfortunately the forums can’t read the diagnostic code usually associated with the crash.
I think the processor is the 14900HX? Not sure if it’s affected by the VM core issue as other 13th or 14th gen Intels.
Nothing a gm can fix directly by web ticket, so unfortunately those recommendations is what I would use too.
Maybe withe the new patch coming soon? Not sure, wait and see i guess.
I too started having this issue. About 30 mins ago. My game is on a seperate drive from the other games and that drive is a 500g with only 25%. Im running 64gs of memory with a 3080. Now im getting the “Program: Z:/World of Warcraft/retail/wow.exe exception: access_violation- The instruction at " bunch of numbers” referenced memory at “bunch of 0’s” The memory could not be “executed”
See below for top line of error message
Summary
================================================================================
World of Warcraft: Retail Build (build 53007)
Exe: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
Command: “C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe” -launcherlogin -uid wow_enus
Time: Jan 20, 2024 11:38:15.140 AM
User: David
Computer: DESKTOP-UJSSLF6
==============================================================================
Exception: ACCESS_VIOLATION - The instruction at “0x00007ff66d13d191” referenced memory at “0x0000026cab450000”.
The memory could not be “written”.
ProcessID: 65996
ThreadID: 2588
<Exception.IssueType> Exception
Crash
Exception.Summary:
ACCESS_VIOLATION - The instruction at “0x00007ff66d13d191” referenced memory at “0x0000026cab450000”.
The memory could not be “written”.
(DBG-OPTIONS DBG-ADDR<00007ff66d13d191>(“Wow.exe”) ← DBG-ADDR<00007ff66d145264>(“Wow.exe”) ← DBG-ADDR<00007ff66d13b2ce>(“Wow.exe”) DBG-OPTIONS<>)
you need another ssd or need to delete something i had this issue awhile back only had like 25gb free on the drive with wow
1 Like
LOL it could never have anything to do with Microsoft or other external fixtures. go figure you complain and then claim you bought a year sub lol total karen behavior.
C drive currently has 452 gigs free of 930 gigs and has had no problems running WoW until only a week or two ago, and I haven’t really installed anything new since then…
Some additional info below on PC specs
Summary
| OS Name | Microsoft Windows 11 Home |
|---|---|
| Version | 10.0.22631 Build 22631 |
| Other OS Description | Not Available |
| OS Manufacturer | Microsoft Corporation |
| System Name | DESKTOP-UJSSLF6 |
| System Manufacturer | ASUS |
| System Model | System Product Name |
| System Type | x64-based PC |
| System SKU | SKU |
| Processor | 11th Gen Intel(R) Core™ i9-11900K @ 3.50GHz, 3504 Mhz, 8 Core(s), 16 Logical Processor(s) |
| BIOS Version/Date | American Megatrends Inc. 1801, 12/26/2022 |
| SMBIOS Version | 3.3 |
| Embedded Controller Version | 255.255 |
| BIOS Mode | UEFI |
| BaseBoard Manufacturer | ASUSTeK COMPUTER INC. |
| BaseBoard Product | TUF GAMING Z590-PLUS WIFI |
| BaseBoard Version | Rev 1.xx |
| Platform Role | Desktop |
| Secure Boot State | On |
| PCR7 Configuration | Elevation Required to View |
| Windows Directory | C:\WINDOWS |
| System Directory | C:\WINDOWS\system32 |
| Boot Device | \Device\HarddiskVolume17 |
| Locale | United States |
| Hardware Abstraction Layer | Version = 10.0.22621.2506 |
| User Name | DESKTOP-UJSSLF6\David |
| Time Zone | Eastern Standard Time |
| Installed Physical Memory (RAM) | 32.0 GB |
| Total Physical Memory | 31.8 GB |
| Available Physical Memory | 21.2 GB |
| Total Virtual Memory | 36.6 GB |
| Available Virtual Memory | 16.8 GB |
| Page File Space | 4.75 GB |
| Page File | C:\pagefile.sys |
| Kernel DMA Protection | Off |
| Virtualization-based security | Not enabled |
| Windows Defender Application Control policy | Enforced |
| Windows Defender Application Control user mode policy | Off |
| Device Encryption Support | Elevation Required to View |
| Hyper-V - VM Monitor Mode Extensions | Yes |
| Hyper-V - Second Level Address Translation Extensions | Yes |
| Hyper-V - Virtualization Enabled in Firmware | No |
| Hyper-V - Data Execution Protection | Yes |
| Name | NVIDIA GeForce RTX 3050 |
| — | — |
| PNP Device ID | PCI\VEN_10DE&DEV_2507&SUBSYS_88721043&REV_A1\4&39FDDC03&0&0008 |
| Adapter Type | NVIDIA GeForce RTX 3050, NVIDIA compatible |
| Adapter Description | NVIDIA GeForce RTX 3050 |
| Adapter RAM | (1,048,576) bytes |
| Installed Drivers | C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\nvldumdx.dll |
| Driver Version | 32.0.15.6614 |
| INF File | oem37.inf (Section078 section) |
| Color Planes | Not Available |
| Color Table Entries | 4294967296 |
| Resolution | 1920 x 1080 x 240 hertz |
| Bits/Pixel | 32 |
| Memory Address | 0xA0000000-0xA10FFFFF |
| Memory Address | 0x0000-0x1FFFFFF |
| I/O Port | 0x00004000-0x00004FFF |
| IRQ Channel | IRQ 4294967275 |
| Driver | C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_ADF5A840DF867035\NVLDDMKM.SYS (32.0.15.6614, 72.75 MB (76,279,952 bytes), 11/30/2024 5:07 PM) |
1 Like
Then I shall demand I get my money back. Since there is no one to take accountability for the crashes. Thank you I will demand I get my money back
It’s unfortunate you’re unable to get your PC setup to work with WoW after updates, but there’s no need for making demands. There’s a return policy and a self-service refund option if you choose to go that route.
https://us.battle.net/support/en/help/product/wow/166/1152/solution
Have you checked your file and folder permissions as they could be set to read only, make sure folders are set to read and write. And before you blame blizzard it’s a windows flaw that has Been around for decades.