Don't trust MS update is what I got from it!
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Microsoft's 'Meltdown' updates are reportedly bricking non Ryzen AMD PCs
- Thread starter nashathedog
- Start date
Don't trust MS update is what I got from it!
Well until we hear from AMD it's simply Microsoft claiming this is true.
If you just bricked a few thousand systems you are going to be pretty defensive. I've made mistakes before and I can definitely spin it to be someone else's fault (if only someone has told me about x and y, I wouldn't have done that).
If you just bricked a few thousand systems you are going to be pretty defensive. I've made mistakes before and I can definitely spin it to be someone else's fault (if only someone has told me about x and y, I wouldn't have done that).
Only just noticed this thread, but just to add my post from the Windows section: https://forums.overclockers.co.uk/posts/31502760/
Seems the affected CPUs are K8 based, so K10 CPUs and beyond should be completely fine. No issues here on my Ryzen. I could test it on my PII chip but I sold that years ago
.
Seems the affected CPUs are K8 based, so K10 CPUs and beyond should be completely fine. No issues here on my Ryzen. I could test it on my PII chip but I sold that years ago
.
Soldato
- Joined
- 6 Sep 2016
- Posts
- 11,629
Well if a update doesn't allow you to boot, you won't be able to get infected.
Seems to be a great idea.
Seems to be a great idea.
Associate
- Joined
- 31 Aug 2017
- Posts
- 2,209
How many folk are wanting to patch on a 10 or so year old pc anyway?
Most ancient bits of crap i see like that dont work right anyway, are filled to the brim with spyware, toolbars and crap, no AV or none working right and patches are the kind of thing you use for an addiction.
Most ancient bits of crap i see like that dont work right anyway, are filled to the brim with spyware, toolbars and crap, no AV or none working right and patches are the kind of thing you use for an addiction.
Are you honestly suggesting that Microsoft should test every patch using every chipset/CPU combination from the last decade?
I think in this instance we can forgive MS for just making it according to the specification given to them by AMD and expecting it to work.
*EDIT*
To use an analogy, if Intel/AMD bring out a new socket and send schematics to all the heatsink/waterblock vendors who then build heatsinks/water blocks to fit as per the schematic, but they don't fit because Intel/AMD put a 6 instead of a 9 by mistake or something, the heatsinks/blocks not fitting is Intel/AMD's mistake.
And this is even more time critical as it's a patch for a huge security issue.
- Joined
- 12 Sep 2013
- Posts
- 9,221
- Location
- Knowhere
- Joined
- 12 Sep 2013
- Posts
- 9,221
- Location
- Knowhere
Isn't it an only for Intel patch though or is this the one AMD are susceptible too as well?
Erm YES! that is a part of Quality Assurance, anyone and everyone has to test the software they make on the system they intend it to run on, that's completely normal.
Spectre affects both.
Software: Yes.
High priority emergency security patch: No.
You don't spend months testing something of this level to check if the information from vendors is erroneous.
It doesn't take months, put enough people on it it takes hours.
Actually yes you do to avoid bricking your customers hardware, (you always test your software, ALWAYS) Microsoft didn't do that and as a result they bricked their customers hardware, all be it its 10 year old hardware the buck non the less stops with Microsoft, it is their creation that caused the problem
I feel obliged to point out this guy is a raging Linux fanboy
He is right tho.
You can see why!
You think they can source/test every viable chipset cpu combination from the last decade in a matter of hours?
That's getting a Mac-10 in ten minutes territory
They don't source hardware specifically for one patch, they make software patches all day everyday and QA it, they already have the hardware.You think they can source/test every viable chipset cpu combination from the last decade in a matter of hours?
That's getting a Mac-10 in ten minutes territory
There's a reason for the nickname Wintel ya know
Its in their own interest to QA for AMD too, unless they are incredibly stupid enough not to realise they run the risk of bricking customers PC's if they don't, oh..... wait a minute
Still the argument is "its all AMD's fault" while AMD may or may not have provided the correct data to Microsoft AMD do have a responsibility there, that does not excuse Microsoft putting out faulty patches they clearly did not QA.
Not half.
I think this has proved more than ever that MS's approach to updates with 10 is completely stupid - it might have been a little more defendable if they had a sizeable hardware lab and the people to rapidly do a reasonable level of testing across generations of hardware and configuration but they clearly aren't setup for that - at least nothing close to the level for this kind of update approach and even then it would still be pretty stupid given that the OS is not real life context aware.