w10 + x99x killer Event 54 Kernel-Processor-Power
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=3103
Printed Date: 20 Jul 2025 at 1:39am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: w10 + x99x killer Event 54 Kernel-Processor-Power
Posted By: bigodon
Subject: w10 + x99x killer Event 54 Kernel-Processor-Power
Date Posted: 25 Jul 2016 at 9:42am
|
Hi, Last weeks i noticed some bad behavior of my rig, i have hard locks sometimes by doing simple tasks like open internet browser and watch a video. These freezes are related to "Kernel-Processor-Power event id 54 - task 39" some information: i have the last firmware flashed on my uefi, the 3.0 version downloaded and installed from uefi i also have the last updates instaled on windows 10 x64 (not the ones from insider preview) i have checked my windows files with SFC and DISM Commands, there is no errors on my installation i have check for malware and virus, and there is nothing that can harm and cause the freezing all my drivers are updated and unused stuff like onboard lan and realtek audio is disabled my computer is: asrock x99x killer intel core i7 5820k 16gb ram ripjaws i don't do any extreme overclocking, i use the uefi 4ghz preset with xmp, nothing that happens before with over than a year of using this hardware. I read somewhere people saying for downgrade to 2.10 firware and the hard lock freeze stoped, i tried without success. I also tried to clear CMOS by change the jumper position, without luck... i really running out of ideas here, the next windows update maybe can fix this... but there is any uefi update by asrock on the way?
|
Replies:
Posted By: wardog
Date Posted: 25 Jul 2016 at 10:44am
|
I believe if you flash to BETA 3.02a this will be resolved. http://www.asrock.com/mb/Intel/Fatal1ty%20X99X%20Killer/?cat=Beta" rel="nofollow - http://www.asrock.com/mb/Intel/Fatal1ty%20X99X%20Killer/?cat=Beta |
Posted By: bigodon
Date Posted: 26 Jul 2016 at 3:38am
|
thanks for info wardog, so i updated to this beta bios and had a hardlock just few minutes ago and it was related to "Kernel-Processor-Power event id 54 - task 39" still looking what can be, if you have an idea to help me out i accept.
|
Posted By: bigodon
Date Posted: 28 Jul 2016 at 9:13pm
|
ok, i think i have an update i tried unpark my cores on windows 10 reg and looks like this get rid of hardlocks following this: http://www.coderbag.com/programming-c/disable-cpu-core-parking-utility allow me stay 48h without hardlocks, i don't know if is fixed but i was having like 2 or 3 freezes per day.. so, my last steps was: 1) upgrade my bios to 3.02 beta 2) upgrade windows 10 to anniversary edition til here the computer still freezing 3) unpark 2 cores, that utility found i think now it's fixed, too early to say... but another people said disable c-state on uefi also works (i didn't done this, only unpark) |
Posted By: parsec
Date Posted: 28 Jul 2016 at 10:14pm
|
So you changed to the 3.00 UEFI, which is the Broadwell-E processor compatibility update, while using a Haswell-E processor, i7-5820K. That is fine, but there is an Intel Management Engine (IME) software update for Broadwell-E. X99 board users that changed to the Broadwell-E processor compatibility UEFI version, and were using a Haswell-E processor, but did not also update the IME software, soon found their over clock did not work. Did you happen to use this version of IME at any point, after applying the Broadwell-E processor compatibility UEFI? Intel Management Engine driver ver:11.0.4.1186: http://www.asrock.com/mb/Intel/Fatal1ty%20X99X%20Killer/?cat=Download&os=Win1064" rel="nofollow - http://www.asrock.com/mb/Intel/Fatal1ty%20X99X%20Killer/?cat=Download&os=Win1064 If not, you should install that version of IME. Using any built in OC profile is a gamble, since all processors of the same model differ in varying degrees. Built in OC profiles normally set the processor voltages higher than necessary for maximum compatibility, but settings like System Agent voltage (VCCSA) can be optimal at a lower voltage. VCCSA is best tuned to the value preferred by your particular processor. XMP profiles can also change (increase) the VCCSA voltage, and again may increase it more than necessary. Over clocking is not a simple "cook book" process, setting UEFI options to specific values and its done. Built in OC profiles do the best they can, but one size fits all is not correct. I use C States on my ASRock X99 board, and have never had any locking, Event 54 problems. The default value for the C3 C State is Auto, which is disabled. C3 seems to not work well with Haswell-E or Broadwell-E processors, but I use C6 without any issues. If you changed C3 to enabled, try it set to Auto. Core parking is a Windows thing, which is similar if not identical to using the C6 C State. I cannot be 100% certain without researching it on an X99 system. I have never had to disable core parking on any PC I use. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|