Archived from groups: alt.comp.hardware.pc-homebuilt (
More info?)
"Jim Smith" <jim_smith@livejournal.com> wrote in message
news:ff0d2d30.0406091030.199354a8@posting.google.com...
> I successfully built my first PC last year without any trouble, and
> now my brother has decided to trust me with assembling another one for
> him. Unfortunately, this time I can't get the computer to boot. When
> I turn it on, all that happens is that the fans start and the lights
> come on in whatever parts I have connected. The POST code on the
> motherboard is FF, which I assume is fine since that's what the
> computer I'm using now is showing. I have yet to get the new project
> to give me a single beep or display anything on monitors that I know
> work.
>
> Something's wrong, and I'm coming to accept that I may have to replace
> a part. I just don't know which one. I can't think of anything I did
> to damage the motherboard, but so far it seems to be the most likely
> culprit.
>
> If anyone can help me figure this out, I'd appreciate it. My
> brother's gonna kill me...
That is most likely the CPU or motherboard, in that order. What make/model
motherboard? Which CPU? Is the HSF fan connected to the motherboard's cpu
fan connector? Is that fan running? Can you hear the hard disk(s) spinning
up eventually? IF SO, then that might point toward a video card or RAM
problem. But if it was video card or RAM, your POST code would probably not
be FF, and you'd probably get some kind of "beep" error, as well. No beep
at all indicates to me that the CPU isn't even running POST. As the
mainboard is giving FF as a post code, this looks suspiciously like a bad
CPU. Or the CPU could just need to be reseated. Another possibility is a
bad power supply, but that's less likely. Basically, the CPU looks for good
power. If it sees power good, it attempts to run POST. During POST, your
video card might be initialized (if it gets that far). But it sounds like
you aren't even getting as far as the CPU starting POST. Most likely
suspect at this point is CPU, I'm afraid. A real long shot . . . have you
tried clearing CMOS settings on the mainboard? I don't think that will
help, but it won't hurt. Good luck, -Dave