Maximus V Extreme - Booted to Windows Once, Now Stuck at Q Code 55

[AerithLives_]

Hi everyone,

This is my second build with an Asus motherboard, I previously used the P7P55D. When I first assembled the system, I was able to boot to Windows and use the desktop as normal. Then I added more components (the 2nd and 3rd HDDs) and since then, I can't get past the error code 55. I hope you may have some suggestions, as I am just about at wit's end.

Specs:
====
- Maximus V Extreme
- Intel Core i7-3770k (BX80637I73770K)
- G.Skill Ripjaws X 16 GB (4 x 4GB) DDR3 1600 (F3-12800CL9Q-16GBXL)
- eVga GeForce 560 Ti (re-used from old build)
- Creative Titanium HD sound card
- Corsair 750W PSU
- x3 Western Digital 1 TB 7200RPM (WD1002FAEX)
- Windows 7 Pro 64-bit



The only things installed right now are the CPU and RAM. I have tried all of the on/off switches for the RAM under the Reset button (1+3, 2+4, each individually), and each time it goes to q-code 55. I tried pressing the Go/memOK button, though I'm not entirely sure what that does.

I have carefully inspected the pins under the CPU and found nothing wrong. I have triple-checked the fit of the CPU and its fan. I have cleared the CMOS numerous times.

Any help would be very much appreciated. I really hope there's something silly and simple that I overlooked that would fix this.

Thanks!

[Zka17]

Hm... that's usually RAM/IMC issue... - have you tried clearing the CMOS?

And, welcome to the ROG Forum!

[AerithLives_]

Hi, yes and thank you. I've cleared it numerous times, but haven't had any luck.

[Zka17]

How exactly did you clear CMOS? By removing everything from the mobo, including all power connections and removing the battery?

If you did that, you may want to try only one memory module in the furthest slot from CPU... if that works, try all the modules individually... - run memtest86+ on them...

If it's not working, then you need to try other memories and other CPU...

[AerithLives_]

Zka17, thank you for your help.

I'm glad to say that it did turn out to be something silly and simple -- the memory wasn't fully seated at the bottoms of the RAM channels. I haven't reinstalled everything yet, but it goes through to the d7 "no input devices" code. Looks like I'm back in business!

[Zka17]

AerithLives! wrote:
Zka17, thank you for your help.

I'm glad to say that it did turn out to be something silly and simple -- the memory wasn't fully seated at the bottoms of the RAM channels. I haven't reinstalled everything yet, but it goes through to the d7 "no input devices" code. Looks like I'm back in business!

Oh, yes! The first thing is always to double-check the proper seatings and connections!

Glad, you sorted it out! :cool:

[chilinmichael]

Happened to me before as well...you always have to be sure to lock in the bottom side before throwing the clip to hold the module in.

[Shreve]

Make sure nothing is shorting out the board.... I struggled for like a month getting various Q Code Errors. Then I took everything out of the case and put it back together piece by piece.

I narrowed it down to either the screw on the wifi connection or the place where you hook up the power and reset buttons (sounds crazy) but everything is PERFECT now.. (Although I taped the wifi connection and dont have a working reset button)

Somet times weird stuff happens

Best of luck

[AerithLives_]

Thanks all!

I've managed to get through to an error code A2, and the boot_device_led is a solid red. The first and only time I got into BIOS, the priority is set (1) Optical Drive and (2) HDD. I've tried running it with just the OD, and just the HDD, no luck yet. I cleared CMOS inbetween each attempt by removing the battery + resetting the jumper.

I'll go back to digging around the forum for info.

[Zka17]

A2 is the code you want to see from now on! :cool: It is meaning that your BIOS handed over the job to the OS... - or it would like too...

The boot device led is showing you that there is some problem with your HDD... - do you have a RAID setup? Are you trying to use a previously installed OS (on an other system)? Where are your HDDs ODD connected?

Double check the cables you used and if they're connected correctly.
Perhaps, you will need a new/fresh install of the OS...