Microsoft Kernel Patch CPU Before and After Benchmarks Thread


Recommended Posts

  On 09/01/2018 at 05:36, adrynalyne said:

Maybe? This isn't my forte. As it was explained to me, it matters if it is x86 code instructions being called with sys calls. The GPU isn't x86 as far as I know.

Expand  

This certainly is not a problem how processor executes x86 code. It is a problem here how user mode app communicates with the OS kernel and how processor handles that matter. All requests for hardware (graphics, disk, memory access) must be passed to the OS which then executes them. Apps do not write directly to GPU . They use OS to handle these calls which then calls graphics driver (at the OS kernel level) which then writes data and commands to the GPU. Therefore I think there is a great chances that these fixes affect 2D graphics as well as other data intensive tasks.

 

Here is the security problem (as far as I understand): cpu allowed user mode app to gain access to OS kernel data, which it should never do. CPU does not handle OS and user mode isolation securely enough.

 

Intel (and others) have used a "shortcut" to speed up things and created a security flaw which is severe.

 

But I must say I was amazed that the effect of this fix was so huge at my Lenovo Thinkpad T440s laptop. Did not expect that much. Maybe Lenovo will provide fixes to the drivers which will help here.

  On 09/01/2018 at 09:25, Jampe said:

Here are my results. FIrst test was right before update. After update I ran tests 3 times since I could not believe my eyes. Results are consistent. PC is Lenovo thinkpad t440s model 20ARS04W00

PerfRes1.gif

Expand  

Disk and 2D Graphics really suffer. I hope neither Microsoft nor Intel will stop optimising their patches. As they are now, I won't be updating. In fact, I will try to find updated Windows 10 ISOs with December patches and archive them if I ever need to reinstall Windows.

On the Azure front we're seeing slowdowns on our legacy Azure VM's running SQL Server. We're having to scale up the VM's to cope with the slowdowns.

 

Obviously this is all being logged and the extra costs will be argued.

 

Not seeing the same impact on Azure SQL Servers, there is an impact but probably only 10% extra as opposed to the ~25% on the VM's.

 

To make matters worse, MS scheduled production VM's for updates then threw the date out the window and upgraded when they felt like it. We're talking multiple end clients productions systems going down for anywhere from 30 mins to 5 hours without warning. A cluster###### if ever there was one.

 

Read some of the comments on this Azure status. I won't say which is my real life account...

https://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/

 

Don't forget that these patches are only part of the fix. According to the articles I've read, a BIOS update will also be required to fully patch the fix. I presume this is where a lot of the slowdowns will come from.

  On 09/01/2018 at 10:54, Daedroth said:

Don't forget that these patches are only part of the fix. According to the articles I've read, a BIOS update will also be required to fully patch the fix. I presume this is where a lot of the slowdowns will come from.

Expand  

the bulk of dell systems should get a bios fix today.

guys the following CERT advisory has links to lots of affected platforms and products, including timescales for fixes from vendors.

 

https://www.us-cert.gov/ncas/alerts/TA18-004A

 

we are currently assessing the entire global enterprise (20k endpoints, 8k+ servers) and we have reached out to NetApp, Cisco and other suppliers of enterprise kit.

 

Were using the tack, if it has a CPU, its potentially susceptible until we are told otherwise (called due diligence).

 

NetApp have confirmed their SAN arrays are  not affected. They dont permit execution of 3rd party code. Awaiting confirmation about Cisco kit.

 

*UPDATE** Cisco have responded. A mixed bad, some products immune but the bulk are affected.

 

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel

 

 

Asus have released the microcode fix/BIOS update for my S270 Strix H. 

 

https://www.asus.com/Motherboards/ROG-STRIX-Z270H-GAMING/HelpDesk_BIOS/

 

STRIX Z270H GAMING BIOS 1203
Improved DRAM compatibility.
Fixed SAMSUNG M.2 device issue.
Fixed SanDisk M.2 device issue.
Fixed AMD SSD device issue.
Fixed SteelSeries Keyboard issue.
Update CPU MicroCode.

 

Cinebench 4D BEFORE Win patch

CPU Benchmark = 966CB

OpenGL Bench = 140 FPS

AFTER

CPU Benchmark = 975CB ???

OpenGl Bench = 149.95 FPS ???

