Access Violation With AMD processor

[Ishae-area-52]

Im not sure whats going on, yesterday i had no issues logging into WoW, this morning, when i try to log in, i keep getting an Access_Violation - the instruction at 0x00007ff746e86a0d referenced memory at 0x000001ef30c4f058, the memory could not be written. And then wow crashes, this is occuring on startup just as the window box pops up to log me into the server. I have done scan/repair, restarted my pc, updated my bios, updated my AMD drivers, and nothing is working. I am using a Ryzen 7 7700x processor, 32 gb ram, and running windows 23H2. Any input would be aprec, not the most tech savy here.

[Kozzae-doomhammer (Kozzae)]

@Elocin-mugthol

Can you add a DxDiag here?

Click here to show/hide DxDiag report instructions

1. Press Windows Key + R, then type DxDiag and press Enter.
2. In the DxDiag window, click Save All Information.
3. Name the file dxdiag and click Save.

After you have the report:

• Upload to Pastebin.com .
• Paste the link in your reply.

Note: If you have trouble posting the URL, highlight the link and click </> on the post editor toolbar.

Please note that there is no guarantee what’s causing your issue will be apparent from a DxDiag and you may need to do more investigating on your own.

More information is needed

[Ishae-area-52]

Here is the dxdiag report, https://pastebin.com/6YVckm11

[Kozzae-doomhammer (Kozzae)]

Let’s try making sure your windows is up to date? Maybe try scan and repair on the app launcher.

Oddly did not see any wow.exe or battle.net error buckets, but some BEX errors, possibly memory or storage related? ChatGPT seemed to point to some things that I don’t personally understand directly. Some if it is a bit beyond me to point and recommend.

The diagnostics you provided include multiple instances of application crashes and errors, primarily related to:

1. BEX (Buffer Overflow Exception) Errors:

• These errors are associated with cpudump.exe and the MFCCPU.dll library.
• The specific error code c0000005 suggests an access violation, indicating that the application attempted to access memory it was not allowed to.

2. StoreAgent Errors:

• These errors relate to update and installation failures in the Windows Store.
• Common error codes:
  • 8024001e: Generic error indicating a Windows Update or Store update issue.
  • 80073d02: An issue where a resource needed by the update process is unavailable, possibly indicating a conflict or a file lock.

---

Troubleshooting Steps

1. Resolve BEX Errors (cpudump.exe & MFCCPU.dll)

• Update the Application: Ensure cpudump.exe and its associated libraries (e.g., MFCCPU.dll) are up-to-date.
• Check for Compatibility: If this is an older application, ensure it is compatible with your version of Windows. Use compatibility mode if needed.
• Investigate DLL: If MFCCPU.dll is a custom or third-party DLL, ensure it is not corrupted. Replace it with a clean copy if possible.
• DEP (Data Execution Prevention): Disable DEP for cpudump.exe temporarily to see if it resolves the issue:
  • Go to System Properties > Advanced System Settings > Performance > Data Execution Prevention.
  • Add cpudump.exe to the exceptions list.
  • Note: Use this only for testing; leaving DEP disabled can reduce security.
• Debugging: Analyze the crash dump or use debugging tools (e.g., WinDbg) for more details.

2. Fix StoreAgent Errors (Update & Install Failures)

• Run the Windows Store Troubleshooter:
  • Open Settings > System > Troubleshoot > Other troubleshooters.
  • Run the “Windows Store Apps” troubleshooter.
• Reset the Windows Store:
  • Run the command wsreset.exe in Command Prompt as Administrator.
• Re-register Store Apps:
  • Open PowerShell as Administrator and run:

powershell

Copy code

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

• Check Services:
  • Ensure that the Windows Update and Background Intelligent Transfer Service (BITS) are running.
• Clear SoftwareDistribution Folder:
  • Stop the Windows Update service:

cmd

Copy code

net stop wuauserv
net stop bits

• Delete the contents of C:\Windows\SoftwareDistribution.
• Restart the services:

cmd

Copy code

net start wuauserv
net start bits

3. General System Maintenance

• Check for Corrupt System Files:
  • Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt.
• Check Event Viewer:
  • Review the logs under Windows Logs > Application for more details about the errors.

If issues persist after applying these fixes, additional context (e.g., recent changes, system configuration) or detailed error logs may be needed for further analysis.

[Ishae-area-52]

Tyvm for looking at that, i will attempt to do some of what you have indicated, although when i did a cursory inspection looking for cpudump.exe it doesn’t come up at all, and i cannot even put it on an exception list.