The memory could not be "read"

I get the code:
Exeption: ACESS_VIOLATION - The instruction at “0x00007ff683f4d578” referenced memory at “0x0000000000028”,
The memory could not be “read”.
processID:20068
ThreadID: 18180

PC is from November, I have the Processor Intel(R) Core™ i7-14700KF, 3400 Mhz, 20 Core(s), 28 Logical Processor(s)

I have done everything I can possible think of.

Clean version of windows, reinstalled wow only, no addons. Still crashes.
BIOS update, memtest86, windows repair tool. I have changed max power draw of long and short durations to 253 and icc max to 307.

It seems to happen more when I’ m resto druid for whatever reason, I have tried other games, but nothing else crashes.

In remix it once got the same message but with “write” instead of read. I have contacted manufacturer and they said I could send it in and they’d take a look. but I don’t have the original packaging, so hopefully it’s an issue with WoW. I have done the scannow, updated drivers, done tons and tons of tests all with 0 issues.

If your BIOS is rly the newest then force the motherboard to use Intel standard power/amp limits.
Its common mistake almost all 13th, 14th gen Intel systems, u can google for it.
Its not a wow error, its motherboard settings error (hopefully your CPU isnt degraded yet).
So disable enhanced CPU profile, and use Intel standard CPU profile.

How do I do this? In BIOS mode? :3

EDIT: I think I did it in BIOS mode… I’ll update if it crashes

EDIT EDIT: It crashed.

Try running with default BIOS settings, and with only 1 stick of RAM, also try putting it in different slots. It’s quite bizarre that if it’s related to hardware that it would only fail on WoW and no other game.
Have you looked through Windows System Logs to check for critical events on the exact time the game crashes?

I believe I only have one stick of ram, in the 2nd slot right now. I’ll try moving it around.

I have not tried this, I will figure out how to look through system logs and recreate the crash :smile:

This error is not WoW error, just this game can bring it out very easily.

Check your memory profile in BIOS, recommended to use XMP 1 profile, or manually set the manufacturer’s recommended timings/clocks.

Unfortunately its kind of error, what is “mostly” come out on Intel systems (not every occasion), thanks for the motherboard manufacturers aggressive CPU boost profiles (what can damage the CPU permanently as well).

As the suggest above me, u need to go to the lowest level. Default setting in BIOS, Intel defaults, memory profiles, trying 1 then 2 modules (or more modules), clean unused memory sockets as well. It wont hurt if the whole hardver gets a full air cleaning.
U can google for your motherboard manufacturer to get information other users how solved their problems maybe there will be a solution.
I am glad i bought AMD system, cause this kind of behaviors of the motherboard manufacturers are outrage.

I have switched memory slot…stick? something, I have reset to BIOS default.

Gonna keep an eye on event viewer and play a bit. I’ve learned a lot about pc soft/hardware at this point :3

EDIT: crashed again, event viewer however said this:

The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout.

So… gamebar is the next suspect

Hi, I had the same issue with constant crashing with a intel 13900K.
Had the gamebar dcom event too, but it was more of symptom of a faulty CPU than the root-cause.

Tried the following steps

  • running WoW with no addons,

  • updating all drivers,

  • running “Scan and Repair”,

  • doing a memtest86

  • installed WoW again run

  • switched to XMP 1 profile ,

  • dissabled XMP,

  • tried different RAM sticks

  • updated BIOS,

  • set BIOS manually to intels recommendet setting for 13th gen.

  • etc.

After many days of try and error and some more researched I decided to do a RMA (Return merchandise authorizatio) for my CPU as it was the only thing left to do.

Got my new CPU and no problems since then.
As already mentioned in this thread some CPUs will become defective / damaged because of the aggressive motherboard boost profiles.

Best of Luck

A friend of mine told me to disable intel turbo mode in bios and that fixxed it :grin:

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