Results 1 to 10 of 50
Thread: Update microcode for Spectre?
Threaded View
-
03-07-2018 11:05 AM #11
jjxakergm PC Specs Motherboard ASUS Maximus IX Apex@MyMOD BIOS Processor Intel Core i3-8350k Memory (part number) G.Skill F4-3600C16D-16GTZR Graphics Card #1 MSI GTX 1080 Ti Gaming X Monitor Dell u2713H Storage #1 Samsung 960 EVO 250GB Storage #2 Samsung 960 PRO 512GB CPU Cooler Deepcool Captain 240 EX Case Phanteks Enthoo Pro M Tempered Glass Power Supply Seasonic PRIME 750W Titanium Keyboard G.SKILL Ripjaws KM780 RGB Mouse Razer Lancehead TE Mouse Pad G.SKILL Ripjaws MP780 Headset/Speakers Edifier R2800 + Supra ZAC Toslink Optical OS Win 10 RS4 x64@MyMod OS/ISO Network Router Asus RT-N65U@Сustom FW "Project Padavan"
- Join Date
- May 2017
- Reputation
- 10
- Posts
- 41
After lengthy tests, I do not recommend upgrading to the microcode to 0x84.
Serious problems with stability are observed, for example, when the instructions are used AES-NI.
With the load for two days, the system can turn itself off (does not respond to the power button), to start it will be necessary to de-energize the system completely, and then turn it on in normal mode.
There are still situations when the system itself turns off and immediately turns on.
The bug in the microcode resembles the operation of the option "forcereset" for the ME FW, just a similar behavior of the system...
Bug is observed on all KBL processors with microcode 0x84, to solve the problem helps rollback to 0x80 and younger.
The bug is very easy to identify, you can, for example, run a mining on an algorithm Cryptonight up to a day or two.
In general, Intel again spoiled everything!
udp. By the way, on the MSI motherboards z270 with a microcode 0x84 there is an error in the logs of the operating system "Power management functions of processor 1 in the performance state in group 0 are disabled due to a problem with the embedded software", on the Asus there is no such entry in the log. Well, it's just for information...
Far from all are faced with problems of arbitrary system shutdown on new microcodes, since the scripts of their appearances are specific. But not the fact that this scenario is the only one. Intel once again failed its partners...
ps. wrote as I could, sorry for my english
Systems on which tests were conducted (bios on default):
MB: ASUS Maximus IX Apex@BIOS ver. 1203 + Mc 0x84
CPU: Intel Core i5-7600k
RAM: G.Skill F4-3600C16D-16GTZR
SSD: Samsung 960 EVO 250GB
PSU: Seasonic PRIME 750W Titanium
OS: Win 10 RS3 x64 Build 16299.251 Specter/Meltdown is Disabled in the registry
-------------------------------------------------
MB: MSI Z270-A PRO@BIOS ver. 1.4 + Mc 0x84
CPU: Celeron G3930
RAM: GeIL GN44GB2133C15S
SSD: Samsung 850 EVO 120GB M.2
PSU: Corsair HX750i
OS: Win 10 RS3 x64 Build 16299.251 Specter/Meltdown is Enabled in the registryLast edited by jjxakergm; 03-07-2018 at 11:33 AM.