New ryzen 9 5900x doesn't start up build error code c5,0D

[unknownperson]

Hello,

i just build my pc about a week ago.. and at first only my ram was limited to 3200mhz higher then that it would crash.and restore the speeds automaticly. 

but today i wanted to start the system and first you see the code C5 and after a few seconds it goes to D0. now my question what do these codes mean because the codes are not in the manual.

i hope someone can help me with this.

if any questions please let me know.

 

system specs:

Ryzen 9 5900x

ASUS ROG Crosshair VIII hero (wifi) Bios version: 2311
DDR4 Corsair Vengeance 3600
samsung m2 980 PRO 500gb
graphics card: MSI 1060 OC 6gb ( i believe )

PSU: RM1000I
case: Corsair 4000d Airflow

the pc ran normal for about 7 days.

 

[Guest]

D0 is Cpu initialization error.

D5 is No space for legacy option ROM.

 

Do you have another cpu to try?

 

 

[unknownperson]

4 minutes ago, ShrimpBrime said:

D0 is Cpu initialization error.

D5 is No space for legacy option ROM.

 

Do you have another cpu to try?

 

 

its c5 not d5 

 

and oh really D0 means Cpu initialization error strange that that is not in the book.

 

unfortunately no i do not have a different cpu. i did check all the pins and i did not see any pins bent.

[Guest]

1 hour ago, unknownperson said:

its c5 not d5 

 

and oh really D0 means Cpu initialization error strange that that is not in the book.

 

unfortunately no i do not have a different cpu. i did check all the pins and i did not see any pins bent.

Sry that was a typo. 

[unknownperson]

17 minutes ago, ShrimpBrime said:

Sry that was a typo. 

how did you obtain that information if i may ask because as far as i can see if it was a cpu problem it shouldve of showed 1 of the following codes: 57,58,59,5A 
 

and for what you said about ''No space for legacy option ROM'' shouldve of been D5 if i follow the q-code table from asus themselfs. while i get code C5

update: i now indeed see that D0 is CPU initialization error. now the question is it the motherboard or cpu?

Edited November 14, 2020 by unknownperson

[Guest]

3 minutes ago, unknownperson said:

how did you obtain that information if i may ask because as far as i can see if it was a cpu problem it shouldve of showed 1 of the following codes: 57,58,59,5A 

 

and for what you said about ''No space for legacy option ROM'' shouldve of been D5 if i follow the q-code table from asus themselfs. while i get code C5

In my sig below. 

 

AMI general post codes have been the same for years. 

Additional post codes are added to more higher end boards.

But your user manual should have the code list. I confirmed with both my sig and your motherboard manual. 

[unknownperson]

1 minute ago, ShrimpBrime said:

In my sig below. 

 

AMI general post codes have been the same for years. 

Additional post codes are added to more higher end boards.

But your user manual should have the code list. I confirmed with both my sig and your motherboard manual. 

haha, i just updated it with the D0, you are right about that 1, any clue if that is the fault of the cpu or motherboard?

 

c5 i cannot find in the asus manual.

[Guest]

3 minutes ago, unknownperson said:

haha, i just updated it with the D0, you are right about that 1, any clue if that is the fault of the cpu or motherboard?

 

c5 i cannot find in the asus manual.

I did make the mistake of D5 which is not your post code. 

 

C5 is blank. because it's the same as the D0. 

 

AMI codes that start with C are generally CPU error codes. Your's just isn't listed.

 

Here is some post code resources for you. 

https://www.evga.com/support/faq/FAQdetails.aspx?faqid=59687

C - C - CPU Error

C0 - OEM BDS initialization codes

C1 - OEM BDS initialization codes

C2 - OEM BDS initialization codes

C3 - OEM BDS initialization codes

C4 - OEM BDS initialization codes

C5 - OEM BDS initialization codes

C6 - OEM BDS initialization codes

C7 - OEM BDS initialization codes

C8 - OEM BDS initialization codes

C9 - OEM BDS initialization codes

CA - OEM BDS initialization codes

CB - OEM BDS initialization codes

CC - OEM BDS initialization codes

CD - OEM BDS initialization codes

CE - OEM BDS initialization codes

CF - OEM BDS initialization codes

[unknownperson]

7 minutes ago, ShrimpBrime said:

I did make the mistake of D5 which is not your post code. 

 

C5 is blank. because it's the same as the D0. 

 

AMI codes that start with C are generally CPU error codes. Your's just isn't listed.

 

Here is some post code resources for you. 

https://www.evga.com/support/faq/FAQdetails.aspx?faqid=59687

C - C - CPU Error

C0 - OEM BDS initialization codes

C1 - OEM BDS initialization codes

C2 - OEM BDS initialization codes

C3 - OEM BDS initialization codes

C4 - OEM BDS initialization codes

C5 - OEM BDS initialization codes

C6 - OEM BDS initialization codes

C7 - OEM BDS initialization codes

C8 - OEM BDS initialization codes

C9 - OEM BDS initialization codes

CA - OEM BDS initialization codes

CB - OEM BDS initialization codes

CC - OEM BDS initialization codes

CD - OEM BDS initialization codes

CE - OEM BDS initialization codes

CF - OEM BDS initialization codes

ohhh, didn't knew that haha.

 

