![]() If you run sfc /scannow the files will be detected as corrupt and replaced. Random Write 4KiB (Q= 1,T= 1) : 95.270 MB/s Ĭlick to expand.Well, not only have I done it before and had it work(replaced imageres.dll in System32 and SysWOW64 with a hacked version to remove the blue and yellow UAC shield icons from shortcuts), but I just did it again, and it worked again!!! So much for that theory!!! You are half-right though. Random Read 4KiB (Q= 8,T= 8) : 1069.782 MB/s <- this was already impacted by 30% before That is an additional loss to previous impacts. Wasnt the MC update until today optional? Just great.ĭid a CrystalDiskMark and I lost about 50% in write speed on my Samsung 970 Evo 500GB. Because I do have a an earlier copy of that file for my CPU. So you should be able to replace that file with an earlier version(pre-this fucked update). From what I just read the OS gets the microcode from c:\Windows\System32\mcupdate_GenuineIntel.dll or c:\Windows\System32\mcupdate_AuthenticAMD.dll. ![]() But I think I know how to do it another way. And the Spectre mitigation disabling techniques/registry hacks aren't "disabling" it. It's the microcode update in the OS that's causing performance loss. I can still overclock with the BIOS I have from 2014. I'm pretty sure that's not going to solve my problem though. The next time it tries to update itself.right back to square one. But I can't see how either is more than a temporary solution. Or obviously by using a backup of the entire system. Pretty sure I could still temporarily fix it with an in-place upgrade. The don't make it past the restoring the registry phase. I've tried 7 restore points dating back to a week and a half ago now. Because I do have a an earlier copy of that file for my CPU.ĮDIT: Also of note. I can still overclock with the BIOS I have from 12/27/13.
0 Comments
Leave a Reply. |