For several months I had a very annoying problem with Windows; most of the time (80%+) when closing my PC down I would get an error pop-up:
"explorer.exe - Application Error
The instruction at 0x00007FFD9C3ACA referenced memory at 0x0000000000000024. The memory could not be written.
Click on OK to terminate the program"
As anyone who’s had this very annoying intermittent error knows, it’s nearly impossible to track down and fix, which meant that I was stuck with a fairly new PC just not working properly any more and so (this sounds dramatic but it’s true) making everyday life a tiny bit worse.
Anyway, guess what happened when the 11.0 pre-patch dropped? Yes, the error went away!
Has the same thing happened to you? Or am I mad and this is all just a big coincidence?
For context, the only other significant thing that happens on this PC is Windows updates; no other apps or programs have been installed or updated. And no Windows update happened concurrently with this sudden ‘fix’.
Seeing the recent state of Blizzard’s programming (where, for me at least, bugs are becoming so prevalent and longlasting as to interfere with my everyday enjoyment of the game) I can’t help but think that the error had been introduced by a previous Blizzard patch in the first place and that their programming has gotten so bad that it can mess up your entire Windows installation.
The number of similar crashes being reported in this forum since 11.0 dropped only reinforces this idea.
I hope that some rare genius WoW dev sees this post and that it helps them to figure something out that eventually leads to fewer such crash-inducing bugs … but I’m not holding my breath.
…
13th Gen Intel Core i9-13980HX 2.20 GHz
NVIDIA GeForce RTX 4090
Windows 11 Home
And don’t phrase comments as to be insulting. You are effectively saying that I’m stupid, I should already know this thing and you are literally laughing at me (in emoji form).
I’m interested in hearing from people who have had the same issue.
Well im sorry if you are that easily offended by an emoji.
I answered your question and it seems like you already know that wow or any other game can not have the impact on your windows files like you were describing.
Why not just be glad that it seemingly fixed itself.
I was offended because your whole comment (not just the emoji) was phrased to imply that I’m stupid, that I should know this thing already and to laugh at what you percieve to be my ignorance.
And now you with your, “Why not just be glad that it seemingly fixed itself”, you are telling me how I should be feeling! I should be glad, should I?
Well, thanks for your input but it is not helpful and I would appreciate it if you would not comment further unless it is with something relevant and constructive.
Forgive me if I do not simply take your word for it that what I am describing is impossible. If I hear that from several people (that don’t start off by insulting me) that they believe that to be the case and they prove to me their tech credentials and expertise with a really detailed explanation then perhaps I will re-evaluate. Until then, I’d really appreciate it if you didn’t derail this topic.
EDIT: also, you say that, “it seems like you already know that wow or any other game can not have the impact on your windows files like you were describing”. If that were the case I would not have asked this question in the first place. I know no such thing, especially when all the evidence I have seen and experienced is clearly pointing in that direction.
I will once again ask, to get things back on track, has anyone else had a similar experience to the one outlined in my original post?
This thread has been closed now due to multiple violations of the Code of Conduct.
As to clarify the curiosity and concerns of the original poster, we’d like to confirm that WoW patches are in no way able to interfere with OS operations and functionalities
That said, in the past days and weeks Windows 11 received updates for some systems, so chances are that this was indeed just a big coincidence ^^
