Finally happy with my EPoX 8RDA+

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
I have searched and I have looked at 8RDAfaq.com and nforcershq forums for this already and came up short so I'll ask the pros here... Is there a definitive driver install guide for the EPoX 8RDA+? I will be installing this board and using the onboard sound and LAN features. So I'd like to know what drivers to install and in what order relative to the OS and each other.

Thanks for any help.

Edit: I changed the name of the thread to reflect current events. :)
Edit: I changed the name of the thread to reflect current events. :(
Edit: I changed the name of the thread to reflect current events. :)
 

SpideyCU

Golden Member
Nov 17, 2000
1,402
0
0
I was sure one of the veterans would've jumped in, but since they haven't, I'll give you an inferior man's account. ;)

Keep in mind this is probably the "best" way to do it, which doesn't mean the "only" way.

* Install Windows (2k, XP, whatever)
* Update to the latest Service Pack (assuming XP, that would be 1)
* Install the nVidia 2.03 drivers for the motherboard

Now, I'm interrupting this right here because I couldn't do it exactly in this order. Why? I couldn't get SP1 unless I had my network connection running...and I couldn't have my network connection running until I installed the nVidia drivers (at the very least, for the on-board NIC). So, I did the drivers off the EPoX CD, then got SP1 for XP, and THEN got the 2.03 nVidia drivers and installed those over the old ones. Anyhow, after you have done that:

* Install drivers for your remaining components (video card, etc.)
* Grab any remaining critical updates that you feel you need from Windows Update

That should provide you with the least headaches. Just to play it safe, reboot whenever an update suggests that you do. When you try to install many, many important updates at once without rebooting, you're just teasing Windows to do something wrong. This isn't really a concern with WinXP/2k, but previous incarnations of Windows were less forgiving, and it's a habit I've carried over.
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Cool, it arrived :cool: If you do use any PCI cards, the fourth PCI slot from the top seems to not share its IRQ, so that would be the first one I'd use.
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: mechBgon
Cool, it arrived :cool: If you do use any PCI cards, the fourth PCI slot from the top seems to not share its IRQ, so that would be the first one I'd use.


Thanks! As of right now, I only plan on using the AGP slot and using the integrated LAN and sound. But if they don't measure up I'll plug in add-in cards. I am hoping the onboard stuff works out though, I'd like to get a SCSI card and HDD and let them OWN the PCI bus.
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Originally posted by: SeekingTao
Originally posted by: mechBgon
Cool, it arrived :cool: If you do use any PCI cards, the fourth PCI slot from the top seems to not share its IRQ, so that would be the first one I'd use.


Thanks! As of right now, I only plan on using the AGP slot and using the integrated LAN and sound. But if they don't measure up I'll plug in add-in cards. I am hoping the onboard stuff works out though, I'd like to get a SCSI card and HDD and let them OWN the PCI bus.
Hehe, now you're talkin' my language :D I used slot 4 for an Adaptec 19160 to run my Cheetah X15-36LP. Adaptec SCSIBench shows peak throughput from card to PCI bus of over 120Mb/second :D

 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: mechBgon

Hehe, now you're talkin' my language :D I used slot 4 for an Adaptec 19160 to run my Cheetah X15-36LP. Adaptec SCSIBench shows peak throughput from card to PCI bus of over 120Mb/second :D
:Q Now that's what I'm talking about. :D How much did you pay for that setup?
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
The card was about $145 (got it from 2336 in the FS/T forum IIRC) and the drive was around $230 from Hypermicro :)

Now the new-generation Cheetah 15k.3 is about $230 for 18Gb (still about 8Gb more than I need) and it trounces my X15-36LP by about 20%, which makes me jealous :p I'd probably pair that up with the LSI Logic U160 card that Hypermicro's got, it's $65 bare or $90 with a cable, terminator and drivers. Coolerguys has some nice buys on silver or gold rounded SCSI cables with terminators too, at $16. BTW, the LSI card is 64-bit-ready too.

Anyway, I like my SCSI setup a lot, no regrets. And nForce2 is the right platform for overclocking with SCSI, since the PCI bus remains at spec all the time.
 

SpideyCU

Golden Member
Nov 17, 2000
1,402
0
0
Now that those SCSI "issues" in WinXP are gone and away with for the most part, I have the urge to move my SCSI controller card and drive out from my Linux box and into my Windows system (which has the 8RDA+, of course). It may not have a 64-bit PCI slot, but, I think it'll be a good match anyway. My SCSI drive is one of the slightly older IBM 18.6 GB models, but still good enough for me.

Unfortunately I'd want to install WinXP on that drive instead of my IDE ones, and that would mean reactivating Windows...AGAIN. :p
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Wow, talk about an easy installation. Very nice. Since my last board was an Epox also, the LED/switch connections were easy. Also, aside from the ATX header everything is laid out so well. Easy to put together.