NVidia Driver update

CPU Benchmark = 962CB

OpenGL Bench =147.64FPS

Post Bios UPD

CPU Benchmark=942CB

OpenGL Bench=147.36

 

3D Mark timespy extreme BEFORE

3998

AFTER

3997 ????

NVidia Driver Update

3971

Post Bios UPD

3955

 

Novabench 

2713

After

2703

NVidia Driver update

2677

Post Bios UPD

2618

 

RealBench BEFORE

Image Editing 212,486/ Time 25.0745

Encoding 93,501/time 56.9829

OpenCL 113,529/ Ksamples per sec 20877

Heavy Multitasking 110,647

Time 68.9761

System Score 132,540

RealBench AFTER

Image Editing 208.830/Time 25.5135

Encoding 92,841/time 57.3881

OpenCL 113,529/ Ksamples/sec 20922

Heavy Multitasking 103,867/Time 73.4779

System Score 129,766

Post NVidia 

Image Editing 108,788/ Time 48.9757

Encoding 84,939/time 62.7273

OpenCL 113,529/ Ksamples per sec 20948

Heavy Multitasking 99,848

Time 76.4357

System Score 101,776 

Post Bios UPD

Image Editing 91,665/ Time 58.1242

Encoding 80,259/time 66.3843

OpenCL 112,996/ Ksamples per sec 20798

Heavy Multitasking 94,712

Time 80.5809

System Score 94,908

 

Hmm taking it with a pinch of salt, as i noticed post BIOS upd i left the OC as auto, so its at 4.37Ghz, not 4.5Ghz I benched with before...DOH

 

ill redo it tomorrow and update.

  On 09/01/2018 at 22:47, Mando said:

Asus have released the microcode fix/BIOS update for my S270 Strix H. 

 

https://www.asus.com/Motherboards/ROG-STRIX-Z270H-GAMING/HelpDesk_BIOS/

 

STRIX Z270H GAMING BIOS 1203
Improved DRAM compatibility.
Fixed SAMSUNG M.2 device issue.
Fixed SanDisk M.2 device issue.
Fixed AMD SSD device issue.
Fixed SteelSeries Keyboard issue.
Update CPU MicroCode.

 

Cinebench 4D BEFORE Win patch

CPU Benchmark = 966CB

OpenGL Bench = 140 FPS

AFTER

CPU Benchmark = 975CB ???

OpenGl Bench = 149.95 FPS ???

NVidia Driver update

CPU Benchmark = 962CB

OpenGL Bench =147.64FPS

Post Bios UPD

CPU Benchmark=942CB

OpenGL Bench=147.36

 

3D Mark timespy extreme BEFORE

3998

AFTER

3997 ????

NVidia Driver Update

3971

Post Bios UPD

3955

 

Novabench 

2713

After

2703

NVidia Driver update

2677

Post Bios UPD

2618

 

RealBench BEFORE

Image Editing 212,486/ Time 25.0745

Encoding 93,501/time 56.9829

OpenCL 113,529/ Ksamples per sec 20877

Heavy Multitasking 110,647

Time 68.9761

System Score 132,540

RealBench AFTER

Image Editing 208.830/Time 25.5135

Encoding 92,841/time 57.3881

OpenCL 113,529/ Ksamples/sec 20922

Heavy Multitasking 103,867/Time 73.4779

System Score 129,766

Post NVidia 

Image Editing 108,788/ Time 48.9757

Encoding 84,939/time 62.7273

OpenCL 113,529/ Ksamples per sec 20948

Heavy Multitasking 99,848

Time 76.4357

System Score 101,776 

Post Bios UPD

Image Editing 91,665/ Time 58.1242

Encoding 80,259/time 66.3843

OpenCL 112,996/ Ksamples per sec 20798

Heavy Multitasking 94,712

Time 80.5809

System Score 94,908

 

Hmm taking it with a pinch of salt, as i noticed post BIOS upd i left the OC as auto, so its at 4.37Ghz, not 4.5Ghz I benched with before...DOH

 

ill redo it tomorrow and update.

Expand  

Mando, is RealBench only for ASUS gaming boards bench utility? Thx for the update, btw :)

  On 10/01/2018 at 13:44, Yogurth said:

