Jump to content

i have an asus CH7 hero non wifi with 3733 teamgroup extreme ram one stick boots into both thr bios and windows 10 with DOCP enabled the second stick boots to a QCODE 0d oddly when i get the QCODE error i dont get and QLED's lit just the error i sent an email to teamgroup for a possible rma any ideas below are pic of the info you may need to help me 

 

oh and i tested some old sticks of DDR4 3000 mhz ram and they boot fine so i doubt its the board or cpu i can only assume one of the ram dticks is bad since one gives the error and one boots fine also seeing as how my old sticks of 3000 mhz ram boot fine no issues

1.jpg

IMG_0029.JPG

IMG_0030.JPG

IMG_0031.JPG

IMG_0032.JPG

Link to comment
https://linustechtips.com/topic/1213637-qcode-issues-on-my-ch7-hero/
Share on other sites

Link to post
Share on other sites

Try updating the BIOS to the latest version (might not fix anything but can't hurt).

 

Do you get the same error no matter which slot the "broken stick" is plugged in to?

Main Rig:-

Ryzen 7 3800X | Asus ROG Strix X570-F Gaming | 16GB Team Group Dark Pro 3600Mhz | Corsair MP600 1TB PCIe Gen 4 | Sapphire 5700 XT Pulse | Corsair H115i Platinum | WD Black 1TB | WD Green 4TB | EVGA SuperNOVA G3 650W | Asus TUF GT501 | Samsung C27HG70 1440p 144hz HDR FreeSync 2 | Ubuntu 20.04.2 LTS |

 

Server:-

Intel NUC running Server 2019 + Synology DSM218+ with 2 x 4TB Toshiba NAS Ready HDDs (RAID0)

Link to post
Share on other sites

2 hours ago, Master Disaster said:

Try updating the BIOS to the latest version (might not fix anything but can't hurt).

 

Do you get the same error no matter which slot the "broken stick" is plugged in to?

@Master Disaster bios is up to date broken stick gives me same error no matter which slot i use but the working stick boots in all slots as done my old ram that i replaced with the current broken ram

 

the only thing i havent tried is bumping the ram up to 1.5 volts default is 1.35

Link to post
Share on other sites

0d is a blank post code (not neccessarily error code) and seems your board just hangs there during post. 

The specific is used for future microcode updates.

 

I wouldnt keep trying to use that memory stick to avoid any further issues.

 

And dont pump 1.5v into the memory unless you're try to accomplish something while benchmarking.

 

Be sure your old sticks work in dual channel as expected to be sure the board or cpu doesnt have an issue.

 

 

Link to post
Share on other sites

6 hours ago, ShrimpBrime said:

0d is a blank post code (not neccessarily error code) and seems your board just hangs there during post. 

The specific is used for future microcode updates.

 

I wouldnt keep trying to use that memory stick to avoid any further issues.

 

And dont pump 1.5v into the memory unless you're try to accomplish something while benchmarking.

 

Be sure your old sticks work in dual channel as expected to be sure the board or cpu doesnt have an issue.

 

 

@ShrimpBrime the old sticks which i have in the board work fine and passed a full memtest86 test which i ran from bootable usb so i know the board and cpu arent the issue teamgroup is gonna do an rma with me

Link to post
Share on other sites

38 minutes ago, dreamcast4599 said:

@ShrimpBrime the old sticks which i have in the board work fine and passed a full memtest86 test which i ran from bootable usb so i know the board and cpu arent the issue teamgroup is gonna do an rma with me

Oh that's good to hear!!

RMA sucks to do, but no choice there.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×