Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
That is, unless you're suggesting M.S.I. locks down rolling back the B.I.O.S. to a prior revision after the B.I.O.S. update is installed. Do they do that?
either let old bios damage cpu farther, or not run xmp til newer bios fixes it
or did op just not enable xmp?
don't act like this is happening to everyone man.
They'll be working hard on those updates right now and mistakes can happen. If you think there's a real problem then tell them.
fwiw, no 1.E on this list...
https://www.msi.com/Motherboard/Z170-A-PRO/support
he just don't understand what he is doing is all
and you can just use live update to check for your all your mobos new stuff.
you can try to write your own bios, but good luck with that
M.S.I. has some motherboards with the relevant 0x129 (not 0x0129) microcode out already. 0x125 is also supposed to address it if I recall correctly, so that might be worth trying but it's a leaked beta version fix instead of the final fix, so it might not work as well (if at all). I posted a list of the first few they released the 0x129 code for in another topic, but here it is again:
They've pleged to have the microcode rolled out for all of their 600 and 700 series motherboards by the end of the month, so keep checking for updates.
Jayz
the corps that talked to that guy have a bad batch.
did you read that verve news article?
nvidia told people if it don't effect you by now you are safe.
What I did read is this:
But that suggests that the new microcode will prevent damage from occurring once applied to the chip if it hasn't already been damaged, not that the chip can't be damaged if you continue to run the old code just because it hasn't been damaged already.
no one has been hurt by this outside of those companies.
polls show this.
"But Intel does tell us it’s “confident” that you don’t need to worry about invisible degradation."
Thanks, yeah I did watch that video the other day. I have the Pro z790-VC Wifi and I'm watching for the update.
The reason I'm waiting to update until a good bit after the 0x129 is posted is I want to see what the analysis and consensus is over a reasonable time frame, because I don't exactly trust Intels fix to only be adjusted voltage requests and not include something dumb like, for example, hammering the cpu with constant idle c-states even under load.
I absolutely do have this system capped, clamped, limited, undervolted, and locked down ATM but it's also never crashed or been unstable even at MSIs wacky default power settings. Shouldn't have to wait very long.
*EDIT*
Yep, this is a good example of why I wait...
https://www.youtube.com/watch?v=dqyaiTUaH9A
The voltage trend sheet showing all microcode versions, first to last, is F'in scary.
If Intel is purposefully lying to us regarding the nature of the microcode update, then they've signed off on their own death warrant.
Back in 1995, Intel recalled all of the Pentium P5 chips over a minor floating point error error and made keychains out of them with the following inscription[www.businessinsider.com].
As big as Intel was back then, they were only worth eleven to sixteen billion at the time[www.intel.com].
Now that the chips are literally destroying themselves 19 years later and they are an 84 billion dollar company, they refuse to issue a recall[www.theverge.com] over much more drastic defects, already downgrading the company status from great to good at most, but probably closer to bad considering they've been acting shady as heck. It's already bad enough that they didn't make a public announcement regarding the oxidation defect discovered in 2022, but outright lying to the customer?
Not only would that destroy whatever shred of faith people have left in the company, but it'd open them up to even more lawsuits.