Mando, is RealBench only for ASUS gaming boards bench utility? Thx for the update, btw :)

Expand  

not 100% its via ROG aspect.

 

give it a whirl, it may work

http://dlcdnmkt.asus.com/rog/RealBench_v2.56.zip?_ga=2.161564219.660284626.1515594169-1054940240.1499777541

 

 

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

    • No registered users viewing this page.
  • Posts

    • Microsoft reportedly planning to lay off thousands of employees, mostly in sales by Usama Jawad Back in May 2025, Microsoft decided to lay off 3% of its workforce, which amounted to roughly 6,000 employees. It claimed that this decision allowed it to implement better organizational changes in a "dynamic marketplace". Now, a new report claims that the Redmond tech firm is planning to lay off thousands more next month. Citing unnamed sources, Bloomberg reports that as the company continues investing heavily in its AI ventures, it is about to announce layoffs of thousands of workers as early as next month. This reduction in workforce will primarily affect sales teams, but they won't be the only ones affected. That said, the sources did mention that the timing for this announcement may change. This move, if true, won't be entirely surprising. In April 2025, Microsoft announced that it will be relying more on third-party firms to sell its software to small- and medium-sized customers. It's currently unclear how many employees will be impacted by this change, but even if the layoff percentage is in the single digits, it would still be significant as it would be impacting the professional careers of thousands. The May 2025 layoffs primarily impacted engineering and product teams. The other major round of layoffs prior to this was the decision to eliminate 10,000 jobs back in January 2023. Those represented 5% of the total workforce at that time, with numerous teams, including the one leading Mixed Reality (MR) efforts, being heavily impacted. It is interesting to note that if the timing of the announcement for layoffs is accurate, it would be soon after Microsoft closes its fiscal year at the end of June 2025. Although we'll get financial reports for the latest quarter soon after too, one has to wonder what the human cost of profit is, as Microsoft continues to report billions of dollars in revenue every quarter. Source: Bloomberg (paywall)
    • Ah .. lockout for suspicious activity. I bet they uploaded the SanDisk utility detected as malware
    • Microsoft 365 will soon disable outdated authentication protocols for file access by Usama Jawad On a fairly regular basis, Microsoft disables outdated protocols that are used to access its services. In the past few years, the company has deprecated Basic Auth in Exchange Online and cut access to Outlook for third-party apps relying on this protocol. Now, it has decided to get rid of old authentication protocols for file access across Microsoft 365 services. As reported by Bleeping Computer, Microsoft has posted a message on its Microsoft 365 Admin Center. Starting from mid-July 2025, the company will begin disabling legacy authentication protocols used to access files across Microsoft 365 and Office apps, SharePoint, and OneDrive. Essentially, applications or services which use the Relying Party Suite (RPS) or FrontPage Remote Procedure Call (FPRPC) will to perform browser-based authentication to perform open operations on Office files will no longer be able to do so. As expected, this is primarily being done to improve the cybersecurity posture of various services. Microsoft states that RPS can be brute-forced and phished with relative ease as it is fairly outdated. Similarly, FPRPC is typically used for remote web page authoring and it is susceptible to exploitation through various vulnerabilities too. As such, both of these protocols will be disabled by default starting from mid-July 2025, with the rollout of this change targeting completion by August 2025. The Redmond tech giant will update the protocol baseline by default without mandating any licensing changes for customers. In addition, once these modifications are rolled out, Microsoft 365 will require admin consent to get third-party access to files and sites. IT admins can view the guidance available here to configure admin consent workflows. Microsoft says that these changes align with the principles of its Secure Future Initiative (SFI). Earlier today, it announced the rollout of improved security defaults for Windows 365 citing the same reasons too.
    • This is how you kill your own business.
  • Recent Achievements

    • First Post
      Fuzz_c earned a badge
      First Post
    • First Post
      TIGOSS earned a badge
      First Post
    • Week One Done
      slackerzz earned a badge
      Week One Done
    • Week One Done
      vivetool earned a badge
      Week One Done
    • Reacting Well
      pnajbar earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      705
    2. 2
      ATLien_0
      283
    3. 3
      Michael Scrip
      216
    4. 4
      +FloatingFatMan
      194
    5. 5
      Steven P.
      130
  • Tell a friend

    Love Neowin? Tell a friend!