NEED HELP: Epox EP-8KDA3+ NForce3 250GB won't boot!

[Insomniak]

Ok, this has been one nightmare night. Here's the story.

Myself and my housemate just assembled his new PC...it was his first time, but I am an experienced DIYer so we had no problems. The installation went fine. System components were as follows:

Epox EP-8KDA3+ Motherboard, NForce3 250GB
AMD Athlon 64 3000+ Socket 754, .13nm (stock heatsink/fan)
1GB Mushkin Basic Green (512x2) PC3200 DDR SDRAM
Leadtek GeForce 6600GT 8X AGP
Western Digital 80GB 7200 RPM IDE HDD
Antec 350W Power Supply, 12v@21A
Two of his old optical drives, one CD-ROM, one CD-RW
2x120mm Case Fans

So we get all this assembled, and go in to start loading software/configuring. This is where the nightmare begins.

On boot, the system checks out the 6600GT, it comes through fine, then I get 1 beep, and it posts processor speed, and memory check, both of which are on spec and fine. Then there is a 15 - 20 second hang. Then it detects IDE devices, which it comes up with the correct IDE devices, and their jumper settings. THen there is another 15 - 20 second hang. Then the POST pops up "Verifying DMI Pool data......" and hangs for about 15 - 20 seconds again. Then it attempts to boot from CD-RW (my second boot device) I assume because it can't boot from the hard disk. It hangs here for 15-20 seconds. Then it attempts CD-ROM, third boot device, and hangs for another 15 - 20 seconds. Then it pops up a disk boot fail message, and asks me to insert system disk. It will sit here indefinitely from here on out.

OK, a few things -

1) If you boot through either optical drive using the WinXP install disk, Windows will install, reboot, configure, and be good. The installation is successful, but the system will not boot to it.

2) As soon as the POST hits the "Verifying DMI Pool data...." part mentioned above, the debug LED on the motherboard gives an FF code, which according to the manual can be 1 of 4 things:

- Incorrectly seated BIOS chip - checked it, it's seated fine.
- Improperly seated add in card. Checked and reseated both, they're fine.
- Incorrect/problem with BIOS. I attempted a BIOS flash (AFTER ALL THESE PROBLEMS HAD BEEN OCCURING), but it would not complete...the system just hung for 15 - 20 seconds then proceeded with it's normal crippled, semi-boot. BIOS version is 10/22/2004, so it really shouldn't need it. I attempted to Flash to the
- Motherboard is dead. Possibility?

Anyway, I have been trying to solve this for about 8 hours now today, and I'm about to go out of my mind. The only option I can think of that I have not tried yet is that perhaps the 80GB WD drive has some kind of defect, so I'm going to swap it for a known good 45GB WD drive and see if things go ok. If so, we've found my culprit, If not, I have two primary suspects:

1) Corrupt BIOS
2) DOA Motherboard



Is anyone familiar with this kind of situation on this board, or any other? If so, can you recommend any fixes or courses of action? Any and all help or suggestions would be greatly appreciated.

 

[o1die]

Switch the hardrive jumper. If you're running in "cable select" mode, try master instead, or vice-versa. Use master slave for the cd drives on the same cable, and keep the western digital by itself. Epox has a "magic flash" utility program which might be easier to use than a floppy, if you can get into windows.

 

[FastEddie]

Two other items. Try clearing the cmos, (complete shut down, unplug the ps from ac, remove cmos battery, clear cmos).

The second is that your powersupply is right at the limit with only 21a on the 12v rail, especially with the 6600GT added to all your other perifs.

 

[Insomniak]

Originally posted by: o1die
Switch the hardrive jumper. If you're running in "cable select" mode, try master instead, or vice-versa. Use master slave for the cd drives on the same cable, and keep the western digital by itself. Epox has a "magic flash" utility program which might be easier to use than a floppy, if you can get into windows.

Can't get into windows. Optical Drives are already on Master/Slave defined, and the WD is on it's own IDE channel. I haven't tried setting it to cable select yet though. I'll give that a shot.


FadtEddie, how long would it take for the CMOS to clear? Haven't done that before, although I am familiar with the method. Do I just need to pop the battery out and reseat it, or do I need to leave it out for a while?


As for the PSU, I'm going to strip this thing down to 1 optical, 1 HDD, 1 Fan, and the video card, and see if that goes, but a 350W Antec with 21A on the 12v should be plenty for all this, don't you think? It's not like the 3000+ or 6600GT are particularly power-hungry...

 

[Insomniak]

UPDATE: Stripped down to the bare minimum load on PSU, which was this:


1x120mm exhaust fan
Motherboard, CPU, RAM
8xAGP 6600GT
80GB WD
CD-RW


And still no dice.

By the way, I highly doubt it's the power supply. I can get into the BIOS, and according to the BIOS, all the rails are spot on, so it certainly doesn't seem like it's short on power. I'm going to try adjusting jumper settings and clearing the CMOS tomorrow. It's late here, and I have to work in the morning.

Tomorrow, I'll also try hooking it up to my Enermax 460W Whisper II with 33A on the 12V, and see if that makes any difference. Like I said, though, I doubt it...

Please do keep posting potential ideas/fixes as they come to you however...I will be checking this thread like a madman...this is my #1 priority until fixed.

 

[NoRAM4U]

Trying setting the CDRom as the first boot device.

Removing the battery doesnt always reset the bios - weird, I know but use the bios reset jumper.

As as for the debug code, FF means everything is OK. I have four Epox boards...and they are all showing FF while running.

 

[Insomniak]

Originally posted by: NoRAM4U
Trying setting the CDRom as the first boot device.

Removing the battery doesnt always reset the bios - weird, I know but use the bios reset jumper.

As as for the debug code, FF means everything is OK. I have four Epox boards...and they are all showing FF while running.

Very odd, because according to the manual it's a problem code...

Either way, everything is NOT ok, as the system won't boot to the windows install I'll try the jumper first instead of the battery tomorrow, thanks for the tip. I've already tried setting CD-ROM as first boot device...no difference.

On the 6600GT....it consumes less than 50 watts at burn, less than 20 watts at Idle according to Xbit - I don't think the 12v on this system is being thrashed, especially considering we're rendering the equivalent of DOS here...

Thanks for the responses so far guys, and keep em coming. I'm going to bed, but I'll be checking back in the AM.

 

[FastEddie]

Clearing the cmos should only take you about ten minutes tops if done the long way (as I described). And when you have the system unplugged from the ac source, push the power button on the front of the case---this will discharge all the charged caps. Then proceed with clearing the cmos.

I question the limits of the ps because of the long delays you are getting through all the stages of loading the os, (verifying dmi pool data, detecting perifs, memory, drives, etc.). When you are in the cmos setup, there is no load on the ps at all, or nearly at all, so seeing strong rails there is good, but doesn't mean that much. Your bios isn't saving, but clearing the cmos might resolve that.

 

[Insomniak]

Tried clearing the CMOS, reseated BIOS chip, swapped out for good RAM, swapped out for good IDE cables, hooked up a 460W Enermax PSU, nothing worked. All other components were confirmed known functional in another system. Only device possibly faulty is motherboard.

We registered the mobo and started the RMA process. Looks like it was just a DOA I appreciate everyone's help and suggestions. Wish me luck!