I did do two things that I am happy about:

1) I put a passive heatsink on the south bridge chip. I used pushpins and Arctic Silver for this.
2) I removed the north bridge heatsink, cleaned off the TIM, applied Arctic Silver, and reattached the heatsink. Hopefully this allows me to do some nice overclocking.

I'll post updates.
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
All right. Windows is almost done installing. WinXP Pro setup didn't recognize my drives (they were previously in my RAID array). I had to use the MaxBlast software to fdisk them first... Strange.

Anyways, both the NB and SB chip heatsinks are pretty warm. Thank god I cooled the SB and used Arctic Silver on each of them. :Q
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
All right. I have completely installed/patched windows and loaded all the drivers. I then flashed to the 03/05/03 BIOS and began to overclock the CPU.

I went right to the settings I was using on my 8K3A+ (13x166x1.7V) and I got a reboot. So I upped voltage to 1.725V. Temp. displayed by MBM 5.2.x.x is 45C. Not bad.

Oh, CPU is an AXP 2100+ Tbred "B", memory is 2x512MB Kingston PC2700 running in DualDDR mode.
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Hmm, the overclocking is not going well on this board. With the same CPU, HSF, and RAM I could run 13x166MHz with memory at PC2700 on my 8K3A+. I am having a hard time running over 150MHz FSB now. 3DMark2001SE and Prime95 won't run for long at 155 and up.

Time to troubleshoot. I wonder if I am being bit by using dualDDR mode?
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
You might want to go through the BIOS-settings "starting point" I posted in the stickified 8RDA+ thread and make sure you didn't leave anything on Optimal. Got the AGP bus locked at 66MHz? BIOS updated to the latest version? (edit: oops, I see you did) The JCLK jumper is capped as it should be? Memory is at 100% of FSB speed as it should be?
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: mechBgon
You might want to go through the BIOS-settings "starting point" I posted in the stickified 8RDA+ thread and make sure you didn't leave anything on Optimal. Got the AGP bus locked at 66MHz? BIOS updated to the latest version? The JCLK jumper is capped as it should be? Memory is at 100% of FSB speed as it should be?

Yes to all that. I hope I can find the source of this problem soon.
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
If you haven't tried it already and you're comfortable with the idea, you might try the next-higher VDIMM setting of 2.77V. Trying just one DIMM at a time as a troubleshooting step might shed some light too. I hope it works out for you :eek:

Actually, here's another idea: try raising JUST the FSB/memory clock, or JUST the multiplier, and see what that reveals about the problem. (edit: bah, I'm too tired to think... you didn't raise the multiplier in the first place :confused: I better get some sleep :p)
 

jiffylube1024

Diamond Member
Feb 17, 2002
7,430
0
71
Try upping your voltage to the memory. Otherwise try running the memory at conservative timings (3-3-3-6) just to see if you can get it stable at 166+ MHz FSB/memory. It might be the pickiness of dual-channel DDR that is the problem...
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
OK, I'll do a summary post of where I am and what I have done so far. First the basic system specs:

EPoX 8RDA+ rev. 1.1 BIOS 8RDA3305
AMD AthlonXP 2100+ Tbred "B" week 0301
Kingston 512MB PC2700 x 2 (ValueRam not HyperX)
Coolermaster HHC-001 with a 5000RPM 60x60x10 Coolermaster fan
Antec PP412X SmartPower PSU
Antec SX840 case with 2 x 80mm exhausting fans (case temp. hovers around 31C)
VisionTek GF4 Ti 4200 128MB
Using onboard sound and LAN
WinXP Pro SP1 (all patched up)

CPU:
1) I have run it at default settings (no Prime95, just to install WinXP, patch it, install the drivers, and flash the BIOS to latest official version)
2) I have run it at 166MHz FSB at various multipliers with voltages up to 1.75V (crashes Prime95 and 3DMark2001SE quickly)
3) I have run it at 155MHz FSB at various multipliers with voltages up to 1.75V (crashes Prime95 and 3DMark2001SE less quickly)
4) I have run it at 150MHz FSB at various multipliers with voltages up to 1.75V (crashes Prime95 and 3DMark2001SE even less quickly)
5) I have run it at default settings at various multipliers with voltages up to 1.75V (successful at Prime95 and 3DMark2001SE)

