AMD processor systems bricked by the Meltdown patch

I think by bricked they really meant borked Windows Update that Windows rolls back after failing to boot into Windows multiple times.
 
I started this thread because I am not sure what CPUs are affected. I've read that up to AM3 may be affected but not sure. Be nice to have a definitive answer. Still have a 555BE floating around without a home so can't test.
Edit So far it seems to have affected up to Athlon 64 X2 6400. Will update as more info is available.
Edit2. Had to laugh. Someone with a Threadripper 1950x reported the same issue on the MS Support thread.
 
Last edited:
And why exactly would you not check processor type and only patch the bad Intel boxes and bypass the AMD ones? Such idiots. Linux didn't have a problem with that.
 
Last edited:
I like how they try to blame this on 10 year old documentation. Hey idiots, how about DON'T APPLY A PATCH TO HARDWARE THAT DOESN'T NEED IT.

Intel: "Oops, we goofed, try this. Its no big deal, not our fault blahblahblah here have a cookie."
AMD: "We don't need this, lol."
Microsoft: "Hold my beer."

AMD please sue both these retards and win. Knowingly using defective or untested work from one vendor and allowing it to damage that vendor's competitor is pretty blatant.
 
10 year old spec is the problem? Funny, the processors worked fine 10 years ago. Somebody misread the spec or didn't bother to test. MS is liable.
 
I like how they try to blame this on 10 year old documentation. Hey idiots, how about DON'T APPLY A PATCH TO HARDWARE THAT DOESN'T NEED IT.

Intel: "Oops, we goofed, try this. Its no big deal, not our fault blahblahblah here have a cookie."
AMD: "We don't need this, lol."
Microsoft: "Hold my beer."

AMD please sue both these retards and win. Knowingly using defective or untested work from one vendor and allowing it to damage that vendor's competitor is pretty blatant.

The issue goes all the way back to PPro and K6.
 
10 year old spec is the problem? Funny, the processors worked fine 10 years ago. Somebody misread the spec or didn't bother to test. MS is liable.

At this point in time if you are crazy enough to buy Windows and not expect this something is wrong with you ;)
 
I like how they try to blame this on 10 year old documentation. Hey idiots, how about DON'T APPLY A PATCH TO HARDWARE THAT DOESN'T NEED IT.

Intel: "Oops, we goofed, try this. Its no big deal, not our fault blahblahblah here have a cookie."
AMD: "We don't need this, lol."
Microsoft: "Hold my beer."

AMD please sue both these retards and win. Knowingly using defective or untested work from one vendor and allowing it to damage that vendor's competitor is pretty blatant.
This patch applies to spectre, a variant which some AMD chips are susceptible to. The issue is that they changed something that (according to them) the documentation said wouldn't cause any problems (or at least, didn't explicitly say it would cause problems). Turns out it did. It could be that they overlooked something, or it may have actually been omitted from the documentation. Either way, Microsoft managed to botch an update again. Nothing out of the ordinary here.
 
This patch applies to spectre, a variant which some AMD chips are susceptible to. The issue is that they changed something that (according to them) the documentation said wouldn't cause any problems (or at least, didn't explicitly say it would cause problems). Turns out it did. It could be that they overlooked something, or it may have actually been omitted from the documentation. Either way, Microsoft managed to botch an update again. Nothing out of the ordinary here.

All AMD chips back to K6 are exploitable by Spectre. Every single OOO design from any vendor.
 
All AMD chips back to K6 are exploitable by Spectre. Every single OOO design from any vendor.
Thanks for the clarification, although what I said wasn't exactly wrong...doesn't hurt to be specific.
 
Nice Job MS/Intel.

I wonder how much Intel paid Microsoft for that "blunder".

So it was AMD fault after all...

http://www.pcgamer.com/microsoft-po...ectre-and-meltdown-patches-bricking-some-pcs/
https://www.theverge.com/2018/1/9/1...tdown-spectre-security-updates-amd-pcs-issues
https://arstechnica.com/gadgets/201...osoft-suspend-spectre-patch-for-amd-machines/

Microsoft has received reports of some AMD devices getting into an unbootable state after installation of recent Windows operating system security updates. After investigating, Microsoft determined that some AMD chipsets do not conform to the documentation previously provided to Microsoft to develop the Windows operating system mitigations to protect against the chipset vulnerabilities known as Spectre and Meltdown
 
Both AMD and Microsoft are at fault. AMD should have provided accurate documentation, Microsoft should have tested the patches before releasing them (either themselves, through partners like AMD, or via beta channels).
 
Both AMD and Microsoft are at fault. AMD should have provided accurate documentation, Microsoft should have tested the patches before releasing them (either themselves, through partners like AMD, or via beta channels).
On hardware that old? Yikes.
 
So compatibility goes out the window because of spectre but we are still on x86 / x64 why? Give me a break.
 
Both AMD and Microsoft are at fault. AMD should have provided accurate documentation, Microsoft should have tested the patches before releasing them (either themselves, through partners like AMD, or via beta channels).

Ok, AMD fault is providing incorrect documentation to Microsoft; whereas Microsoft fault was to trust AMD in this.
 
Ok, AMD fault is providing incorrect documentation to Microsoft; whereas Microsoft fault was to trust AMD in this.
They just both need to get act together and fix the issue before becomes more of a major headache.
 
Ok, AMD fault is providing incorrect documentation to Microsoft; whereas Microsoft fault was to trust AMD in this.
The Verge sees this as typical buck passing, however, there is in the quote below from poster "Reflex" there about noted poor documentation of chipset work in previous generations. Go to excuse and buck passing? You be the judge.
"Having worked on the MS side of platform engineering in the past I am in no way surprised. I like AMD, I've usually run AMD unless untenable. But their chipset work was very poorly documented and the bugs we ran into were usually due to poor assumptions we had to make in the lack of better information. The speed of these patches unfortunately would have the risk of exposing this issue (vs a longer cycle which would give time for back and forth with AMD/additional testing), and that seems to have been the case here..." -Reflex
 
They just both need to get act together and fix the issue before becomes more of a major headache.

They are

Update: AMD has released the following statement about the issue. "AMD is aware of an issue with some older generation processors following installation of a Microsoft security update that was published over the weekend. AMD and Microsoft have been working on an update to resolve the issue and expect it to begin rolling out again for these impacted shortly."
 
Back
Top