Q-code error 0d - Crosshair VI

[Teramungus]

Hello all,
I received my back-ordered MOBO and put my new computer together but can not get it to POST. I assembled and tried to boot but get Q-code:0d and can not get to BIOS. The MOBO light up RGB and appears to be on; the amber light indicating a problem with DRAM is lit. CPU light is green (ready).

BUILD:
ASUS Crosshair VI
Ryzen 1800X
G.Skill F4-3200C14D-16 (2x8GB)
Samsung 960 Pro.
Asus Strix GTX960 OC 2GB
Corsair CX750M (24-pin and 8-pin; no 4-pin)
Fractal Define R5
Dark Rock Pro 3

I tried the shipped BIOS first: Q-Code: 0d.
I updated to latest BIOS via USB and back button: Q-Code: 0d.
Loosened the back plate to the CPU cooler (removed and re-seated all components): Q-code Od.
Tried to clear the CMOS with button on back: Q-code: Od.
Unplugged the USB 3.0: Q-code: 0d.
Tried all RAM slots and each separately (both RAM bad?): Q-code: 0d (on all combinations).

UPDATE: I went to Best Buy and bought PNY Anarchy 2x8GB 2133 CL15 and tried each of the RAM stick and got the same result as above: Q-code: 0d.
UPDATE 2: Tried both BIOS 0902 and 1002.
Update 3: Purchased PNY Anarchy (2x8) 2133MHz (not QVL) and the result did not change: Q-code: 0d.
UPDATE 4: I removed the original backplate for the new cooler and reused the thermal pad so I disassembled and tried again without the pad and no change: Q-code: 0d.
UPDATE 5: I called ASUS and went through the basic steps above but this time without the video card.... same result: Q-code 0d. They recommended RMA. Returning to Amazon (quicker).

