help - will not boot!

if it was ram you wouldnt reach the bios pages,the cpu or mem led would blink

i would consider rma,seems to be sata port issue,cant think whatelse you can do/try
 
Isn't the sata ports because it won't boot usb devices either.

Could be the chipset, this handles all bus communications I'm guessing?

If only there was a way to isolate whether it's the motherboard or the CPU though - that'd be useful
 
Isn't the sata ports because it won't boot usb devices either.

Could be the chipset, this handles all bus communications I'm guessing?

If only there was a way to isolate whether it's the motherboard or the CPU though - that'd be useful

the chipset controls sata and usb whereas the pci bus uses the cpu, a seperate sata chipset on pci would not use the p67 chipset.

a £26 1155 celeron would help say if it was the cpu at fault. ebay it after.
 
Ah I see, in this case would a PCI usb hub be a suitable way of testing my usb drives to see if they would boot?

And if so, I'm guessing no boot = cpu problem, boot = motherboard?

I ask because I have one lying around and would rather avoid wasting money on a cpu and sata controller which will never see further use.

Thanks
 
Ah I see, in this case would a PCI usb hub be a suitable way of testing my usb drives to see if they would boot?

And if so, I'm guessing no boot = cpu problem, boot = motherboard?

I ask because I have one lying around and would rather avoid wasting money on a cpu and sata controller which will never see further use.

Thanks



It appears actually that the PCIe lanes apart from the graphics lanes is controlled by the chipset, therefore my suggestion may not work.
 
Erm, random idea, may have no foundation at all but, could it be psu? initial boot would surely not draw as much as a full on load os from drive?
 
Unfortunately couldn't be that.

I tried it both with my 6950 in, and also without any GPU - issue was the exact same. I can't see how booting could cause such a significant difference in power consumption tbh.

Thanks for the suggestion though, will just have to wait now :)

EDIT
And OCuk have passed it on to Asus. So it looks like it was some sort of motherboard problem. Thanks everyone for your input, especially nkata. Hopefully they'll turn it around quickly. :)
 
Last edited:
Back
Top Bottom