Home > Markets > AMD Releases Statement on Windows 10 Thread Scheduler Conflict

AMD Releases Statement on Windows 10 Thread Scheduler Conflict

By March 15, 2017 at 7:53 am
AMD has issued a statement about the Windows 10 Scheduler conflict (Photo : Neilson Barnard/Getty Images for Dell)

Advanced Micro Devices (AMD) launched its first three Ryzen CPUs of the Zen architecture two weeks ago, on Mar. 2, 2017. The Ryzen 7 CPUs clearly performs better with most applications and costs lesser than their Intel counterparts.

This has put AMD back on the CPU business. It is also expected that this will most likely even the playing field in months to come with Ryzen 5, Ryzen 3, and Naples (AMD's server CPUs).

On the other part, enthusiasts have posted that the Ryzen 7 CPUs are sluggish compared to Intel CPUs when it comes to 1080p gaming. However, AMD stated that games today are still not optimized for AMD CPUs and is hopeful that the gaming performance will improve in time as developers become familiar with the Zen architecture.

However, there is an issue concerning the new Ryzen CPUs and the Windows 10 bug which users believe to have throttled the performance of Ryzen. Because AMD's Zen architecture is new, there have been a lot of issues reported with the Windows Thread Scheduler that is causing the Ryzen CPUs to perform slower than expected. CPU testers noticed that the Ryzen benchmark results were significantly higher when simultaneous multithreading (SMT) was disabled.

 Microsoft acknowledged this issue and is currently working on a solution for the problem. This is great news for Ryzen as Windows takes on the issue and will take advantage of Ryzen's true potential. The SMT issue isn't new as it also occurred during Intel's introduction to their HyperThreading technology.

AMD released a statement addressing the problem. "We have investigated reports alleging incorrect thread scheduling on the AMD Ryzen processor," the company said. "Based on our findings, AMD believes that the Windows 10 thread scheduler is operating properly for 'Zen', and we do not presently believe there is an issue with the scheduler adversely utilizing the logical and physical configurations of the architecture."

Like Us on Facebook