ASUS Maximus VI Impact boot up prob

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
Newly built PC with ASUS Maximus VI Impact. Initially set up fine, booted no prob and installed Windows 7. Now, it won't boot up with Q code 15. This happens quickly in the boot up sequence, when the PS appears to be 'ramping up.' By this, I mean its audibly noticeable that its 'working harder' as the PS fan's RPM is higher than normal. It stays in this state, no signal to the monitor or anything else. Does anyone know what Q code 15 represents?
Thanks for any help.
 
Solution
Will want some thermal compound, always best to put new on, simply remove your cooler, then clean the bottom of it (rubbing alcohol works well, loosen the clip holding the CPU in and lift the CPU gently from a corner, best to hold the CPU by the edges, clean off the top and maybe even bottom, chek socket for any pins that look bent

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
Yeah, manuals been checked. There's no 'Legend' or 'Key' regarding what a particular Q code means...kinda frustrating. Began a chat session w/ASUS techs online from their webpage earlier, only to have it timeout and say their techs were no longer available...even more frustrating. :(
 

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
I know how to get to the BIOS, my prob is that the boot sequence is hung up prior to when the monitor display kicks in...I've no monitor at the moment. I REALLY think this is RAM related also, as the MB DRAM_LED next to the EATXPWR connection is lit up. According to the manual, these LEDs are used to pinpoint where issues are coming from.
 

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
Okay, I'll give that a shot. If no joy is found, I'll have to pick up another stick of RAM tomorrow and try it....I'll post what I find out.
Thanks for all your help tonight, Tradesman1!

Cheers!
-CC

 

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
So, I checked both DIMMs w/only one stick at a time, same prob...BUT, with only one stick in, it was easier to see the MB LEDs and it turns out the CPU_LED is the one lit up. So, I'll be removing the CPU to check it now...is this a delicate procedure w/the thermal paste being on the CPU? I've never had to remove/check a CPU for probs before so I'm a little apprehensive...
 

Tradesman1

Legenda in Aeternum
Will want some thermal compound, always best to put new on, simply remove your cooler, then clean the bottom of it (rubbing alcohol works well, loosen the clip holding the CPU in and lift the CPU gently from a corner, best to hold the CPU by the edges, clean off the top and maybe even bottom, chek socket for any pins that look bent
 
Solution

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
So, I removed the cooler from the CPU and noticed how non-uniformal the thermal compound layer was on the CPU. (Bunched mostly on the left side, next to nothing for compound on the right edge of the CPU). I've attached a pic to show what I mean. Would this cause my CPU to work fine in the beginning, but then not work after awhile? Here's the link to the pic http://imageshack.us/photo/my-images/163/bhrl.jpg/
 

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
Also, I inspected the CPU back and the socket, no pins appear to be bent. Cleaned of the cooler surface and will now clean off the CPU. When originally set up the thermal compound, I followed a procedure from the Arctic Silver website. It showed to just apply a line of compound down the middle of the CPU, which I did. Maybe I used too much? It didn't seem like it at the time....<shrugs>
 

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
Memory used is G.SKILL Ares Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1866. The MB's onboard 'issue' LED was lit up for the CPU and the MB socket had no bent pins etc upon inspection, that's why I RMA'd the CPU.
 

raja@asus

Distinguished
Sep 28, 2011
891
2
19,360
The CPU LED will light up if the POST codes fall early on after the microcode is initialized - this does not necessarily mean the fault lies in the CPU cores - the System agent will halt if there is instability over the memory bus as well. If the CPU memory controller is weak, that would cause it, but that can usually be rectified assuming one can get the system to POST.
 

calvin_coolidge

Honorable
Oct 30, 2013
25
0
10,530
Well, I guess I'll find out when I get the new CPU. So it sounds like if, when the new CPU arrives and the code 15 remains, the only solution is to RMA the MB as I can't fix the weak mem controller w/o being in the BIOS. I hope this isn't the case....I just wanna use my new rig! :(