Microsoft Kernel Patch CPU Before and After Benchmarks Thread


Recommended Posts

Just now, Mockingbird said:

Which processor?

 

On Intel processors, Kernel VA shadowing is disabled if incompatible Anti-Virus is detected.

 

On AMD processors, Kernel VA shadowing is disabled.

Ryzen 1700.

2 minutes ago, Mockingbird said:

I don't even know what you are talking about.

Clearly.

 

Otherwise you wouldn't have argued with me about the AMD user claiming performance loss when there was none, and would have also corrected yourself after seeing @Yogurth's link included post microcode update, which tends to clash with your posted post-microcode update screenshot,. Of which it seems to be a rather odd one-off, like the AMD user. Hence I posted what I did.

Just now, adrynalyne said:

Clearly.

 

Otherwise you wouldn't have argued with me about the AMD user claiming performance loss when there was none, and would have also corrected yourself after seeing @Yogurth's link included post microcode update, which tends to clash with your posted post-microcode update screenshot,. Of which it seems to be a rather odd one-off, like the AMD user. Hence I posted what I did.

I don't thing there were many AMD users claiming performance because I have said, Kernel VA shadowing is disabled.

Just now, Mockingbird said:

I don't thing there were many AMD users claiming performance because I have said, Kernel VA shadowing is disabled.

Just like there aren't many showing a 21% performance hit after microcode update. I'm glad we are now on the same page.

Just now, Mockingbird said:

There hasn't been any microcode update from AMD (for these issues).

I didn't say there was. Go back and look at what I typed.

The AMD user was an example of a one-off, and most likely incorrect conclusion.

Your microcode update results are likely the same, which is why we need more microcode testing results.

Which @Yogurth supplied and confirmed my suspicions.

1 minute ago, adrynalyne said:

I didn't say there was. Go back and look at what I typed.

The AMD user was an example of a one-off, and most likely incorrect conclusion.

Your microcode update results are likely the same, which is why we need more microcode testing results.

Which @Yogurth supplied and confirmed my suspicions.

The "AMD user"?

 

Which "AMD user"?

7 minutes ago, Mockingbird said:

The "AMD user"?

 

What "AMD user"?

Really? I linked the reddit url in this thread if you want to go look. Specifically, this is what I said:

1 hour ago, adrynalyne said:

There hasn’t been enough testing with the microcode update to verify it. There is also a screenshot out there showing a massive performance hit after the meltdown patch on an AMD cpu. Just one that I saw. 

One-offs never tell the whole story.

 

Edit: I posted it to a similar but different thread that spawned this one. Let me go find it.

Edited by adrynalyne
1 minute ago, adrynalyne said:

Really? I linked the reddit url in this thread if you want to go look. Specifically, this is what I said:

One-offs never tell the whole story.

Why would someone with an Intel Core i7-8700K be called the "AMD user"?   Facepalm.

 

I think you mean the "Intel user".

Just now, Mockingbird said:

Why would someone with an Intel Core i7-8700K be called the "AMD user"?   Facepalm.

 

I think you mean the "Intel user".

No, you just don't understand what you are reading.

 

 

@Yogurthposted this.

Of which contains, this:

USPdAEX.png

 

3 minutes ago, Mockingbird said:

 

"I found one on Russian forum. Can be fake"

 

There you have it.

OMG, stop being so obtuse.

 

"Can be fake" --yeah, so can yours.

Thats why...wait for it...wait for it...we need more microcode testing. Your argument for performance loss increase from microcode update after the OS patch is based upon a single microcode update-enabled test you posted.

 

1 minute ago, adrynalyne said:

OMG, stop being so obtuse.

 

"Can be fake" --yeah, so can yours.

Thats why...wait for it...wait for it...we need more microcode testing. Your argument for performance loss increase from the OS patch is based upon a single microcode update-enabled test you posted.

 

Someone with a Core i7-8700K and a ASUS PRIME Z370-A can easily run update his//her BIOS and run Realbench 2.56.

 

What you have posted has no context

Just now, Mockingbird said:

Someone with a Core i7-8700K and a ASUS PRIME Z370-A can easily run update his//her BIOS and run Realbench 2.56.

 

What you have posted has no context

