Machine constantly giving ACCESS VIOLATION Errors

Support Technical Support
1

I have a Gigabyte 5080 Gaming OC 16G

Set the game back to default removed all addons and reinstalled.

Set BIOS on motherboard to run at gen 4 for graphics card

removed all virus protection

I have turned of overlays, reinstalled, changed memory, check the bios on motherboard upto date, turned off addon, set to divx 11 with d3d11. I cannot work out what is wrong… Here is the first couple of lines of log. ================================================================================ World of Warcraft: Retail Build (build 64743) Exe: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe Command: “C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe” -launcherlogin -d3d11 -uid wow Time: Dec 5, 2025 8:08:21.694 PM -------------------------------------------------------------------------------- ============================================================================== Exception: ACCESS_VIOLATION - The instruction at “0x00007ffba7d09e24” referenced memory at “0x00000f5d00040019”. The memory could not be “read”. ProcessID: 22412 ThreadID: 14124 ------------------------------------------------------------------------------ <Exception.IssueType> Exception Crash Exception.Summary: ACCESS_VIOLATION - The instruction at “0x00007ffba7d09e24” referenced memory at “0x00000f5d00040019”. The memory could not be “read”. (DBG-OPTIONS DBG-ADDR<00007ffba7d09e24>(“nvwgf2umx.dll”) ← DBG-ADDR<00007ffba7fce04f>(“nvwgf2umx.dll”) ← DBG-ADDR<00007ffba7fcdfb0>(“nvwgf2umx.dll”) DBG-OPTIONS<>) <:Exception.Summary> Exception.Assertion: DBG-ADDR<00007ffba7d09e24>(“nvwgf2umx.dll”) DBG-ADDR<00007ffba7fce04f>(“nvwgf2umx.dll”) DBG-ADDR<00007ffba7fcdfb0>(“nvwgf2umx.dll”) DBG-ADDR<00007ffba7fc2cfd>(“nvwgf2umx.dll”) DBG-ADDR<00007ffba84d591a>(“nvwgf2umx.dll”) DBG-ADDR<00007ffba888c4ba>(“nvwgf2umx.dll”) DBG-ADDR<00007ffcbe3fe8d7>(“KERNEL32.DLL”) DBG-ADDR<00007ffc192b9f40>(“”) DBG-ADDR<00007ffcbeeec53c>(“ntdll.dll”) <:Exception.Assertion> Exception.HashBlock: DBG-OPTIONS ERROR #132 nvwgf2umx.dll nvwgf2umx.dll nvwgf2umx.dll nvwgf2umx.dll nvwgf2umx.dll nvwgf2umx.dll DBG-OPTIONS<> <:Exception.HashBlock> No <Jira.JiraProjectId> 11701 <Jira.JiraProjectKey> WOW11 <Exception.ProjectId> 10

2

My search is pointing to trying to ddu the driver, then reinstall but more info might be needed. What CPU, how much system memory, are the memory sticks matched, in 1, 2 or 4 sticks. A dxdiag might help.

Please note, this is a player to player discussion forum, myself also just a player. Unfortunately this is not a forum where direct diagnosis or fixes are guaranteed. There is more information about your PC we may need to evaluate your issue, but this does not replace the need for a full evaluation and may need a local PC tech to become involved if you are not sure of how to proceed. With this in mind we can look at a dxdiag and make some recommendations. Errors are usually noted on the end.

To run dxdiag, open the Run window (Windows key + R), type “dxdiag”, and press Enter or click “OK”. This will open the [DirectX Diagnostic Tool], where you can view system information and save a report.

You can paste the results to a site like pastebin.com to help bypass the character limitations imposed by Discourse.

Steps to run dxdiag:

Open the Run window: Press the Windows key + R.

Type dxdiag: In the “Open” field, type “dxdiag” (without quotes).

Run the command: Press Enter or click “OK”.

The DirectX Diagnostic Tool will open: You can then explore the information it provides and save a report if needed.

Save the report (optional): Click “Save All Information” to save a text file containing the diagnostic data.

Choose a location and save: Select a location on your computer to save the file.

Exit the tool: Once you’ve saved the report (or if you don’t need to save it), you can exit the DirectX Diagnostic Tool.

For a Diag, you can post it to a site like pastebin, and then code the link to bypass trust level restrictions.

Posting a Code Line

Wrap the link in the Tilde. ` or use the preformatted button in the editor.

1 Like
3

This is system and crash log

4

Repost just the DX, and the full report, unfortunately it got cut off.

5

This is system and crash log all

6

Processor: Intel(R) Core™ i9-14900K (32 CPUs), ~3.2GHz

How long have you had this PC? Some of these CPUs are starting to degrade despite the BIOS updates.

Driver Date/Size: 2/12/2025 10:00:00 AM, 816488 bytes

Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: nvcontainer.exe

The GPU driver is considerably out of date and crashing. Time to run DDU and reinstall the latest driver.

2 Likes
7

about 9mths I have had it. I have just updated the nvidia driver.

8

Your GPU driver is fine

Driver File Version: 32.0.15.9144

This came out the day this post was made. You could try to revert back to 8194 (the previous nvidia version) if you’re noticing it started happening that day.

Also, edit out your account information next time you post a dump. People are weird on the internet.

1 Like
9

But it wasn’t a clean install, or the date would have fully updated. There are still old driver remnants, which are out of date.

1 Like
10

i would like to echo this, rolling back updates.

i have a 13700K since its launch and was having crashes after updating bios about 9 months ago, i can’t even begin to tell you how many replies have been “update bios again” or “your cpu is ded get a new one”. i kept updating bios and it kept crashing, until i reverted back to a bios from a year ago and now WoW i back to normal again.

11

Intel put out these code updates to hopefully keep the CPU from being exposed to too much voltage, in turn not causing the CPU and Motherboard from being damaged. If the damage was already started, updating the Bios likely would not help. Intel was the one that issued these alerts though, rather then issuing a full recall on the affected SKU.

But the GPU driver would not be related to the Bios you used.

1 Like
12

sorry if i caused confusion but what i should have said was that if you had a period of time where you were not crashing and stated after an update, rollback that very update. not specifically pointing to rolling back the gpu driver. also i believe access violation is system memory and not related to gpu.