Game crashes, memory could not be "read"

Support Technical Support
1

so when wow started to ask me to install new bios i did… it went well and wow stopped talking about it but ever since then wow keeps crashing randomly. usually once per raid night and even in town while doing nothing.

error message says something about ACCESS_VIOLATION and then memory could not be “read”

my dxdiag WER list is full of livekernel event 193 id:0 also, idk if it’s related.

chkdsk says no error
dism says all is good
sfc says all is good
windows memory diagnostic tool passed with 0 errors

newest nvidia driver from today clean install
newest bios/chipset/lan/audio all installed from MSI website
windows update says it’s up to date.

scan & repair from launcher finds nothing to repair.

it still crashes the same way no matter what i do ever since that bios update. it’s only wow as far as i know, i’m very pleased with how the system behaves outside of wow.

what else should i try? i do not really feel like opening a ticket for a long back n forth of things i already did lol

*i’m thinking all that is left to try is reinstall windows and wow fresh but thought i’d ask for ideas here before i jump into that.

1 Like
2

Processor likely had duty cycle degradation before you updated bios to mitigate it. RMA it. If it’s a pre built, contact the manufacturer.

3

nah it always performed beautifully and still does. didnt have anything to say about it until wow made me think i should install a new bios :wink:

im not gonna rma a chip that works great for everything except wow and wow was also doing great before it asked me to upgrade bios lol

i get your idea, trendy subject. doubt that’s my case tho.

*going back to the older bios and ignoring wow’s bios popup might be a solution though, now that i think about it.

i really wish wow never had that popup i would still be worry free , chilling. lol

4

Until the CPU gave up the ghost permanently. Given your “see no evil” attitude, after even the extended warranty period.

1 Like
5

i dont think there is evil to see. only wow crashes no other problem. just a nice crash to desktop too. and only since i updated bios at the request of wow.

im not going with the nuclear option when only wow might crash once per 3 hours with no other symptom

i get it tho, anyone with a 13/14th gen cpu is doomed to hear this forever even with an unaffected chip :slight_smile:

6

because every chip is doomed to be affected when run prior to microcode updates.

7

why was it perfect on the old bios and only wow is acting up only after new bios?

dont you think it might be a bios setting or something? youre just jumping to the most extreme option right off the bat… cmon.

8

occam’s razor. It just so happens that the most extreme option is also one of the most likely options. It’s also literally in the sticky

9

alright ill go back to the old bios and forget about it. wish wow wouldve minded its own business. what a waste of time.

thanks for the hasty thoughts even if i dont agree with them :slight_smile: was worth a shot.

10

Well that’s certainly your prerogative

11

alright so it was an easy fix after all. 1 bios setting.

“CPU lite load” was on normal and i put it on intel’s default instead.

would’ve never figured it out myself but i found a video of someone having the same issue in fallout 76 and that was his fix.

been in the game for 4+hours without crashing everything is gucci now.

12

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