Epox 8RDA+/XP2500+ computer won't boot - WORKING!

[techwanabe]

I came home from work yesterday and my computer wouldn't boot. I've got the manual here but I can't find the beep codes. When I started it, it sounded like one long beep... or possibly one long and two short... it's hard to tell since they weren't distinct separate short beeps. Could be one long beep with a little distortion at the end...

So I boot up, get a long beep, the monitor shows no picture at all and remains solid black... I know the video card is good (currently a Radeon 32DDR) cause I put it back in my old faithful Tualy computer and it displays fine. I can hear the hard drive chattering quitely. No joy.


Anyway, I'm trying to find out about the beep codes... the motherboard LED displayed FF - it's an Epox 8RDA+
I'm thinking my CPU might be bad or maybe memory? I was running a AMD Athlon 2500+ Barton (Retail) at factory spec speeds (never overclocked it). Temps always seemed ok - in the 40's. Comments?

I'm going to take up a spare stick of DDR RAM from work to swap and check the memory.

 

[Ionizer86]

So I suppose the PC used to work, right?

My first step (other than changing components) would be to pull everything out of the case and set up a test bench. See if everything works. It really does sound like the board though since it it was memory it would post with a C1 and if it was the chip or video, it'd probably post something else. FF upon boot is most likely the board.

 

[techwanabe]

Originally posted by: Ionizer86
So I suppose the PC used to work, right?

My first step (other than changing components) would be to pull everything out of the case and set up a test bench. See if everything works. It really does sound like the board though since it it was memory it would post with a C1 and if it was the chip or video, it'd probably post something else. FF upon boot is most likely the board.

Yes,

It has been working fine for four months. The LED on the board normally shows FF if I remember correctly. I'm going to try different memory next.

 

[Dogma420]

cpu, mb, or memory. If you can, swap each out and insert another. Easiest way. Sometimes the hardest way.

 

[farscape]

Some info for you from :

http://www.motherboardfaqs.com/news.php


My board will not boot part two: Error Codes!

One of the greatest features that Epox included with this board is the diagnostic LED. During the boot process the LED outputs a hexadecimal code that tells the user what step of booting it is currently working on. This means that if the boot process fails, the user will know what part of it failed. While it isn't a fool proof system, and the users manual has almost no valid information on error codes, it can be an invaluable tool when you learn to use it. What follows is a list of known error codes in and what they mean. Also if a given fix for an error code doesn't work, try resetting the bios or starting again with the basics (board, cpu, ram, power supply, and video card) to help isolate the actual problem. I did not simply copy the entire list out of the manual, like other guides have, because the manual doesn't really provide much (if any) useful information for most error codes.

1d - Commonly mistaken for "P1" which is not a hexadecimal code. This code means your video card isn't being detected properly. Try reseating the card and test the card in another system to make sure that its ok. This error code can also come up as 2d.
12 - Normally this code is caused by a bad battery. Just replace it. The battery is a "CR2032", and can be found at most stores for about two dollars.
26 - This is an "overclocking" error. You can almost always fix this by clearing the cmos.
C1 - The number one error that users have with this board. It means that the ram was not detected. To be honest there aren't many fixes for this. Try different combinations of slots and sticks if possible, but the odds are you are out of luck. This board can be extremely picky about ram. In this situation I would test the ram on another board if possible to ensure that it works, and if so, return the motherboard for a new one. I would say that about 10% of boards have this problem with about 25% of ram. Not an impressive number. This error can also appear as C3 or C5.
FF - This code can be life or death for your motherboard, literally. FF means a successful boot or a complete failure. This normally means that your bios chip is dead or not being accessed properly. Try tapping or holding insert while attempting to boot the system, resetting the cmos, or: If your floppy drive makes any noise when booting, but the system appears dead, try placing a floppy in the drive with a copy of the latest bios file on it. This might cause the system to use an emergency re-flash feature.


Hope it's not your board. They aren't too easy to come by lately.

 

[Ionizer86]

I'm seconding the board as the problem. Spend some time diagnosing, but with the focus on the board as the most likely problem. I got a DOA 8KHA+ once, and no matter what chip, ram, PSU I used etc, it posted FF with no video on the monitor.

I hope EPoX or the vendor lets you RMA. I think that their not make 8RDA+ boards anymore is not a big issue since I still believe they make 8RDA3+ boards, which has some new features, but unfortunately has no MCP-T.

 

[Stonewall44]

I've had nearly the identical problem recently. Computer wouldn't boot, black screen, the whole works. Because of the error codes, etc., that I would get, I believed it to be a hard drive failure. Bought a new hard drive, nope. Not the problem. Bought a new processor, again...no luck. Tested the memory, nope...just fine. Took the mobo out of the case, installed the processor, heat sink, and fan and hooked up the PS....no go.

Motherboard is on it's way back to newegg for RMA. I'm writing this using my old Biostar motherboard and 1gig Athlon processor. The good news is that when my board gets back my system specs will look like this....


AMD Athlon XP Barton Core 2600+, 333 FSB, 512 cache
MSI K7N2-L Motherboard
Maxtor 80gig 7200 rpm hard drive, 8 mg cache

 

[techwanabe]

Some things to chew on here... an bad mobo will be a pain in the tush... I'm trying different memory tonight and will report back. I'm down a video card too so that means downing this PC to diagnose the other... fun fun fun.

 

[techwanabe]

UPDATE!

I threw in a different memory module into a different slot (Kingston PC3200 256 mb DDR), and she booted up. I'm writing you from the computer in question. So, I've narrowed it down to either the slot or the Buffalo chip, er memory module!

Looks like the motherboard is ok, that's a relief! Woo hoo!

 

[Ionizer86]

Wow, that's so weird. I'd really have expected the C1 code if some memory was screwed. Hope the dimm is god and that the other ram is RMAable

 

[techwanabe]

Hey, weird I know, but It's alot easier and cheaper to RMA a little memory module than a whole motherboard!

So... FF was the LED reading on the mobo, which is what it always reads. Hmmm, maybe they read FF no matter what!!!

It was a stick of PC3200 Buffalo Winbond 512mb DDR that seemed to go plughy... Newegg says lists it as lifetime warranty.

 

[Ionizer86]

The thing is, this is how FF usually works:

If the PC boots, cycles many codes, and the mobo then displays FF once everything is working, your board is Fully Functional.

If something screws up, and it lands on FF right upon boot with the other stuff not working, your board is Fully F%#ored. At least that's how it usually goes, but good thing you found out your board was good.

My board gave me lots of bios checksum errors before as well (8RDA+). I put in a new 2032 Energizer and thankfully the problem is gone. The 8RDA+ once again proves its excellence

 

[techwanabe]

Yep, I haven't tried the original memory slot yet, but I'd have to think that would be very unusual.