Asus P5QL-E & Q6600 Won't Post. Please Help!

Hi Guys,

I've put my build together on top of the cardboard box comprising of the following:

P5QL-E, P4 Quad Q6600 and Heatsink
Single stick of Corsair XMS2 6400 DDR2 Ram (1x2GB)
NVidia GeForce 8800GT
Corsair 600W PSU

I'm getting no bleeps whatsoever and the motherboard fails to post and display anyhting on the monitor (DVI).

The green light is displayed on the motherboard and the only time I can get a bleep is if I unplug the PCI Express power lead out of the graphics card.

If I remove the RAM I still get no bleeps, only cutting power to the graphics card gives me anything.

I've cleared the BIOS, tried my other stick of ram to no avail.

On my corsair power supply I have the 12v connector which comprises of 2 4 pin connectors which go together, however the 2nd connector has a different set of shapes but still goes into the 2nd half of the 8 pin socket. I'm assuming this is correct as simply inserting the 5 pin plug gives me nothing either.

I remember with my last build I had to hold a key on my keyboard to get an emergency screen where I could manually change the RAM voltage. Is this the case again? It concearning that I get no bleeps with no ram in there.

Any ideas would be much appreciated.

Cheers guys...

John

I have had a similar problem and it ended up being a shonky motherboard.

If you have another GC i would try that and see what happens. Also boot up without the GC inserted into the mobo and see what happens then.

Hey there,

Thanks for replying tomawest...

Without the graphics card the same problem occurs. In fact. If i just have the cpu and heatsink connected without ram or a graphics card, no bleeps occur.

I found out earlier that the long bleep that I hear when diconnecting the PCI Express cord is coming from the onboard speaker of the graphics card. Thus no noise is eminating from the motherboard at all.

I hope there's nothing wrong with the Q6600 as I don't have my reciept or box to send the thing back.

Regards,

John

I have the P5QL-PRO, not the -E, and my motherboard doesn't have a built in speaker and neither does my Antec 300 case; therefore, I had to hook up an old speaker to the motherboard using the Q-connector thingy-ma-jig. So if your board (or case) doesn't have a speaker, then you won't hear any beeps.

I would recommend hooking up an external speaker - one from an old PC case - and then seeing if you get beeps.

The only two times my system wouldn't post was:

1) Knackered motherboard = no beeps

2) Enabling AHCI (or is it ACHI?) for the SATA in the bios AFTER installing vista with it set to IDE mode.

Yeah, after looking at everything i had an asus mobo as well and i can give you a high probability that it is the mobo that has bust and not the processor. Hope that you can take it back tho :). Also run as many different parts on different systems for approx a week if you have the luxury as I reckon that it may be something else that has caused the failure. if you can test just one thing, make it the PSU.

if you have another system that supports that cpu u have, put your cpu in and power it up. if it passes POST you know that the processor is fine. I think that it will be fine though. If you have OEM vista on that machine turn it off straight after POSTing as it will have worked and you wont kick windows security alarms into play.

Quote:

---

if you have another system that supports that cpu u have, put your cpu in and power it up. if it passes POST you know that the processor is fine. I think that it will be fine though. If you have OEM vista on that machine turn it off straight after POSTing as it will have worked and you wont kick windows security alarms into play.

---

That or hit delete to enter BIOS:)

Another thought...try putting the gpu in the second PCI-e 16x slot.#

Upon reading this i realized my p5ql-e will not boot with q6600 and 800mhz ram i have brought the exact same system as you and also my system will not up but for some weird reason when i use 667mhz ram i can post up its very weird i would just like to know how did you fix this issue :confused: