Finally happy with my EPoX 8RDA+

[cvb]

OK, that was simple. I had an older build (300) and a newer build (330) is working OK

 

[Megatomic]

Were you able to run 3DMark yet cvb?

 

[cvb]

yes. it works with a 330 build.

155x12.5, 155 RAM seems to be stable

 

[Megatomic]

Well, I sent in a trouble report to Epox in hopes of getting some help from them. Here's what I wrote:

My Kingston ValueRam PC2700 won't run at PC2700 (DDR333) at all. The highest FSB I can run is 150MHz. Higher than that and I get failures in Prime95, MemTest86, and 3DMark2001 SE Build 330. This memory was previously used on my trusty Epox 8K3A+ rev. 2 and it ran at DDR333 at the fastest timings the 8K3A+ offered. So I know the memory is fine.

Several other members at AnandTech Forums are having the same troubles with Kingston and Crucial memory. Many of these users used the same memory on other motherboards successfully also. We believe that there is a memory timing issue at the root of the problem (or something of that nature) and we want Epox to know about it so that it can be fixed ASAP. We bought our 8RDA+ motherboards so that we could run at DDR333 or faster using components rated to run at DDR333 or faster.

Please make an effort to troubleshoot the problem and see if it can be fixed with a BIOS update possibly. I love this board otherwise and I want to use it for a long time to come. Thanks for reading this and thanks for any help Epox can be in fixing this issue. Here is a link to a thread I started at AnandTech Forums, you can read it and see what I went through and what I did to narrow down my problem. (I am SeekingTao by the way)

http://forums.anandtech.com/messageview.cfm?catid=29&threadid=998712

Kind regards,
Jeff XXXXXXXX

Let's see if I get any reply or help. I hope I do.

 

[webley]

Good move SeekingTao, I also sent one to them about the 166MHz problem. Hope they help us out soon.

 

[Megatomic]

I don't know what I'm going to do. I am feeling more and more frustrated everyday. I can't afford to go out and buy new RAM right now. I could sell my current RAM and buy more with the money but then I'd be down waiting and the RMA period for the motherboard would be exceeded without me knowing if it is bad or not. Or I could trade but who'd trade me now?

 

[Megatomic]

Well, there is one kinds ATer that did want 1GB of RAM. I have a 512MB stick of PC3200 Corsair XMS on the way. Hopefully I receive it Wednesday and I will then attempt a 200MHz FSB. All I really ever wanted was a 166MHz FSB but I'll take 200 if I can get it.

 

[webley]

SeekingTao, So are you thinking about RMAing your 8RDA+? I've thought about it too but wonder if it would help. Did you get the impression that replacing it might help?

 

[Megatomic]

I was thinking of RMAing it but then I figured I'd give this killer board another shot. I have a stick of the best RAM available on the way. If I can't do squat with the board then I will immediately RMA the 8RDA+.

I sooooo want this board to be fine for me. It has everything I need (aside from IDE RAID) to make me a happy gamer for a while.

 

[cvb]

What really makes me NOT want to RMA the board is the built-in sound chip. OMG, what a great sounding setup (with my Klipsch 2.1 speakers).

 

[webley]

You mean RMA for refund? I was thinking about an exchange in case it's a problem with only some 8RDA+s.

 

[Megatomic]

I'd opt for another 8RDA+. I don't think NewEgg would refund us would they?

 

[webley]

Actually i got mine from MWave. Newegg is great at RMAs though. Do you think trying a new 8RDA+ could help?

 

[Megatomic]

Originally posted by: webley
Actually i got mine from MWave. Newegg is great at RMAs though. Do you think trying a new 8RDA+ could help?

I don't think so. If a part of the board refused to work at all then yes, it would. But everything works (albeit with our RAM underclocked). There is nothing stopping you from asking though, it is possible that a component is flaky causing this problem but that seems to be remote. How long do you have to RMA your board webley?

 

[SpideyCU]

I'm not sure how that'd work. If I had to give an honest reason for RMAing, myself, I'd say 'it worked fine with the old memory, but won't run at the same speed with this new memory', and they'd say "you've got bad RAM". Of course, that's only if I were honest.

In reality, I'm not sure a new board would fix this for me, so I'm going to wait out for a BIOS update or SOME sort of solution. The other part of it is that I'm just too lazy to reinstall a new board and suffer the temporary downtime!

 

[webley]

How long do you have to RMA your board webley?

I have a few more days but decided to go ahead and RMA it now after reading about the statement Crucial supposedly made about 3% of the 8RDA+ boards having trouble with Crucial PC2700 512 MB ram. That was the RMA reason that I gave and I think it's legitimate. I'm also replacing my Crucial PC2700 ram with Kingston HyperX PC3000 ram just in case that works any better. This is the first system I've built where I had to replace most of the parts (except the processor) to get it to work normally. I sure hope this helps because it's adding a lot to the price after the new ram and the shipping is added in. I'd still rather do this than be a dude getting a Dell however.

 

