- People were saying that chipset drivers fixed things...well, not really...it is all about Windows! I have had it fixed since at least 5 Dev versions ago...
The L3 thingy is Windows related. The Chipset update adressed the CPPC2 State BugID: hhlxry4
People got the l3 cache fixed as well with chipset drivers...maybe they did bring some windows update togetherID: hhm1awm
No, i think you got that wrong. The windows update is available to the public since 20.10.21 Chances are high that people rebooted (needed for the chipset driver) and windows update did its thing.ID: hhmwh82
You got that wrong, sorry you been down voted by that, typical mistake thanks to these companies can't communicate things properly to us
I read the chipset fixed the prefered core, so it affect other things not the L3 cache (which is fixed in a windows update instead).ID: hhlxpu1
Of course it did, still, the CPCC preferred cores were already fixed on dev versions. On early versions CSGO was having way more FPS on windows 10 for example, and now it is even a bit better on Windows 11
your bandwidth is still all pver the place tho, before and afterID: hhmwihn
Is there variance in results without the updated drivers? I've seen consecutive benchmarks bounce all over the place.
Thats still not fixed win10 L3 had 600+gb/s bandwidth also 10ns. You can double click on those values to test separately one preferred and results inconsistentID: hhmwhl9
Win10 never had 900+ with a 5600x lol
So you actually lost 100GB/s bandwidth after updating chipset drivers thenID: hhmwaru
Aida64 bench is very "variable" on l3 cache
The chipset driver fixes performance for CPUs with more than 8 cores.ID: hhlxm6g
That is not only that, i don't know where you got that info. People with lower end CPUs got a big fix by using the new chipset drivers on the released windows 11 version, what I'm saying is that even without the chipset drivers, dev versions have the same results, meaning that it has to do with a windows update that was maybe included with the chipset drivers and not the chipset drivers themselvesID: hhlxzl7
“Performance impact may be more detectable in >8-core processors above 65W TDP”
That why smart people will install W11 after 1-2 years while other will be non paid OS testers.ID: hhlxub4
You don't need to pay at all for Windows, so your argument is quite invalid. That's the same as complaining about something you got for freeID: hhm905m
If its free you're the product not the customer.ID: hhly2vk
You pay it with your free wasted ime because Microsoft likes free testers like you.
this may be a dumb question but does anybody know how to update the chipset drivers? do i have to delete old ones? If so, how?ID: hhmwcvw
Uninstall them via control panel, restart, install new onesID: hhn2p23
I just run the new installer.
Dev channel CU has just been released via Win update--today 10/22, and it fixed the L3 bug for me.
After the CU, the build # is 22483.1011.