New
#70
Thanks for the confirmation Jeannie! I'll make the correction.
Steve
Not sure how reliable Tom's Hardware is as a source - but if this is true, then I'm also going to hold off on any BIOS updates for a while too. I'm still running Haswell and it's apparently causing some issues on both Haswell and Broadwell CPUs.
Intel's Spectre BIOS Fix Causes Crashes On Broadwell, Haswell Systems
It's been around 1 day since I installed these four updates, which did take a while to download. No doubt that MS's servers are probably getting hammered for updates.
Aside from a weird, possibly unrelated issue during restarting where my monitor couldn't detect any HDMI output from my PC (another restart fixed this), nothing out of the ordinary to report so far.
That's good news!
Not to worry you but I looked up your sapphire GPU, doesn't that have an AMD chip in it? You might have dodged a bullet... I can't find anything on if AMD GPU's would act the same as their CPU's the GPU is on a different level and I'm thinking your i5 shielded it and when you did the 2nd boot it cleared out the cobwebs.
I'd just keep an eye on it and see how it goes, it may of just been a hiccup. Run your machine like you normally would, maybe a little harder, do you game?
Test it with a demanding game an see if you can tell if it runs the same now as compared to before the updates. If you don't normally shut down between uses try that like overnight and see how it acts on a cold re-start.
http://www.sapphiretech.com
I've tested my RX480 with some fairly demanding games, and it has been running as normal. I'll keep an eye on things, but nothing bad to report.
And according to a quick search, AMD GPUs are not affected by Meltdown or Spectre.
From The Verge:
Also, from a post on AMD's own forums asking about the issue:AMD is also revealing that its Radeon GPU architecture isn’t impacted by Meltdown or Spectre, simply because those GPUs “do not use speculative execution and thus are not susceptible to these threats.” AMD says it plans to issue further statements as it continues to develop security updates for its processors.
No GPUs are affected by Meltdown and Spectre, nVidia only patched their vulnerable software.
I installed the update this morning after installing ten others, bit by bit, creating additional restore points along the way, finishing with creating two system images on different drives for safe measure and checking for any last minute McAfee updates.
It took about 12 minutes to install and configure. Everything seems to be running as normal, I haven't noticed any slow down in performance or any error messages.
@Nitesco,
In case something would crop up you could point to this thread but you should start a new thread here: https://Graphic Cards | www.sevenforums.com. You've probably heard of Furmark, here's a tutorial on how to run the stress test: Video Card - Stress Test with Furmark remember to check the related tutorials at the bottom.
On the Geeks3D Softwares page you might be interested in: GPU Shark is a lightweight GPU monitoring utility for AMD Radeon and NVIDIA GeForce cards. It's second from the bottom.
I'd keep those two links so you could periodically check back for updates. Here's one from AMD that I missed , it's at the bottom of Updates and before the Information section(s):@Hellriser,There have also been questions about GPU architectures. AMD Radeon GPU architectures do not use speculative execution and thus are not susceptible to these threats.
I've been reading this page from mbam that started on the 4th of Jan.: Meltdown Mitigation It should be for business support but the mods there are allowing discussion for consumers, paid and free, free starts at post#12. I've read it to the last post that was 15hours ago and in it you'll see discussion about how the action center is set, running mb-check, and post#25 on how the different versions of mbam act towards setting the key.
From what I can gather, and since you like livin' on the wild side I'm thinking that you don't have any AV running and you need at least MSE to be running and that will set the key.@kimiraikkonen what happens is when you check for updates, Windows Updates looks to see if you have security software registered in Windows Action Center. If you do, it looks to see if that registry key exists, because that key should be put in place by the security vendor. If that key is missing, the update won't be pulled down. If the key is there, the update is installed.
As for the question of what Free users need to do, it's nothing. This only impacts Malwarebytes if you have Malwarebytes registered in Windows Action Center. You can only register Malwarebytes in Windows Action Center in the Premium/Trial mode, free mode does not provide real time protection, and therefore does not register.
if you go to your action center and expand the security section i.e. - click on the down arrow to the right of Security do you see these two settings turned to on?
If not start up MSE, check to verify the settings, if they're on then force a check in windows updates.
there is also discussion and I stand corrected, that you can manually create thekey but, I would strongly suggest that you have good backups of your system if anything goes wrong.Code:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat
@LevelBest,
On any given updates exercise bit by bit is sound practice when you have that many to do, it allows the creation of those extra restore points and makes it easier to troubleshoot any problems. With the extra images it looks like you're all set.
Did you check your installed updates to see if KB4056897 and in some cases like mine KB4056894 was installed? They both relate to the meltdown issue.
Instead of clicking on history, click on installed at the bottom, let the list populate then check.
Image courtesy of Brinks tutorial
@Anak: I can report successful install of KB4056894. I followed your advice and installed MSE, it created the registry, forced check updates, KB4056894 and KB4055532 appeared, installed, uninstalled MSE, restarted the PC a few times during this process, everything seems to run OK.
The only difference I saw is that Windows takes an extra 1-1.5 seconds to start up.
Thank you very much for your time, you really helped me with this. Too bad I can't rep.