TRX40 Creator - "Code 54" After Reboot |
Post Reply | Page <12 |
Author | |
Moose
Newbie Joined: 17 Apr 2018 Location: UK Status: Offline Points: 221 |
Post Options
Thanks(0)
|
Thanks for the suggestions to try anyway, I just tried with CMD2T set to 2T and PowerDown disabled as well as reducing the frequency to as low as 2666MHz and it still occurs unfortunately.
Furthermore, Asrock list a similar Kingston ECC (KSM26ED8/16ME) as supported which is Micron but is Dual-rank and mine is Single-rank though so may be a factor: https://www.asrock.com/mb/AMD/TRX40%20Creator/#Memory I mean the system is stable, it's just this reboot issue maybe it is something else but the code 54 seems to indicate memory. There's loads of BIOS settings available not even mentioned in the manual so maybe more things to try. |
|
Moose
Newbie Joined: 17 Apr 2018 Location: UK Status: Offline Points: 221 |
Post Options
Thanks(0)
|
Well, believe it or not but after restoring the BIOS to defaults and configuring the same existing settings one-by-one, the issue has gone away. But I left all voltage and timings on Auto as well which was the same as initial testing. The only difference I can think of is I was saving and loading configurations, maybe there was a hidden setting being changed or something when loading a configuration. I have been in contact with ASRock support about this recently so will pass on this information. I also found that Overclocking is disabled when TSME is enabled (the BIOS menu disappears and Ryzen Master stops supporting it).
|
|
ket
Senior Member Joined: 13 Jul 2017 Location: UK Status: Offline Points: 1676 |
Post Options
Thanks(0)
|
Thats weird but not unheard of, didn't we already try resetting CMOS defaults a few times and it didn't work? Might be a hidden setting, or more likely the auto settings have changed one or two settings thats a very common occurrence, and why I'm not a fan of auto settings on mainboards. Use ZenTimings to have a peek at what timings the board is using now and if you have one compare them to an older screenshot when the board was using auto timings to see if anything is different.
|
|
Moose
Newbie Joined: 17 Apr 2018 Location: UK Status: Offline Points: 221 |
Post Options
Thanks(0)
|
Yes, did try BIOS reset a few times. Just had a look at ZenTimings and everything is the same as originally posted (post #7). Very strange. |
|
ket
Senior Member Joined: 13 Jul 2017 Location: UK Status: Offline Points: 1676 |
Post Options
Thanks(0)
|
Very strange indeed, not had an issue like this apparently magically fix itself before. Might be worth cleaning the gold contacts on the memory with a soft white artists eraser and ensuring the DIMM slots are clear of any dust and general debris. Has Windows done any updates recently? Perhaps one of those did something to remedy the problem. Chalk this one up to one of lifes little mysteries for now I guess.
|
|
Rogash1
Newbie Joined: 15 Oct 2022 Status: Offline Points: 15 |
Post Options
Thanks(0)
|
I'm still facing this issue in 2022 with the newest bios version 1.83. Was anyone able to resolve the problem so far?
|
|
Moose
Newbie Joined: 17 Apr 2018 Location: UK Status: Offline Points: 221 |
Post Options
Thanks(0)
|
Haven't seen the issue for a long time now. Also using 1.83 currently and it is working fine. Try restoring your BIOS to defaults and then reflashing your bios with the same latest version and then restoring to default once again and see if it does it at default settings (you might want to disable bitlocker in Windows first if that is applicable). |
|
Post Reply | Page <12 |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |