• 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

nashathedog

nashathedog

nashathedog

Permabanned
Joined
12 Sep 2013
Posts
9,221
Location
Knowhere
Microsoft has stopped them for now, blaming AMD documentation.

https://www.engadget.com/2018/01/09/microsoft-halts-meltdown-spectre-amd-patches/

According to reports from users, the unbootable problem appears to happen with specific AMD models. "I have older AMD Athlon 64 X2 6000+, [and] after installation of KB4056892 the system doesn't boot, it only shows the Windows logo without animation and nothing more," said one user. The same issue was confirmed by other Athlon and Sempron-equipped PC owners. Microsoft has stopped them for now, blaming AMD documentation.
Click to expand...

Because it's never their fault right?
 
sideways14a said:
Crikey an x2, is it even a legit supported processor under windows 10?
It must be fun to run, if you like waiting for things.
Click to expand...
The Meltdown update (which theoretically shouldn't do anything on AMD CPUs to begin with) applies to Windows 7 and 8 too, both of which still officially support non-Ryzen AMD CPUs.
 
Posted this in the "other" thread....

MS have identified the issue, as noted here.....



https://support.microsoft.com/en-us...security-update-block-for-some-amd-based-devi

According to Microsoft, some AMD PCs are in an unbootable state after installing the recent patches because their chipsets "do not conform" to the documentation that was provided to Microsoft when it was developing mitigation techniques against Meltdown and Spectre. In simpler terms, AMD's provision of incorrect and/or incomplete information regarding the CPU has resulted in potentially thousands of machines being rendered unusable.

As such, Microsoft is temporarily pausing Windows updates to AMD processors impacted by the issue. These updates include:

  • January 3, 2018—KB4056897 (Security-only update)
  • January 9, 2018—KB4056894 (Monthly Rollup)
  • January 3, 2018—KB4056888 (OS Build 10586.1356)
  • January 3, 2018—KB4056892 (OS Build 16299.192)
  • January 3, 2018—KB4056891 (OS Build 15063.850)
  • January 3, 2018—KB4056890 (OS Build 14393.2007)
  • January 3, 2018—KB4056898 (Security-only update)
  • January 3, 2018—KB4056893 (OS Build 10240.17735)
  • January 9, 2018—KB4056895 (Monthly Rollup)
Click to expand...

^^^^ Found the above on Neowin....

https://www.neowin.net/news/heres-w...stalling-microsofts-patches#comment-598155594
 
How does it even happen that the hardware and the documentation pertaining to it don't align? Seems like a giant mistake (although confusingly one that has had little impact until now).
 
DragonQ said:
The Meltdown update (which theoretically shouldn't do anything on AMD CPUs to begin with) applies to Windows 7 and 8 too, both of which still officially support non-Ryzen AMD CPUs.
Click to expand...

Yes that is true, i was however thinking these crashing issues were a ten only thing. I must be preconditioned to expect more issues on ten than normal :p
 
x-st said:
How does it even happen that the hardware and the documentation pertaining to it don't align? Seems like a giant mistake (although confusingly one that has had little impact until now).
Click to expand...

Its pretty typical of AMD - and as much as like to hate on MS especially over updates I can believe the fault lies on AMD's side on this one.

EDIT: Though someone has a point in the other thread that MS shouldn't have just assumed it would work because it was in the documentation they should have tested it... but yeah MS lost their ways a couple of years back or so so good luck with that.
 
jigger said:
Of course you do ;)
Click to expand...

For instance up until fairly recently AMD used to report all kinds of texture formats as supported in GPU caps some of the lesser used ones would appear to accept writes fine - but try and render from them and you'd find stuff like the driver crashing, only getting black or corrupt data out or missing a supposedly supported alpha channel, etc. despite their documentation claiming they worked.

Though they've been better of late they still seem to have a culture of claiming things work in the first instance irregardless and only bothering about it if someone finds something is broken.
 
Rroff said:
For instance up until fairly recently AMD used to report all kinds of texture formats as supported in GPU caps some of the lesser used ones would appear to accept writes fine - but try and render from them and you'd find stuff like the driver crashing, only getting black or corrupt data out or missing a supposedly supported alpha channel, etc. despite their documentation claiming they worked.

Though they've been better of late they still seem to have a culture of claiming things work in the first instance irregardless and only bothering about it if someone finds something is broken.
Click to expand...

Of course this all AMD's fault. Well from your point of view it's always AMD's fault.
 
@Roff Even if what Microsoft say is true they obviously had not tested thier own fixes because had they done any sort of QA they wouldn't have this problem.

The responsibility stops with with the people making the software, that's Microsoft. The fact that Microsoft are trying to lay the blame entirely on AMD despite their own QA responsibility speaks volumes and you have fallen for their PR hook line and sinker.
 
jigger said:
Funny how you still make the odd attempt to look impartial. Stranger still is you cast insults in the same post.
Click to expand...

I make no attempt or claim to be impartial. Another example of your preconceived perception versus the reality - I've said many time if it comes to one or the other I generally side with nVidia over AMD.

There is nothing insulting in the truth unless you twist it that way - AMD doesn't have the performance, supply or margins currently to challenge the way nVidia are doing things even if AMD wanted to do things better for consumers - that is the hard cold facts not an insult.
 
Rroff said:
I make no attempt or claim to be impartial. Another example of your preconceived perception versus the reality - I've said many time if it comes to one or the other I generally side with nVidia over AMD.

There is nothing insulting in the truth unless you twist it that way - AMD doesn't have the performance, supply or margins currently to challenge the way nVidia are doing things even if AMD wanted to do things better for consumers - that is the hard cold facts not an insult.
Click to expand...

Now you're just trying to shoehorn nVidia vs AMD expansion arguments into this thread, derailing it.

Stick to the topic, Microsoft are at least equally responsible for Quality Assurance as AMD are for providing accurate data, Clearly Microsoft did not do any QA what-so-ever, had they they wouldn't have had to withdraw their patches and PR blame AMD for it.
 
You must log in or register to reply here.
Back
Top Bottom