*****EDIT 4/7/17- I received a second Crosshair VI and assembled the computer. I updated BIOS to 1002 before all else and can access BIOS. I then attempt to install WIN10 but as soon as the splash screen comes up the install freezes. I cannot populate DIMM_A2 slot with any memory and get Windows to boot. (The RAM is detected in BIOS but I am getting Q-code 54 & 55 and can not install Win10 and once installed will not boot as long as DIMM_A2 is populated; either stick of G.SKill works in DIMM_B1 & B2 or I can run two sticks in single-channel mode as long as DIMM_A2 is not populated. DIMM_A2 would not accept the PNY Anarchy 2133 (non-QVL). I tried to set the RAM speed in BIOS (not AUTO) and no change.

BOTTOM LINE: All the RAM I began with works. I get the same Q-code: 0d when 2nd MOBO DIMM_A2 is installed. WIN10 would not load OS and once installed will not boot as long as DIMM_2 is populated (BIOS sees it with 54 and 55 code and wont boot).*****

Any suggestions?

Thanks in advance.

[Teramungus]

Thanks to all!

I hope someone finds this thread useful and does not have to go through RMA.

I never got a chance to try your method. Amazon is sending a new one overnight and I tore computer down to ship before your responses.

to get a displayport working on your graphics card at boot all you have to do is disable csm completely in bios
and you don't have to disconnect anything when you can't boot ....try what i said ....it works...and works every time for me ....
hit reset to bios and immediately!! press and hold the start button in until you see the q codes light up then let go ...it will always no matter what go to bios on my board when i do this, it even gets passed the dreaded 8 code

I was using HDMI.

If I have any problems with the new board I will try the following:

hit reset to bios and immediately!! press and hold the start button in until you see the q codes light up then let go ..

Thanks Demoniacstar... and again, thanks to all!

[Teramungus]

So, I am curious as to what you do after you enter BIOS to prevent going through this method every time you boot. Does it go away when an OS is installed? Are settings changed in BIOS? :confused:

Another question to all: Was your yellow DRAM light lit (right below the Q-code display)? :confused:

[MNMadman]

Teramungus wrote:
So, I am curious as to what you do after you enter BIOS to prevent going through this method every time you boot. Does it go away when an OS is installed? Are settings changed in BIOS? :confused:

Another question to all: Was your yellow DRAM light lit (right below the Q-code display)? :confused:

Those lights under the Q-Code should only light up during the boot process. If the light stays lit, it indicates a problem. Normally that would indicate a problem with your RAM.

Since you have already tried different RAM, it indicates a bad CPU or board instead.

[Demoniacstar]

MNMadman wrote:
Those lights under the Q-Code should only light up during the boot process. If the light stays lit, it indicates a problem. Normally that would indicate a problem with your RAM.

Since you have already tried different RAM, it indicates a bad CPU or board instead.

who the *uck told you that!!! lmao...that is so totally wrong dude!!! now stop

you dont even own one of these boards and a ryzen cpu do you!!!
even after these boards boot to windows they still show a q code dude ...and they do not shut off!!

[MNMadman]

Demoniacstar wrote:
who the *uck told you that!!! lmao...that is so totally wrong dude!!! now stop

you dont even own one of these boards and a ryzen cpu do you!!!
even after these boards boot to windows they still show a q code dude ...and they do not shut off!!

Reading comprehension fail on your part. Re-read what I posted.

The Q-Code stays lit. The LED lights for CPU, DRAM, and GPU do not.

Stop being a dick and trying to find ways to mock me.

[Demoniacstar]

MNMadman wrote:
Reading comprehension fail on your part. Re-read what I posted.

The Q-Code stays lit. The LED lights for CPU, DRAM, and GPU do not.

Stop being a dick and trying to find ways to mock me.

yes the cpu light stays on and stays green .....not the yellow(ram) red (cpu) white(gpu) and green (boot) lights on the q code but that little green one up there is a cpu ok light it stays on

[BaneSilvermoon]

Demoniacstar wrote:
yes the cpu light stays on and stays green .....not the yellow(ram) red (cpu) white(gpu) and green (boot) lights on the q code but that little green one up there is a cpu ok light it stays on

And he said the lights under the Q-Code, which is the location of the QLEDs, not the CPU Ready Light. Which is very relevant being that someone had mentioned the RAM light remaining lit. Calms yourself

[R71800XSS]

Teramungus wrote:
So, I am curious as to what you do after you enter BIOS to prevent going through this method every time you boot. Does it go away when an OS is installed? Are settings changed in BIOS? :confused:

Another question to all: Was your yellow DRAM light lit (right below the Q-code display)? :confused:

Too I have qcode 0d, and can´t boot neither into BIOS. Led on is yellow. I tried clear CMOS some times (10 seconds), get out pile, releasing screws, remove all except PSU, M2 disk EVO 960, case , DDR4 Corsair LPX 3000 and it can´t boot. I sended memory for seller. I don´t understand why it happened, only I have changed the case.
anybody can explain it, it's memory error, or mobo error?

[jbasemoine]

Teramungus wrote:
Hello all,
I received my back-ordered MOBO and put my new computer together but can not get it to POST. I assembled and tried to boot but get Q-code:0d and can not get to BIOS. The MOBO light up RGB and appears to be on; the amber light indicating a problem with DRAM is lit. CPU light is green (ready).

BUILD:
ASUS Crosshair VI
Ryzen 1800X
G.Skill F4-3200C14D-16 (2x8GB)
Samsung 960 Pro.
Asus Strix GTX960 OC 2GB
Corsair CX750M (24-pin and 8-pin; no 4-pin)
Fractal Define R5
Dark Rock Pro 3

I tried the shipped BIOS first: Q-Code: 0d.
I updated to latest BIOS via USB and back button: Q-Code: 0d.
Loosened the back plate to the CPU cooler (removed and re-seated all components): Q-code Od.
Tried to clear the CMOS with button on back: Q-code: Od.
Unplugged the USB 3.0: Q-code: 0d.
Tried all RAM slots and each separately (both RAM bad?): Q-code: 0d (on all combinations).

UPDATE: I went to Best Buy and bought PNY Anarchy 2x8GB 2133 CL15 and tried each of the RAM stick and got the same result as above: Q-code: 0d.
UPDATE 2: Tried both BIOS 0902 and 1002.
Update 3: Purchased PNY Anarchy (2x8) 2133MHz (not QVL) and the result did not change: Q-code: 0d.
UPDATE 4: I removed the original backplate for the new cooler and reused the thermal pad so I disassembled and tried again without the pad and no change: Q-code: 0d.
UPDATE 5: I called ASUS and went through the basic steps above but this time without the video card.... same result: Q-code 0d. They recommended RMA. Returning to Amazon (quicker).

I wont be sending this back until tomorrow or the next (new ones are back-ordered 4 days). So, Any suggestions?

Thanks in advance.

ok this might sound crazy but you might try the follwing!
When i tried to flash the bios i did not work, the flashing of the bios seem to go fine but when i booted up the pc i constantly got a Q-code which left me stuck pre boot (so i could not enter the bios or nothing!).
After alot of headache and 6 hours of trouble shooting i reflashed back to a older bios version which i know work.
While back in windows (with older bios version) i redownloaded the latest bios and tried again, and yet again the flashing went as it should but pc would not go beyond the pre booting and everytime i relflashed the bios a diffrent q-code came up.
Finaly i copyed the bios from usb stick (which i used 12 times to flash the bios) to a other Ubs stick and i tried to flash with that usb stick.
And after a succesful flash all worked properly!
It somehow seems that one usb stick does not work proper while trying to flash bios (which is verry wierd since the stick itself works perfect!!!! never had any isseus with it).
So i would suggest to try an reflash the bios while using diffrent usb stick hopefully it will help you!

[MeanMachine]

Well I now know Bios revision 1002 works. I'm up and running. I flashed using the rear IO panel in the usual way with a USB stick and no probs. I also know what caused my Qcode od. Hate it when there not documented.

A few quick changes in Bios and my RAM is on 2099Mhz and I've clocked the CPU to 4.02GHz. My temps are not reading correct but I know the cause so yea, benchtest over and assy and fun begins. Will install the OS tomorrow.