Hi my PC has just recently started displaying this error for the last 2 months -
“0x00007ff618047cd7” referenced memory at “0xfffffffffc2349cb” The memory could not be “read”
I have tested my ram, Got a new graphics card xtx7900, made sure all my drivers are up to date, reinstalled WoW, Played with no addons / minimal addons / lots of addons, Repaired game files, Deleted cache / interface / wtf folders, changed graphics settings… I’ve done the lot
If its listed for a fix I’ve done it And I’m still running into the same result a month into the expansion with my enjoyment of the game becoming less and less due to the crashes or the fear of running into a crash on heroic progression or ranked arena’s
My pc specs are -
MOTHERBOARD - Z690 STEEL LEGEND WIFI 6E
CPU - 13TH GEN I9 1300KF 3000MHZ
RAM - 64GB KINGSTON FURY DDR4
GPU - AMD RADEON RX 7900 XTX
OS - WINDOWS 11
Error in pastebin
If you need any additional information ill post what i can. Please help me put an end to this misery its really ruining my experience for the new expansion
Access violation errors are exactly what they sound like: the game can’t access the assets. What’s up with this directory structure?
D:\WoW\WoW\World of Warcraft\_retail_\Wow.exe
If you want to know what the specific memory address is pointing to in the error file, you have to read the memory dmp file (requires a debugger tool). Sometimes volunteers in the Windows forum will read them.
You’ve tested a lot of pieces in your system, but have you confirmed you’re not suffering from the Raptor Lake issues that came to light earlier this year? The short of it is that these chips have been “ageing” much faster than they should have, giving some of them a lifetime better measured in months rather than years or decades. Actual failure rate varies depending on who you ask, with some sources indicating single-digit percentages while others have experienced 100%.
Single-threaded workloads, which is going to include WoW due to the load disparity between its “Master” thread and supplemental ones, are more likely to show issues with this as they run higher clock speeds. There’s a library in Unreal Engine 5 that’s also known to cause problems fairly reliably citing a lack of video memory, while Ghosts of Tsushima is known to crash after the splash screen when attempting to pre-compile shaders (both misdirecting to graphics hardware).
Two microcode updates (available via BIOS updates) have been released to help address this so far, with a third expected in the next month or two. These can only help prevent the issue from occurring, though - they cannot undo what damage may have already been done. For chips that have already been damaged, Intel has extended the warranty for an additional two (2) years.
@asterchades that was one of the first things i got my mate to check. Luckily in my case i don’t overclock or change any bios settings apart from the xmp profile. So my chip is working per normal. But yeah definitely something that crossed my mind but have ruled out to be sure
Thanks for help and input much appreciated
Also for Blizz employee’s here is my crash log’s for today
I speak as Microsoft employee (SQL Server) when I say this: DO NOT UNDER ANY CIRCUMSTANCES EVER UPLOAD A DUMP FILE TO A PUBLIC LOCATION!!! These can and often do contain sensitive data INCLUDING PASSWORDS, CREDIT CARD INFO, LITERALLY ANYTHING.
A directx or msinfo usually doesn’t contain personal information, never seen any password or financial information. It’s mainly for diagnostic purposes only. Hopefully op can find out what their crash is with out it.
There are issues with the 13th gen CPUs with DX12 related games. I had similar issues with Remnant 2. There is a hacky fix and a longer term one being pushed out by intel. The hacky fix is if you download intel extreme tuning utility and drop the performance core ratio below the default (think its 55x) the game becomes stable again. Try dropping it to 54x or 52x and see if it fixes it.
The other fixes are bios updates being pushed out, so you will need to make sure your bios is up to date, as some of these patches were in the last few days.
Source: I had the same exact crashes for a while, and could not figure out the source until I tried a hail mary fix I did for Remnant. been able to stay fully logged in for 2 hours now with 0 crashes.
I was referring specifically to people posting memory dumps. msinfo is probably fine, though you’d want to review it in case it has something obviously identifying in there.
Most forums that will read your memory dump files have instructions for removing any sensitive information. I’m obviously not suggesting posting your financial info in public…
