X99 Extreme4 + Bios3.30 - Event 54 Kernel Error

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I get same issue with X99E-ITX/ac / BIOS 3.10 / Win 10 x64. 
Edit: Just realized BIOS 3.60 was released 2 days ago, going to test it )
Edit2: Yes, 3.60 fixed Event 54 Kernel Error, but added new one:
Event 137 Kernel-Power Error: "The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance."

Edited by McLeft - 06 Sep 2016 at 9:27pm

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
McLeft Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 05 Sep 2016 Status: Offline Points: 16	Post Options Post Reply Quote McLeft Report Post Thanks(0) Quote Reply Topic: X99 Extreme4 + Bios3.30 - Event 54 Kernel Error Posted: 05 Sep 2016 at 8:48pm
	I get same issue with X99E-ITX/ac / BIOS 3.10 / Win 10 x64. Edit: Just realized BIOS 3.60 was released 2 days ago, going to test it ) Edit2: Yes, 3.60 fixed Event 54 Kernel Error, but added new one: Event 137 Kernel-Power Error: "The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance." Edited by McLeft - 06 Sep 2016 at 9:27pm

xichiu Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 03 Aug 2016 Status: Offline Points: 1	Post Options Post Reply Quote xichiu Report Post Thanks(0) Quote Reply Posted: 03 Aug 2016 at 1:05pm
	I'm getting crashing with the same code as everyone here. Every hour or so with safe cpu temps it only happened after updating to the latest 3.10 bios. Using x99e-itx on windows 10. Please try to fix this as fast as possible. Thanks in advance!

ASRock_TSD Members Profile Send Private Message Find Members Posts Add to Buddy List ASRock_Official Joined: 20 Mar 2015 Status: Offline Points: 8592	Post Options Post Reply Quote ASRock_TSD Report Post Thanks(0) Quote Reply Posted: 29 Jul 2016 at 5:34pm
	Dear Bigodon, Greetings, this ASRock TSD. Please check the BIOS P3.10 as the link: http://www.asrock.com/mb/Intel/Fatal1ty%20X99X%20Killer/?cat=Download&os=BIOS Thank you for your patience. If any, please feel free to contact us! Kindest Regards, ASRock TSD

bigodon Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Jul 2016 Status: Offline Points: 6	Post Options Post Reply Quote bigodon Report Post Thanks(0) Quote Reply Posted: 26 Jul 2016 at 4:16am
	I start to have this some weeks ago, now it becoming too often to be honest, this start to annoy me because i cannot work without hardlocks and freezing! I created a topic here with information of my computer and what i already did to try fix this. but my mobo is Asrock x99x killer, with 3.02a beta firmware recomended by a moderator here, and unlucky it didn't fixed. please Asrock, work closer with microsoft to fix those issues on windows 10 thanks!

ASRock_TSD Members Profile Send Private Message Find Members Posts Add to Buddy List ASRock_Official Joined: 20 Mar 2015 Status: Offline Points: 8592	Post Options Post Reply Quote ASRock_TSD Report Post Thanks(0) Quote Reply Posted: 02 Jun 2016 at 7:41pm
	Dear customers, Greetings, this ASRock TSD. Please download the BIOS file for Instant Flash from the link, we first release for X99 Extreme6: https://mega.nz/#!Rlk2wCiS!qqpIYrIMaC9sWpWd6c14eXRkImb7XXn0ftYY8lKhsx4 and Extreme4 : https://mega.nz/#!0wES2KYJ!WFY-7XjGa8yk9tgCAtKQq8NU52BtoMQy_QzNggNZCi4 The BIOS not only solve the event ID problem but also improve the system compatibility. We are now updating the BIOS to our official website instead of the free space. Since there're many different models, please give us some times to finish the work, thank you. Thank you for your patience. If any, please feel free to contact us! Kindest Regards, ASRock TSD Edited by ASRock_TSD - 03 Jun 2016 at 11:59am

panakyr Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 01 Jun 2016 Status: Offline Points: 8	Post Options Post Reply Quote panakyr Report Post Thanks(0) Quote Reply Posted: 01 Jun 2016 at 1:22pm
	I own a X99 WS. With Windows 8.1 and bios 3.10 I have the same error(event 54) No error with bios 2.10 Please could you fix it?Thank you

ASRock_TSD Members Profile Send Private Message Find Members Posts Add to Buddy List ASRock_Official Joined: 20 Mar 2015 Status: Offline Points: 8592	Post Options Post Reply Quote ASRock_TSD Report Post Thanks(0) Quote Reply Posted: 27 May 2016 at 5:47pm
	Greetings, this is ASRock Technical Support. We are sorry and we know that everybody is waiting for the solution. Considering another BIOS modification, we have to release the BIOS after a complete test. Actually this error message is NOT a critical issue that will not affect normal application. Anyway, we will release the BIOS ASAP. Thank you for your patience. Kindest Regards, ASRock TSD

Silverback1985 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 26 Apr 2016 Status: Offline Points: 5	Post Options Post Reply Quote Silverback1985 Report Post Thanks(0) Quote Reply Posted: 12 May 2016 at 1:15am
	@AsRock_TSD Any updates on this ?

mbtech Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Apr 2016 Status: Offline Points: 10	Post Options Post Reply Quote mbtech Report Post Thanks(0) Quote Reply Posted: 01 May 2016 at 7:25pm
	I have the same experience with ASRock X99 Extreme6 motherboard with BIOS v3.0. This version of BIOS has note in description - "Support 2016 Q2 coming new CPU". Strange thing is, that in Windows 7 Pro with same version of BIOS (v3.0) is no such errors in Windows Event Viewer -> Windows logs -> System. Errors appear only in Windows 10.

Codeblock Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 28 Apr 2016 Status: Offline Points: 3	Post Options Post Reply Quote Codeblock Report Post Thanks(0) Quote Reply Posted: 30 Apr 2016 at 2:30am
	Thanks for reply ASRock, waiting for results about this issue.