What's new
  • Please do not post any links until you have 3 posts as they will automatically be rejected to prevent SPAM. Many words are also blocked due to being used in SPAM Messages. Thanks!

Fixed! - First Post - ASUS Crosshair VIII Q-code stops at 15

bjcsoln

Well-known member
Joined
Apr 19, 2013
Messages
396
Location
Vancouver
Okay, just tried my first POST after confirming that the loop was working fine.

No error code beeps, but the Q-code gets to 15, then restarts and stops at 15...
That Q-code is "Pre-memory System Agent Initialization Started".

Have a pair of Trident Z NEO DDR 16 GB ram in slots DIMM_A2 and DIMM_B2 (which according to the manual is the recommended configuration) and an AMD3900xt.

I checked to make sure the RAM was seated properly, any ideas where I might've messed something up?
 

bjcsoln

Well-known member
Joined
Apr 19, 2013
Messages
396
Location
Vancouver
sswilson.

Thanks - I gave that a shot - tried (each) of the single sticks in all 4 slots, then moved the pair to the A1 and A2 slots as well. Same thing - I also noticed that the QLEDs, in this case the DRAM one, turned yellow which points to a DRAM error.

Might I need to try and return this set of RAM and try a new set? I want to think that it seems unlikely that they would not work out of the box (meaning the problem might be somewhere else) but not sure.
 

sswilson

Moderator
Staff member
Joined
Dec 9, 2006
Messages
23,531
Location
Moncton NB
My first gut instinct would be to try different ram, preferably something with relatively loose timings / speeds. Best would be if you had access to another set before having to return the ones you have, but not everybody has access to extra hardware for fault finding.
 

bjcsoln

Well-known member
Joined
Apr 19, 2013
Messages
396
Location
Vancouver
I guess I check what's in my current rig (although I dont think it is DDR4) - and if not, I will take your suggestion and get a cheap basic set to give that a shot. Thanks!
 

Sagath

Moderator
Staff member
Folding Team
Joined
Feb 7, 2009
Messages
6,360
Location
Edmonton, AB
Yeah, its not clear its the ram. You'd have to have both sticks dead (possible, but not likely) or it could be CPU...or mobo...

A good stick of ram is easiest to check though at this point.
 

bjcsoln

Well-known member
Joined
Apr 19, 2013
Messages
396
Location
Vancouver
Well, i took out a piece of RAM from my current rig and stuck it in, same result. With the single stick of 4GB, I did get a slightly different sequence of QCodes - it briefly flashed CC,92,C8,14, then stay on 15 before repeating.

With the (new) 2x16 pair (or just a single 1x16) it pretty much went to 14,15 then restarted.

Is it time to strip it all down and see if I can find anything shady?
 

sswilson

Moderator
Staff member
Joined
Dec 9, 2006
Messages
23,531
Location
Moncton NB
Reseat your MB power connectors before you start tearing everything down, and possibly disconnect everything but 1 stick, power connectors and video. If everything is working as it should it should at least boot into bios with that config.

The "pre-memory" code makes me a bit nervous though, usually an error code represents the last "good" indication it got and that suggests to me that it's either CPU memory controller, or MB memory interface.
 

bjcsoln

Well-known member
Joined
Apr 19, 2013
Messages
396
Location
Vancouver
Thanks - I will give that a shot. Meanwhile, this is the first time ever a build hasn't posted for me. I know its best practice to test everything first (I didn't) so maybe its time I learn my lesson. I will let you know the results.
 

Latest posts

Top