I'm done here because you are clearly trolling now.

 

I gave plenty of context for those who choose to see it. I'll try one last time and you can decide to be obtuse, or not. I don't care.

 

You posted a huge performance hit after microcode update. Just one. I believe it showed in the upwards of 21% performance loss?

Its not conclusive until the results can be verified and reproduced. That is just good investigation.

We've not seen enough evidence in bulk to verify how much a hit the microcode updates will actually have on performance.

@Yogurth posted results, upon which you said were without the microcode update. These conflicted with your 21% loss.

I explained, we need more microcode testing to verify the results of the performance hit (implying to what you posted). I gave an example of why more verification is needed because there was even an AMD user who claimed performance loss from the meltdown patch. No verification means its not really useful. Could it be fake? Yeah, it could. Could yours? Yeah they could. That iss why we need more testing.

@Yogurth later explained it was indeed was with microcode updates, also invalidating your claim, not by any fault of yours, but through the power of verification and further testing.

Then you invented this idiotic argument, of which I am done with.

 

I forgot to mention, there is an important bit of information in Techspot article for those who only checked results. Nvidia GPUs are most likely susceptible to meltdown attack and they are planning to issue a statement over this soon.

Just now, Yogurth said:

I forgot to mention, there is an important bit of information in Techspot article for those who only checked results. Nvidia GPUs are most likely susceptible to meltdown attack and they are planning to issue a statement over this soon.

Interesting. Nvidia GPUs aren't x86 or ARM, are they? Honest question, I don't know.

 

Just now, adrynalyne said:

Interesting. Nvidia GPUs aren't x86 or ARM, are they? Honest question, I don't know.

 

No idea either, but here is the quote from the article, if it helps... "On the GPU front, Nvidia is reportedly also affected, so there will be loads of additional tests to be done when "time comes. Our interpretation from Nvidia's blog is that they rely on CPU-like aggressive branch prediction on their GPU architectures. It's part of their performance gains over consecutive generations. The flaw appears to be the same as Intel CPUs, in that speculative operations occur without security checks first, as a secure design should be done."

So, I'm not sure if this has been covered (apologies if it has), but the Windows 10 Kernel patch is only half the story. We all need to apply BIOS updates to the various intel boards that we are using.

If you are worried about the performance hit on your intel PC, you need to re-test with the Windows 10 patch along side your motherboard manufacturers BIOS update that has the Intel CPU microcode update.

For those using Asus boards, they have annouced if your board has one of the following chipsets X299, Z370, Z270, Z170, B150, B250, H270, H170, H110, Q170, Q270 and finally X99 there should be an incoming BIOS update that contains the Microcode update (if its not already live).

Please see the following link for a full table of Motherboards, and the BIOS version containing the Microcode update: https://www.asus.com/News/V5urzYAT6myCC1o2

Hardware unboxed has done a benchmark video of a Z370 board with and without the latest Bios - all in all only a very small performance difference noticed in general. NVMe SSD performance does seem to be hit however:
https://www.youtube.com/watch?v=JbhKUjPRk5Q

Hope this helps.

2 minutes ago, Yogurth said:

I forgot to mention, there is an important bit of information in Techspot article for those who only checked results. Nvidia GPUs are most likely susceptible to meltdown attack and they are planning to issue a statement over this soon.

Are you sure?:

Quote

NVIDIA’s core business is GPU computing. We believe our GPU hardware is immune to the reported security issue and are updating our GPU drivers to help mitigate the CPU security issue. As for our SoCs with ARM CPUs, we have analyzed them to determine which are affected and are preparing appropriate mitigations. 

https://forums.geforce.com/default/topic/1033210/nvidias-response-to-speculative-side-channels-cve-2017-5753-cve-2017-5715-and-cve-2017-5754/

  • Like 2
3 minutes ago, LimeMaster said:

Like I said I do not know, I hope Techspot info is wrong, though Nvidia statement is already a few days older than the Techspot findings. Anything goes I guess.

Just now, Yogurth said:

Like I said I do not know, I hope Techspot info is wrong, though Nvidia statement is already a few days older than the Techspot findings. Anything goes I guess.

I'm just worried we'll see more performance drops if it turns out their GPUs are affected.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!