hmm interesting, in your opinion what is likely to be broken the motherboard or cpu? or should i just send both back?

and curious what if the code was 0d? do you know that code?

[unknownperson]

On 11/14/2020 at 11:50 PM, ShrimpBrime said:

I did make the mistake of D5 which is not your post code. 

 

C5 is blank. because it's the same as the D0. 

 

AMI codes that start with C are generally CPU error codes. Your's just isn't listed.

 

Here is some post code resources for you. 

https://www.evga.com/support/faq/FAQdetails.aspx?faqid=59687

C - C - CPU Error

C0 - OEM BDS initialization codes

C1 - OEM BDS initialization codes

C2 - OEM BDS initialization codes

C3 - OEM BDS initialization codes

C4 - OEM BDS initialization codes

C5 - OEM BDS initialization codes

C6 - OEM BDS initialization codes

C7 - OEM BDS initialization codes

C8 - OEM BDS initialization codes

C9 - OEM BDS initialization codes

CA - OEM BDS initialization codes

CB - OEM BDS initialization codes

CC - OEM BDS initialization codes

CD - OEM BDS initialization codes

CE - OEM BDS initialization codes

CF - OEM BDS initialization codes

hi,

 

i wanted to let you know the code was 0D

[Guest]

2 hours ago, unknownperson said:

hi,

 

i wanted to let you know the code was 0D

Blank code.

 

Reserved for future AMI SEC codes. 

[unknownperson]

On 11/18/2020 at 6:52 PM, ShrimpBrime said:

Blank code.

 

Reserved for future AMI SEC codes. 

i wanted to update you and the post.

 

i decided to send it back to ASUS because i couldn't figure it out.

 

they fixed the issue. sadly enough i do not know nor do they tell me what the fix was. but it definetly was the motherboard.

[Guest]

3 minutes ago, unknownperson said:

i wanted to update you and the post.

 

i decided to send it back to ASUS because i couldn't figure it out.

 

they fixed the issue. sadly enough i do not know nor do they tell me what the fix was. but it definetly was the motherboard.

Did you get the same board back?

If so, they could have flashed the bios or installed a new bios chip. That would be the only physical thing they could have done.

[unknownperson]

1 minute ago, ShrimpBrime said:

Did you get the same board back?

If so, they could have flashed the bios or installed a new bios chip. That would be the only physical thing they could have done.

yep, same board.

 

yea new bios got released 3 days ago and that is also the date i recieved notice of it being sent back.

 

i do wanna thank you for thinking with me to try and fix the problem  

[Guest]

7 minutes ago, unknownperson said:

yep, same board.

 

yea new bios got released 3 days ago and that is also the date i recieved notice of it being sent back.

 

i do wanna thank you for thinking with me to try and fix the problem  

Haha go figure!!

You're welcome!

[unknownperson]

22 hours ago, ShrimpBrime said:

Haha go figure!!

You're welcome!

sadly enough i got another problem now. my ram refuses to go any higher then 2133...

 

and docp is enabled..

[Guest]

50 minutes ago, unknownperson said:

sadly enough i got another problem now. my ram refuses to go any higher then 2133...

 

and docp is enabled..

Try 3200mhz frequency instead. The IMC should handle that.

[unknownperson]

10 minutes ago, ShrimpBrime said:

Try 3200mhz frequency instead. The IMC should handle that.

yea won't work either..

 

even 2666mhz..

 

 

[Guest]

41 minutes ago, unknownperson said:

yea won't work either..

 

even 2666mhz..

 

 

If you are running 4 sticks, try only 2 sticks in A2 and B2 slots. 

[Guest]

What's the memory part number?

[unknownperson]

15 minutes ago, ShrimpBrime said:

What's the memory part number?

Corsair : CMK32GX4M4D3600C18

 

I also tried what you asked.. 

 

after removing 2 ram sticks i was able to make it 3200mhz and even 3400.. but 3600 was still outta reach.

 

 

[unknownperson]

1 hour ago, unknownperson said:

Corsair : CMK32GX4M4D3600C18

 

I also tried what you asked.. 

 

after removing 2 ram sticks i was able to make it 3200mhz and even 3400.. but 3600 was still outta reach.

 

 

update:

 

after i posted that i saw i only got 8 gb..

 

so i tested a bit more..

 

1 ram stick i get code 21.

1 ram stick works but 3400 NOT 3600

1 ram stick doesn't even show up.

1 ram stick works ( speed i did not test)

 

when i put the 2 ram sticks that work together i do get 16gb but only 2666mhz

[Guest]

Test each stick with mem test. Sounds like a  bad stick or two maybe.

[unknownperson]

On 11/28/2020 at 11:25 PM, ShrimpBrime said:

Test each stick with mem test. Sounds like a  bad stick or two maybe.

i ordered a new pack and same problem..

 

not sure what asus did but doesn't really look like they fixed it.. 

[unknownperson]

On 11/28/2020 at 11:25 PM, ShrimpBrime said:

Test each stick with mem test. Sounds like a  bad stick or two maybe.

contacted a few people, and they say its not a guarantee that the ram can run 3600 or 3200 because it also depends on cpu memory controller etc.. that is probably the reason i now only can get up to 2800mhz..

 

so i guess il have to deal with it.. and hopefully its just a bios problem haha..