[Megatomic]

Ok, I got my Corsair XMS Platinum Series installed (1 x 512MB) and my system is running at 166MHz FSB (2172MHz) at default CPU voltage and DIMM voltage. I will stress the system at this point until I am done with my project for school (probably Friday night) then I will subject this machine to a torture she has yet to experience.

So, to sum up:

1) My Epox 8RDA+ is fine. It has no problems (now).
2) The Kingston PC2700 I used to own is fine. It worked properly in my Epox 8K3A+ at PC2700 and it is now working properly in it's new owner's computer.
3) The combination of my Epox 8RDA+ and the Kingston PC2700 was not fine. There is some issue between the two that I was not able to resolve given the current motherboard's BIOS code and components. I don't know what the problem is but it is there. Hopefully it does get resolved soon for those who haven't or will not replace their memory with different DIMMs (such as this Corsair or some TwinMOS or Mushkin).

Thanks to everyone who participated in this thread, it was "fun" and definitely a learning experience.

 

[mboy]

Originally posted by: mboy
What are your mem timings at? I would run them rather relaxed as I dont have much faith in that ram Oc'ed and at tight timings.

Onboard NIC is not a problem as I am using it on mine @ 200fsb

Keep your vcore@ 1.775 and your vdimm at least 2.77.

I would also reco some better cooling on your CPU, but I dont think that is your problem.

I bet it is your ram.
Before my twinmos/winbond (which I cant praise enough), I was using my old crucial pc2100. Even tho it ran at 145fsb @ cas2 in my 8kha+, it wouldnt run that on the 8rda+.
Obviously it wasnt my 8rda+ or xp2100, casue I am running my mem in synch @ 5-2-2-2 @ 200fsb x 11.5

Thats what I figured

 

[webley]

Great to hear your 8RDA+ system is working with the new Corsair SeekingTao. I hope to get mine working soon too with some Kingston HyperX ram.

 

[SpideyCU]

I've been able to get my system to run at 157 sync stable with this Kingston memory. I've been pondering whether the extra 9 MHz is worth my troubles to either RMA or spend money on more expensive memory. Choices choices. Anything above 160 Mhz still craps out on me.

 

[HardwareAddicted]

Finally happy with my EPoX 8RDA+

I wish I could say the same... but it could be something simple.... no idea.

I just built the PC with almost the same config as you....

EPoX 8RDA+ rev. 1.1
AMD AthlonXP 2100+ Tbred "B"
Kingston 512MB PC2700 x 1 (ValueRam not HyperX)

Wont even boot.... no idea what version of the bios it has.... never seen it yet. *sigh*

Any ideas ?

~ Mark

 

[Megatomic]

Originally posted by: HardwareAddicted

Any ideas ?

~ Mark

Have you verified that all the cabling is connected properly? I know it's basic but when I have issues I always eliminate that first. PSU plugged into 120V source, ATX header connected, case wiring connected to the right pin blocks, CPU HSF plugged into CPU fan header on the mobo, etc...

Also, is the RAM seated properly? Have you tried to clear the CMOS by any chance? And if this is a new build (please don't take offense) is there a switch on the outside of the PSU that might be in the "off" position? That has gotten me once before, I was really embarrassed too.

I'll see if I can come up with more things to check. Good luck.

 

[HardwareAddicted]

Originally posted by: SeekingTao

Originally posted by: HardwareAddicted

Any ideas ?

~ Mark

Have you verified that all the cabling is connected properly? I know it's basic but when I have issues I always eliminate that first. PSU plugged into 120V source, ATX header connected, case wiring connected to the right pin blocks, CPU HSF plugged into CPU fan header on the mobo, etc...

Also, is the RAM seated properly? Have you tried to clear the CMOS by any chance? And if this is a new build (please don't take offense) is there a switch on the outside of the PSU that might be in the "off" position? That has gotten me once before, I was really embarrassed too.

I'll see if I can come up with more things to check. Good luck.

All good basics... no offence taken.

I should have told you.... I have power... both the DVD, and the burner start lighting up.... fans all start up.... FDD light up for a sec... all normal looking....

I get the "FF" on the board.... just no picture..... nothing....

~ Mark

 

[Megatomic]

OK, have you tried to clear the CMOS by any chance? I believe that the FF code on POST with no POSTing is one of the signs of a dead NF2 BIOS. Hopefully a clear CMOS can clear that up. If not, an RMA is in order.

 

[HardwareAddicted]

Originally posted by: SeekingTao
OK, have you tried to clear the CMOS by any chance? I believe that the FF code on POST with no POSTing is one of the signs of a dead NF2 BIOS. Hopefully a clear CMOS can clear that up. If not, an RMA is in order.

Yeah.... tried it twice now.... second time I took the battery out too.

Dang it.... I wish I could flash it once to clear this up....

Thx for the help though

~ Mark