Share via

AMD Processor Decreased Performance after Latest Windows 11 Update (KB5006746)

Anonymous
2021-10-23T09:43:10+00:00

This Windows update was supposed to fix degraded performance with AMD processors. Not sure if it did actually fix the "L3 cache latency bug" but my AMD Ryzen 7 5800H chip in a Lenovo Legion 5 gen 6th laptop, has got even worse.

Windows 10 Cinebench R23 score:

CPU (Multi Core) 13030 pts

CPU (Single Core) 1401 pts

Windows 10 Time Spy Score:

Graphics: 11,116

CPU: 8,988

Windows 11 after latest Update Cinebench R23

CPU (Multi Core) 12230 pts

CPU (Single Core) 1348 pts

Windows 11 after latest Update Time Spy

Graphics: 11, 110

CPU: 8,631

I also downloaded AMD Chipset Software 3.10.08.506 to fix issue but didn't seem to make much difference on scores for these. I also have turned off Core Isolation.

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-10-25T14:10:31+00:00

    The two updates I stated above, which decreased performance, Microsoft and AMD said fixed the performance issues. They also said the previous patches fixed the performance issues but didn't, just like these didn't. I've now restored back to Windows 10 and that has fixed the performance issues.

    I don't think I'll be going back to Windows 11 anytime soon.

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-10-23T10:08:14+00:00

    I've actually heard about this issue it's actually the reason why my gaming PC is still Running Windows 10 instead of windows 11 because I'm using a AMD 3600 or AMD Ryzen 5 would be the name of my processor although i have no problems running it on my lap top because it's intel however from what I've read into on the situation i found that AMD is aware of the problem and they are working with Microsoft to try and fix the issue

    0 comments