Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Suddenly q code 56 no boot...

Ocelot
Level 7

‎07-23-2017 02:14 AM - last edited on ‎03-05-2024 10:11 PM by Community Admin

Hi,

my system was stable until last night no problems but today my system won't boot with code 56.
I have a ryzen 1700 OC with pstates and offset @3.8ghz with 1.375v stable with prime and occt. Ram gskill flare x 3200hz @2933 14,14,14,34 with 1.35v.

I can't use the newest beta bios because I have the wifi version.

What seems to be the problem?**
0 Kudos
5,344 Views
9 REPLIES 9

Eleiyas
Level 10

‎07-23-2017 02:37 AM

QCode 56 is Invalid CPU Type or Speed.

Try doing a BIOS/CMOS reset and seeing if your rig will boot
0 Kudos

Ocelot
Level 7

‎07-23-2017 02:39 AM

I did that and it will boot fine but after awhile Iam not sure what causes it it happens again after working for a few days with no problems it suddenly won't boot and is stuck at code 56

*
0 Kudos

Eleiyas
Level 10

‎07-23-2017 02:47 AM

Try reflashing the BIOS using flashback.

If you still get the same issue, try re-seating the CPU - maybe there is a faulty connection somewhere
0 Kudos

Ocelot
Level 7
In response to Eleiyas

‎07-23-2017 02:59 AM

Eleiyas@ASUS wrote:
Try reflashing the BIOS using flashback.

If you still get the same issue, try re-seating the CPU - maybe there is a faulty connection somewhere


I will try that but if the CPU is not seating right then it wouldn't be working at all right ? But that's not the case....
0 Kudos

haihane
Level 13

‎07-23-2017 03:08 AM

Why not do both cpu reseating and bios flashback?
no siggy, saw stuff that made me sad.
0 Kudos

Eleiyas
Level 10
In response to haihane

‎07-23-2017 05:05 AM

haihane wrote:
Why not do both cpu reseating and bios flashback?


If the BIOS is the issue and reflashing resolves the issue, then reseating the CPU is pointless :3
0 Kudos

Ocelot
Level 7
In response to Eleiyas

‎07-23-2017 05:32 AM

Eleiyas@ASUS wrote:
If the BIOS is the issue and reflashing resolves the issue, then reseating the CPU is pointless :3


reflashing resolved the problem 2 days ago but today it happend again....lets wait and see
0 Kudos

Eleiyas
Level 10
In response to Ocelot

‎07-23-2017 01:34 PM

Ocelot wrote:
reflashing resolved the problem 2 days ago but today it happend again....lets wait and see


in that case, if reseating the CPU doesn't work either, then you are (unfortunately) looking at a faulty CPU or a faulty board (most likely)
0 Kudos

Ocelot
Level 7

‎07-23-2017 04:35 AM

I reseated the cpu and reflashed the bios lets wait and see if it happens again. I had so much trouble with this board since I bought it last week if the problems dont get resolved I guess I have to try some other board...
0 Kudos