Access Violation crashes

Support Technical Support
1

I keep crashing due to Exception: ACCESS_VIOLATION. Memory coud not be “read”, could be in the first 5 min up to an hour. I have done tried multiple things to try to fix that others suggested on diff threads I read.

  • Updated Drivers
  • Checked BIOS there isnt any Turbo mode option to even turn on or off
  • Unchecked the two graphic settings
  • Ratio is at 100% already
  • Uninstalled and Reinstalled WoW and Battlenet

I am just stuck. There isnt a specific action I do to cause the crashes its random. I do not have a 13th or 14th Gen chip either. DXdiag here https://pastebin.com/ntbejF0c

2

2 things for me, others might see something else. Not sure why a win10 install shows a win7 driver. Also the driver for a device, looks like audio capture, is 10 years old.

I don’t know if this is causing your issue though.

Sound Tab 1: The file vbaudio_cable64_win7.sys is not digitally signed, which means that it has not been tested by Microsoft’s Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo’d driver from the hardware manufacturer.

Sound Capture Devices

        Description: CABLE Output (VB-Audio Virtual Cable)

Default Sound Capture: No
Default Voice Capture: No
Driver Name: vbaudio_cable64_win7.sys
Driver Version: 1.0.3.5 (English)
Driver Attributes: Final Retail
Date and Size: 9/1/2014 6:00:00 PM, 41192 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

3

Updating this post, after removing the VB Audio completely, it still does crash. Expected that but was worth the try

4

Did you recently update from a amd GPU or CPU?

Fault bucket INVALID_REQUEST, type 0
Event Name: WindowsServicingFailureInfo
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.19041.4950:1
P2: 0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.5007_none_f333b30e7fe6d944
P3: ??›???

5

I have not, also not that you asked but just wanted to add, WoW is the only game giving me crashing problems

6

Wow is more CPU intensive then pretty much any other game on this planet. I play Red redemption 2 and my CPU runs 10c hotter playing wow. Well my GPU runs hotter playing Red redemption 2.

7

I would try running repair for Windows. The error I pointed out earlier could very well be why wow it’s not working properly.

https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca#:~:text=Type%20DISM.exe%20%2FOnline%20%2F,%2F")%20and%20press%20Enter.

8

Okay I will try that, thank you for the help

Update: Both things the instructions said to do were successful and the one said it found no integrity violations.

Update 2: It did not fix the issue

9

I too am now getting these on my new prebuilt PC…. Out of nowhere! Have been playing since TWW came out with my new PC with no issues and then all of a sudden bam! Everything is updated and not sure what to do, it makes me so upset as I just came back to the game because I have a good computer again, i9, 4070, 64gigs of DDR5… help :frowning:

1 Like
10

For me, this issue started after the last update. I can log in, choose a character, but when I start doing anything I get the “Access Violation” “memory could not be written” Worst part is anything else I try to run works like normal, it’s just wow that is giving me issues

11

I had posted last month of the same issues and let my sub lapse.

I received the updated Intel BIOS patch to address the known issue with 13th and 14th gen CPUs.

Resubbed and I am seeing crashes again. I played for a month on FF14. Pre-BIOS patch it would crash a few times, but post BIOS patch it never crashed a single time.

This is a WOW issue and they need to address it. It makes the game unplayable at usually the most intense parts (delves, dungeons).

12

Had the same issue on my end. If you are on an Nvidia GPU try rolling the drivers way back. I don’t know exactly where it stops happening, but I am on the 552.12 drivers from April and I have not seen an access violation in 2 days. I know the last two more recent version were still causing it.

13

This started happening to me again tonight, completely at random. I encountered the crashing back when 11.0 first dropped (the prepatch) and eventually the solution that worked for me was adjusting my render scale to 100% (a blue post suggested that doing that would help).

Disabling addons also seemed to alleviate the issue, but this is WoW—the game is not designed to be played without addons if you, like me, want to excel at harder content (like high keys and mythic raid).

Now my render scale is 100%, and I tried disabling Optional GPU Features (another proposed solution from back in July), and the issue persists. I’m testing the game without addons to see if it makes a difference, but again, I’m not showing up to raid without addons.

14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.