Memory:
1) I have run it at default settings (no Prime95, just to install WinXP, patch it, install the drivers, and flash the BIOS to latest official version)
2) I have run it in DualDDR mode PC2700 in aggressive, turbo, and optimal modes at default and 2.77Vdimm (crashes Prime95 and 3DMark2001SE quickly)
3) I have run it in DualDDR mode 155MHz FSB in aggressive, turbo, and optimal modes at various multipliers with voltages default and 2.77Vdimm (crashes Prime95 and 3DMark2001SE less quickly)
4) I have run it in DualDDR mode 150MHz FSB in aggressive, turbo, and optimal modes at various multipliers with voltages default and 2.77Vdimm (crashes Prime95 and 3DMark2001SE even less quickly)
5) I have run it in DualDDR mode PC2100 in aggressive, turbo, and optimal modes at various multipliers (successful at Prime95 and 3DMark2001SE when overall freq. <= 2128MHz)
6) I have run it in single channel mode, memory populating DIMM2 and DIMM3, at PC2700 in turbo mode at 2.77Vdimm (crashes Prime95 and 3DMark2001SE quickly)
7) I have run it in single channel mode, one stick in DIMM1, at PC2700 in turbo mode at 2.77Vdimm (crashes Prime95 and 3DMark2001SE quickly)

I didn't have enough time to test it in single channel mode at less than PC2700 but I suspect that the results will follow the trend and operate more stably at lower FSB settings. It seems to me that the system doesn't like elevated FSB. Keep in mind that this very CPU and RAM combo ran at 13x166 and PC2700 just fine on my Epox 8K3A+ board so it is not the CPU and RAM that I am questioning. This leads me to the next phase of this post: questions/doubts

1) Before I installed the motherboard I removed the heatsink from the north bridge chip. I cleaned off the TIM pad the best I could but I couldn't find my Goof Off. I used nail polish remover (basic stuff) and isoproply alcohol to clean the heatsink and chip but they still felt tacky (i.e. there was a residue of TIM on them). I then applied Arctic Silver to the north bridge chip and reattached the heatsink. Could the residue of TIM on the chip and heatsink be causing improper cooling of the chip and thus this inability to to run at a FSB higher than 133MHz?

2) I am using the onboard NIC. Does the use of the nVidia NIC lead to instability when running at higher FSB settings?

3) And the biggest question/doubt I have. Is all this an indicator of my system not liking to run at higher FSB settings due to using 512MB DIMMs? I hope not but the doubt nags at me.

Please help with any advice/comments you can come up with. Thanks.
 

Blain

Lifer
Oct 9, 1999
23,643
3
81
"Please help with any advice/comments you can come up with."

Avoid any memory labeled "Kingston" or "ValueRam". :D
I guess I'm still bitter about being screwed out of a rebate on some, many moons ago.

When you say you've run the CPU at 166 using various multipliers, have you tried 166 FSB with a 10.5 multiplier and default voltage?
I'd suggest disabling all the "onboards", keeping the PC2700 at conservative settings, starting at the CPU's default speed on a 166 FSB and working your way up from there.

 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: Blain
"Please help with any advice/comments you can come up with."

Avoid any memory labeled "Kingston" or "ValueRam". :D
I guess I'm still bitter about being screwed out of a rebate on some, many moons ago.
Sorry to hear about that Blain but remember, I used this very same memory successfully at PC2700 at the fastest timings on my Epox 8K3A+ board for weeks. No problems. If only it would have migrated to the 8RDA+ smoothly.
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Originally posted by: Blain
When you say you've run the CPU at 166 using various multipliers, have you tried 166 FSB with a 10.5 multiplier and default voltage?
I'd suggest disabling all the "onboards", keeping the PC2700 at conservative settings, starting at the CPU's default speed on a 166 FSB and working your way up from there.
I don't think I went down all the way to 10.5 but I know I went to 11x. Same results. The voltage was elevated though. I think I'll try your suggestion when I get home from work today. And I can disable the onboard LAN with no problem as I have a 3Com NIC standing by but I hope it's not necessary to disable the onboard sound. I sold my TBSC to help the purchase of the 8RDA+.
 

Blain

Lifer
Oct 9, 1999
23,643
3
81
It's bsically stripping everything down as much as possible.
1. You know the RAM will run 166 fine.
2. The MB & CPU are fresh and unproven.
3. The MB's been flashed and has a good track record of 166. The CPU stepping also has a good track record for OCing.

That's why I wouldn't bother starting at 133. The XP may not require extra voltage to run it's default MHz even on a 166FSB. My MP will run its default MHz on a 166FSB and default voltage.
 

mboy

Diamond Member
Jul 29, 2001
3,309
0
0
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
 

Megatomic

Lifer
Nov 9, 2000
20,127
6
81
Thanks for the replies Blain and mboy. I will elevate the Vdimm and Vcore again (this time 2.77Vdimm and 1.775Vcore) and try to run at 10.5x166MHz. If that works, I will elevate the multiplier until I get failures again and stop there.

mboy, I never was overclocking the RAM, it is PC2700 and I never ran the memory clock faster than that. I ran it per SPD several times and my system still crashed Prime95. :(