Thank you Rommax, truly do appreciate the feedback on this. When we are presented with something like that error, it’s nice to see confirmation about why, and validation that it’s legit.
4 Likes
I’m going to be “that guy” with the opinion of “The BIOS I’m running is none of a gaming company’s business. Let my motherboard manufacturer deal with that kind of issue. What’s next, telling me I have to install Windows updates released two minutes ago before I can play?”
2 Likes
Clearly you didn’t read through this thread. You can still play the game without updating the BIOS, you are just doing so at your potential eventual peril.
1 Like
I’m well aware of the issue. You know I’m well aware of the issue because you liked my initial post in this thread. I was making a point.
Just put together a new build yesterday and ordered it.
Going back to an AMD build. My last AMD build was circa 2003, and have been Intel since.
I researched this issue, and it caused me to lose confidence in Intel.
2 Likes
Intel has been a dumpster fire. Fortunately their laptop chips aren’t affected (supposedly) since finding a decent AMD + nvidia laptop is a chore (or used to be at least).
2 Likes
The Laptop I built about a year ago was right up-to-date and has not had the issue at all thankfully.
I have an MSI prebuilt, and as such they say to only use the updates assigned to to it, however the last bios update was old and I got tired of seeing the popup.
ChatGPT helped me to see that I can simply get the latest bios for the mobo and to ignore the pre-built advice.
So I actually grabbed updates for all the components as well as the bios.
improved my PC performance and satisfied Blizzard. That was a couple months ago.
A lack of Windows updates won’t physically damage your CPU.
1 Like
Keeping your bios updated to the latest release is safe, plus it keeps you safe from malware bios attacks.
3 Likes
Well, managed it, and didn’t even get locked out of my account. I loved the full 1.5 min that my BIOS took to acknowledge that it was working on the update… finally. -.-
Not amused.
Because it has most likely has completely swamped their crash log system, and rendered it useless.
The problem is that updating your microcode does not necessarily prevent future crashes, as these CPUs have been permanently degraded. The microcode updates just stop further degradation, but if it’s already happened, it’s already toast.
Windows live-sideloads in new intel microcode updates via Windows\System32\mcupdate_GenuineIntel.dllwhen the BIOS has a version that’s out of date. The problem is it doesn’t persist through reboots and the OS has to sideload it in every time. Additionally, there are some updates that are restricted from sideloading, and IHVs will provide with BIOS updates for first.
1 Like
Get rid of that intel garbage and replace it with a superior X3D model.
But, where do I update my Bios from tho? I updated my computer and error still pops
The issue for me is that I already updated my BIOS and i’m still getting this message.
The issue for me is that I already updated my BIOS and i’m still getting this message. I didn’t receive the message until this patch. So I assume it’s a bug.
4 Likes
I updated mine back when they gave the previous message. Now it says to update it with the one from 9/27/24. That’s what mine is according to System Information. Not going to update it again. That’s a good way to screw up the computer for no reason.
3 Likes
So the consensus is another update needs to be done then?
2 Likes
It was never properly fixed. Intel CPU’s are still getting bricked, they’re just delaying the inevitable with the patches.
It’s Intel’s problem, not WoW’s. They’re just there to inform of you of it.
Correct.
7 Likes
Seriously. People who become accustomed to dropping money into their system every time something needs updating because Blizzard has changed something are closer to becoming P2W whales.
3 Likes