help w/ boot prob..

[clocked1]

I was going to say I needed a clue, but right now there is more truth to it than I like to admit.. :D

Anyway, I just recently put together an AMD system using the 1.4 Tbird on a Epox 8k7a+ MB.. It worked great the first couple of hours running at 1.4 but started going downhill fast lastnight with several w2k stop errors. Temp was not a serious issue, it never went above 42C.

Today I go to fire up the machine, and nothing.. No floppy/hd access and no video signal but all the fans spin up, the nic lights do their little dance, and the cd tray's open when I hit em.. I popped the cover to take a look at the post leds and they start at FF and stay there. I seem to remember them going through several codes last night prior to settling on FF but could be mistaken.

Am I along the right lines thinking the BIOS is shot?? I thumbed through the good ole' epox MB owners manual to find out the FF code is "system booting, BIOS already pass the control right to the OS." I no longer have any other AMD chips, or boards to play with but I tried another video card, and another stick of DDR with no dice.. Anyone have some ideas on additional things to try now? Epox doesn't want people calling them, they don't have a phone number in the manual, and I couldn't find one on their website. I sent there email support folks a message, but don't have much hope of them answering it anytime soon.

One thing I did notice that was out of the ordinary is the fans spun up alot higher than they ever did before, almost like there was a power surge when I turned it on this morning.

Any thoughts?

[Thelemac]

Sounds a lot like when I killed a cpu. Try booting without the cpu in and if it doesn't do anything differently, that's probably your problem. Though the FF is kinda confusing. Try booting with it in and watch it. If it just stays there, cpu, otherwise, not sure.

[clocked1]

I tried it without the CPU already, I don't remember the exact results but it did display differently on the LEDS, and also had a nice Alarm.. :)

So if nothing else the board still recognizes there is something in the socket. I haven't blown a chip in several years, and I seem to remember that it at least made it through the boards post got the initial bios screen before it died detecting the chip.. This one isn't even going that far.. :(

I'm probably overly optimistic, but I'm still kinda hoping for a $15 fix instead of a $140... :)

[LyL Fox]

Actually, I ran into the exact same problem where my the code only showed FF and no video nor POST. I even contacted Epox about it and they say that the FF code at power on means that the bios couldn't detect a CPU.

[Pitspawn]

WAIT BUDDY!

Before going out to blow another $140 just try one thing...Reset CMOS. When I blew my PSU I tried everything BUT that. I was about 99% ready to buy a whole new rig when suddenly I remembered that jumper I hadn't tried. Booted up first time. 4 WEEKS i spent on a crap computer thinking mine was toast.

I love CMOS reset!

[clocked1]

Unfortunately I've already tried clearing the CMOS. I tried the machine again without the cpu this afternoon out of the case on a non conductive surface and It doesn't do anything differently without the chip as it does with it. So I'm thinking either a bad chip, or a bad socket.

Since the processor is "new" with less than 5 hours on it and never abused or operated out of spec I'm going to attempt an RMA on it... If I get a replacement great, if not I'll be selling the epox and going to the Tyan with twins. :) After swapping email back and forth with Epox all day trying to narrow down the problem I'm disappointed to say the least in their product knowledge. The only troubleshooting they offered was to try the system with just the bare bones, mind you this was after I told them I already did it. After I advised them it failed again they replied it's either the MB or CPU, replace them both...

Some support, that was their only suggestion. I support computers all day, where can I get one of those jobs where I can offer just one really basic suggestion and give up when it fails?

[wild_andy_c]

Originally posted by LyL Fox
Actually, I ran into the exact same problem where my the code only showed FF and no video nor POST. I even contacted Epox about it and they say that the FF code at power on means that the bios couldn't detect a CPU.

That is not what a stuck code FF means at all. FF means fully operational, to have FF with no video signal or HDD activity means that you have power regulation problems - insufficient 5v rail in the power supply.

[clocked1]

For grins and lack of other ideas I tried a couple different brands of powersupplies. They didn't make any difference. I got lucky and borrowed another cpu and bios plcc and between the 2 of them the machine boots! With just the borrowed cpu or just the bios nothing, but with both it works!

No idea what killed them, but they're dead. I'm on air cooling so I can't even point the finger at condensation as the cause! There are no shorts, everything was exactly as I built it with all of the wires properly loomed and tied. This is going to drive me nuts trying to figure out what killed it. So far I've narrowed it down to a fluke voltage spike coming through the UPS. Short of my cat opening the case while I was sleeping and rubbing against the chips I can't think of anything else that would of killed it, afterall it worked...

[Paiynn]

Your house could burn down tonight and then you could say, "But it was there this morning" :)

I'd just go for an RMA on it. Shouldnt be a problem, I crushed a t-bird with an orb and they replaced even though it had visible physical damage. If they dont want to replace it, wrap the cpu in a sheet of attitude, works wonders.