I am taking bets that the next patch Tuesday (the 14th this month) is gonna be an epic adventure worthy of popcorn.

eRe4s3r wrote on Mar 10, 2017, 20:50:
I am taking bets that the next patch Tuesday (the 14th this month) is gonna be an epic adventure worthy of popcorn.

Or it will be a hotfix like they did with bulldozer.

Oh AMD....LOL

I have NEVER needed a patch to allow my Intel CPU to work like it's supposed to.

As usual, more excuses and smoke-and-mirrors from team red.

SirKnight wrote on Mar 10, 2017, 22:36:
Oh AMD....LOL

I have NEVER needed a patch to allow my Intel CPU to work like it's supposed to.

As usual, more excuses and smoke-and-mirrors from team red.

What? You really don't remember the early days of Intel hyper threading, when CPU reviewers had to disable HT to get the 'proper' performance in games?

It's the same thing. New CPU, new way of hyperthreading, new bugs.

mag wrote on Mar 10, 2017, 23:30:

SirKnight wrote on Mar 10, 2017, 22:36:
Oh AMD....LOL

I have NEVER needed a patch to allow my Intel CPU to work like it's supposed to.

As usual, more excuses and smoke-and-mirrors from team red.

What? You really don't remember the early days of Intel hyper threading, when CPU reviewers had to disable HT to get the 'proper' performance in games?

It's the same thing. New CPU, new way of hyperthreading, new bugs.

That wasn't a scheduler issue though. That was HT just not being fully baked. It took Intel until the Nehalem architecture to get it right.

AMD should have worked with Microsoft in advance on this, not like they didn't have fucking years of delays on the launch.

Title says Microsoft Windows bug.
Article says Microsoft is working on a fix for Windows.
2 posters mention HT issues have happened before with both AMD and Intel involving Microsoft.

Yet the lynch mob wants to storm AMD.

Dacote wrote on Mar 11, 2017, 08:46:
Title says Microsoft Windows bug.
Article says Microsoft is working on a fix for Windows.
2 posters mention HT issues have happened before with both AMD and Intel involving Microsoft.

Yet the lynch mob wants to storm AMD.

Well you would think Q&A would have found and fixed such issues before release, but far more interesting is that Ryzen or the Mainboards or Windows have a really wonky RTC bug (Ryzen sleep bug if you are curious) when you return your OS from sleep, timers slow down breaking literally everything in the OS, and fudging benchmark numbers to boot (since timer is slower = less time passed = higher numbers). If you return your OS from sleep and you notice weird happenings (like clock being totally wonky, video stuttering and encryption failing) then you know are affected..

We can thank MS for that one as well... RTC = real time clock

This comment was edited on Mar 11, 2017, 11:18.

That wasn't a scheduler issue though. That was HT just not being fully baked.

People should stay out of these threads if you know fuck all about hardware. You aren't fooling anyone!

Title says Microsoft Windows bug.
Article says Microsoft is working on a fix for Windows.
2 posters mention HT issues have happened before with both AMD and Intel involving Microsoft.

Yet the lynch mob wants to storm AMD.

Maybe the "lynch mob" understands hardware a little better than you do. There is no "bug" in Windows, it detects hyperthreaded cores exactly the way it is supposed to. Of course Microsoft is working on a fix, they have to update the OS to detect these new Ryzen cores properly.

If I release a new piece of hardware tomorrow without telling MS how it works, is it their fault that their OS doesn't magically detect my new hardware calls... or mine?

It's clearly AMD's fault for not getting the OS support inline before launching their fucked up product. It's clearly not MS's fault that AMD released hardware that doesn't fucking work right. At no point could AMD have ever thought they were getting the full performance of their new CPU when they released it to reviewers.

Maybe it's time for some introspective, why are you so willing to make excuses for AMD for fucking this up? We all want better competition in the CPU market, but MS isn't your personal punching bag just because you want something to be true..

Re: Microsoft Windows Bug Is Holding Back AMD Ryzen

You're holding me back, Obi-Wan!

We all know how that ended... AMD will fall on its knees and give in to the evintel empire!

descender wrote on Mar 11, 2017, 11:40:
snip

Good info and well put.
The bug has been fixed in the latest Linux kernal and Microsoft will hopefully have a patch out "soon" for Windows.

descender wrote on Mar 11, 2017, 11:40:
It's clearly AMD's fault for not getting the OS support inline before launching their fucked up product. It's clearly not MS's fault that AMD released hardware that doesn't fucking work right. At no point could AMD have ever thought they were getting the full performance of their new CPU when they released it to reviewers.

Maybe it's time for some introspective, why are you so willing to make excuses for AMD for fucking this up? We all want better competition in the CPU market, but MS isn't your personal punching bag just because you want something to be true..

you are naively assuming that MS would jump to attention and immediately address these concerns from AMD, precisely adhering to AMDs timetable, or responding in a reasonable way... but in the world of corporate industrialization, it doesnt work like that.

AMD may have a certain need to release this product now, but MS is in no way obligated to enable them to meet this specific deadline... its quite possible AMD told MS about this issue and MS said "yeh yeh we'll get right on that... eventually" and AMD was forced (by their own timetable) to release this product before MS was ready to fully support it

these kinds of back end dealings arent going to be public, for good reason.. namely the "optics" (lol)

mag wrote on Mar 10, 2017, 23:30:

SirKnight wrote on Mar 10, 2017, 22:36:
Oh AMD....LOL

I have NEVER needed a patch to allow my Intel CPU to work like it's supposed to.

As usual, more excuses and smoke-and-mirrors from team red.

What? You really don't remember the early days of Intel hyper threading, when CPU reviewers had to disable HT to get the 'proper' performance in games?

It's the same thing. New CPU, new way of hyperthreading, new bugs.

Not the same thing at all and has absolutely nothing to do with "early days" or a bug. To this very day, you will get better performance in many games by disabling HT. Same thing for AMD and SMT on Ryzen by the way. Many of the Ryzen reviews from last week also had tests with SMT disabled which yielded a small boost in performance in most games.