• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Intel bug incoming? Meltdown and Spectre exploits

Are we sure that on Windows, the fix that slows things down is disabled for Ryzen?
Yes, I saw someone post a screenshot on reddit of that power shell scrip that verifies whether the fixes are applied and kernel VA shadowing was disabled on Ryzen and marked as not necessary.
 
Not entirely true. The minimums of one user has tanked

Indeed.

I just finished running Rise of the Tomb Raider benchmarks, 1080p, very high preset, FXAA.

Unpatched:

  • Mountain Peak: 131.48 FPS (min: 81.19 max: 197.02)
  • Syria: 101.99 FPS (min: 62.73, max: 122.24)
  • Geothermal Valley: 98.93 FPS (min:76.48, max: 117.00)
  • Overall score: 111.31 FPS
Windows patch only:

  • Mountain Peak: 135.34 FPS (min: 38.21 max: 212.84)
  • Syria: 102.54 FPS (min: 44.22, max: 144.03)
  • Geothermal Valley: 96.36 FPS (min:41.35, max: 148.46)
  • Overall score: 111.93 FPS
Windows patch and BIOS update:

  • Mountain Peak: 134.01 FPS (min: 59.91 max: 216.16)
  • Syria: 101.68 FPS (min: 38.95, max: 143.44)
  • Geothermal Valley: 97.55 FPS (min:46.18, max: 143.97)
  • Overall score: 111.62 FPS
Average framerates don't seem affected.

https://np.reddit.com/r/pcmasterrac...nce_impact_of_windows_patch_and_bios/ds88idv/


Edit: I'll leave this here but just realised that with out a graph or the removal of outliers my statement is not entirely accurate.
 
Not entirely true. The minimums of one user has tanked



https://np.reddit.com/r/pcmasterrac...nce_impact_of_windows_patch_and_bios/ds88idv/


Edit: I'll leave this here but just realised that with out a graph or the removal of outliers my statement is not entirely accurate.

Seen as the averages were all exactly the same, and the mins vary wildly between unpatched, patched and patched with bios patch, i doubt that the brief lowest minimum has anything to do with anything other than some sort of brief hitch or mem cache type thing.
 

User also said they didn't notice it drop below 85, so lows could have been loading stutter.

https://np.reddit.com/r/pcmasterrac...nce_impact_of_windows_patch_and_bios/ds8qy3e/

Probably best to wait for more gaming benchmarks.

Hope haswell-e gets a microcode update, Intel can jog on if they think I'll replace a 2 year old system with another Intel based one if they don't make it right.

So sort of related, has intel's ipc advantage been because they have been cheating and not fussed about security?
 
Do not do this, if it's a Windows Server OS then the patch will apply BUT it will not be enabled. Please read the MS articles.

You have to manually enable the patch (you have to add 2 reg-keys), which will then potentially cause/give a performance impact.

EDIT: I would seriously recommend you also read this article - https://support.microsoft.com/en-us/help/4073225/guidance-for-sql-server

Some are server OS but we have some Win 10 Pro workstations as well. I'll take a look at that article thanks.

Unless the testing is purely functional, it should really be run in an environment that's representative of production - i.e. with the patch enabled. It'll be no good proving performance in test only for it to be slower when released to live.

I realise I've made a lot of assumptions above :)

Yeah we have a testing environment in the cloud which replicates the production environment, but we do a lot of dev work in house where we often just want to test functionality.

Plus if you use production data in the test environment then security is just as important as in production. I imagine in testing you'd want to try and emulate production as closely as possible to minimise any surprises that might happen when moving from testing to production.

No point running tests on a test database with 100MB of data if your production database is several GBs.

We develop websites so the production data is just fabricated input.
 
Last edited:
I think it is going to take intel some time to get the confidence back from a lot of people and businesses

The problem isn't trust, it's need. If your company requires 500 more computers, or if a server farm needs upgrading you can't simply not buy and if AMD computers aren't available you only have one other choice. That is the big issue, computers run the world, the choice to not buy doesn't exist for business. If Amazon require expanding their cloud capacity they can't just wait, they lose business doing that to someone else who would buy computers to expand their capacity instead. So Amazon have to buy and again they can only buy what is available. I fully expect companies to think heavily about buying AMD and many will, but AMD will run out of chips and given no other option trust or no trust, they'll buy Intel.

Now if GloFo had the same manufacturing capacity as AMD and it wasn't already assigned (which itself is a situation that wouldn't happen, you don't keep 20billion+ worth of fabs sitting there idle waiting for this kind of situation) then I think trust could massively massively hurt Intel, but in the current situation it will likely make much less difference than it should.
 
For the life of me I do not understand these people who are saying "No real drop in FPS doesent affect me" and are even saying they wont install patch because it will hinder performance. Are you people nuts? Are you ever going to go banks site with your computer? Ever going to be putting Credit card info on anywhere? Ever logging in on any site? Ever logging to program on your computer? If you are and dont have every last patch and firmware u are absolutely ******.

I literally use my gaming pc to game, nothing else (I have other devices for that). The only services I log into are gaming services, which I have different passwords to the services with which I'd care if they were hacked. Nothing personal stored on it whatsoever. My other devices - I will definitely apply the fix.

To be honest, the fact that such a vast amount of hardware has got the flaw gives a certain sense of safety in numbers. If almost all computers are potential targets, I don't feel particularly threatened as all computers have always been able to be hacked in one way or another anyway.

Obviously I know very little about computer security, but I know about probability. It sounds like it would be a freak occurance for an individual to get targeted given the hundreds of millions of affected devices. I probably have a higher chance of dying during one of my skydives tomorrow, or getting run over by car in the next few weeks. Putting things into perspective, I just don't care if someone hacks the password to my Steam account...

Its inexcusable how intel handled it though in my opinion. I think I'll go with AMD for my next build.
 
certain sense of safety in numbers

Sorry to burst your bubble, but that's not what safety in numbers means though - it means that most get away unscathed as a minority pay the price.

Abundant technology exists to enable scale and automation - it's very little cost to attack millions vs attacking a few. If you're a victim alongside many others, you're still a victim :(

Of course you have your own pain thresholds and unique circumstances, but don't let scary headlines put you off patching.
 
AMD has it's own protection built in to its cpu, and so only if you can actualy get access of the computer can you use the exploit. So AMD are almost bomb proof, so why the need for a patch.
Intel on the other hand, well you should have used 2 glued togeather deasktop cpu's to save all bother. LOL!!!
 
AMD has it's own protection built in to its cpu, and so only if you can actualy get access of the computer can you use the exploit. So AMD are almost bomb proof, so why the need for a patch.
Intel on the other hand, well you should have used 2 glued togeather deasktop cpu's to save all bother. LOL!!!

For meltdown yes. However, from what i have read Spectre affects AMD stuff as well.

Also from what i have read meltdown is fixed with the OS update but it is Spectre that needs the microcode update.
 
gives a certain sense of safety in numbers.

If you're a victim alongside many others, you're still a victim

Good hygiene should avoid him downlaoding any compromised/injected code though, plus two factor authorisation on the critical applications means passwords are of limted use (unless the attacker is waiting ready to control your system immediately you provide the second password) ?
 
Back
Top Bottom