PC3500 corsair of course.
224 2-3-3-5 works a lot better 4 me than 225 2.5-3-3-5.
Printable View
PC3500 corsair of course.
224 2-3-3-5 works a lot better 4 me than 225 2.5-3-3-5.
That's pretty good King.
I just backed my ram down to 218 so i can top off the CPU at
2506mhz.
I think this is the sweet spot for the CPU and the ram together
218 x 11.5
Now I'll play with the ram timings. I should be able to tweak it better since it's down to 218 now.
I'm running 2240 MHz with 10x224 instead of 2300 MHz @ whatever.
I need more VCore 4 running one 3DMark loop with 10.5x227 MHz (highest benchable FSB) but i need at least 2.1V to bench @ 2390 MHz. But cut a trace??? It isn't removable, or?
BTW : Never thougt a corsair PC3500 would hit his limit sync 2 the FSB. I love this board. With S-ATA, VDD, Soundstorm and a better Vreg it would be THE board!
Let us c, what 8RDA2+ will bring us?
I just put my system up with the 8RDA+ and i have the vcore shutdown issue. It dies over 1.9V. I think this suck and after the weekend i will put back my 8k3a+. Maybe i will mod the board but it sucks to have to mod a new board thats suppose to do 2.2V vcore.
I had posted some problems above and was wondering if anyone has heard of the vcore messing up and frying the processors. I have an xp2100+ tbred and i had upped the vcore to 1.75 to see if t could stablize the 8RDA+ to a high clock speed. It was working at 10x200 fsb. Temps were ok and when i changed the vcore the system bios booted and then there was a blank screen. I thought i had fryed the chip and shut down. I checked it out and it seemed fine, no melted spots and it did not smell burned. I reset the bios and tried again, but nothing. I loaded an Athlon 1.4 from an older system and tried it again but the same results, although when i placed the Athlon 1.4 back in the old system, Blank screen!
i took the chips to my friends and loaded them on his system and the same results although his chip loads fine, so it cant be the system. Im am thinking that this mobo fried both chips and am uneasy about trying another chip because it might or will fry again. Is there a way that this motherboard can stay stuck at a higher vcore and fry the chips???
Will they refund both the mobo and the chip cost- ?? any help here would be appriciated. thanks-
Just curious...are you guys running the REV 1 or REV 1.1...I had somewhat similiar problems (couldnt ran after 1.95v's) with the REV 1 board, but so far, have not had the same problems with the new REV 1.1 board. I can run 1.95v's and higher without a problem now.
BTW - My REV 1 board fried after running it at 1.9v's for a few weeks straight.
ok im having some serious issues with the High Vcore shutdown with my 8RDA+ and its very strange i was using my XP-2000+ Tbred at 1.85volts for a few weeks without any trouble at all but the other day i installed XP-1700+ Tbred A witch has a default voltage of 1.5 volts now when i try to change the Vcore from the default to 1.7/1.85/1.9 etc i will then save my settings but seconds into the POST my system completly powers down and i need to reset BIOS WTF is causing this?
now i found something very interesting the system only shuts off if i do big voltage leaps for example if i go from the default of 1.5volts right up to something like 1.85 or 1.9 i will get the system shutting off just seconds into post BUT if i increment the voltage slowly like start at 1.6 reboot go back into BIOS and keep increasing the Vcore by .5 volt increments it will let me get all the way up to any voltage i want
also if i power down the system it will shutdown upon post so the only way to keep it alive is to keep restarting
so WTF is going on here is this the case of the high Vcore shutdown problem?
GR,
Sorry to hear you lost a couple of processors, that sucks! :(
You can RMA the board to the place of purchase or EPOX if it's not modded in any way. I don't think you'll get any cash for the CPUs though. If either of them was retail boxed then you could probably get it replaced by AMD. I haven't seen any other reports of an 8RDA killing CPUs. Don't try any more!
Glock,
This issue affects both revs 1.0 & 1.1. I had one of each and they both had it. My rev 1.1 is still running fine with no shutdowns since I posted the mod.
what i am experiencing is not a shut down, but more of a instant reset. the system stays powered on but instantly reboots to the bios post screen. this seems to happen when i run my vcore@2v+ is this the same thing as the overvolt problem?
I really need a photo of this how does this chip set when on the board???? I am doing LN expiriment tommorrow and i really need this
http://8rda.com/upload/8rda_vcore_mosfet1.jpg
ok here you go .you can see where i removed the resistor.....
and the rebooting problem will not be cured by this mod......rebooting....i bet it does it while you are benching the pc ..like 3d2001 ?
this comes from unstable memory.or cpu setting...but my money on the memory.been though that prob for weeks.just try lower memery timing and or lower the fsb untill you can bench with out the reboot.also helpped me when i got close and just rebooted slightly at times is to reload video and the reload bench program..
that seams to help..;)
you are right. i experienced the rebooting while running 3dmark2003. i will have my TwinMOS 3200 tonight. (winbond -5ns) i will see if its the pc 2100 running at 147@ 2100 being the culprit.Quote:
Originally posted by bowman1964
ok here you go .you can see where i removed the resistor.....
and the rebooting problem will not be cured by this mod......rebooting....i bet it does it while you are benching the pc ..like 3d2001 ?
this comes from unstable memory.or cpu setting...but my money on the memory.been though that prob for weeks.just try lower memery timing and or lower the fsb untill you can bench with out the reboot.also helpped me when i got close and just rebooted slightly at times is to reload video and the reload bench program..
that seams to help..;)
what didi that mod do to your system then if it didn't resolve the rebooting issue?
well some of us had problems running high vcore.anything close to 2.0v would cause a sudden shutdown of the system.i didnt have the trouble as bad but i wanted to get some high benches.and i was having reboots so i thought it might help that too.but only memery has anyhing to do with that.Quote:
you are right. i experienced the rebooting while running 3dmark2003. i will have my TwinMOS 3200 tonight. (winbond -5ns) i will see if its the pc 2100 running at 147@ 2100 being the culprit.
but there are some nice people who like to help... but one thing i noticed.the guys who know and are at the top dont like telling all there secretes too easily.so i found out the hard way.and for benching thats another story.but memory will help your problem
P S i took that pic myself of my board.as all my posts only use my pictures.i dont mind people using mine.but i only use what i actually have done:toast:
How did u remove it i thought u were supposed to cut a line not actaully removie something
so its a total system shutdown, and not a system rebot people are experiencing?:stick:Quote:
Originally posted by bowman1964
well some of us had problems running high vcore.anything close to 2.0v would cause a sudden shutdown of the system.i didnt have the trouble as bad but i wanted to get some high benches.and i was having reboots so i thought it might help that too.but only memery has anyhing to do with that.
but there are some nice people who like to help... but one thing i noticed.the guys who know and are at the top dont like telling all there secretes too easily.so i found out the hard way.and for benching thats another story.but memory will help your problem
P S i took that pic myself of my board.as all my posts only use my pictures.i dont mind people using mine.but i only use what i actually have done:toast:
yes this fix is only for a shutdown from the ovp chip.
and yes you can cut the trace as i did first.
but it is easer to remove the resistor i found with a soldering iron.
here is a pic that you can see the cut better in.you notice i connected a vr resistor to the solder points .this way you still get use of the shutdown.but in the end i just removed the vr and run without anything....i know now i can run up to 2.2vcore with no problems.
so, to test if i have this problem i would set the v core to 2.2 and try to run prime 95 or 3dmark. if it shuts the pc down totally, then i have to do the mod, but if it just resets the pcs and starts to boot on its on, then its maybe my 2100 sammy @ 150 thats the culprit?:stick:Quote:
Originally posted by bowman1964
yes this fix is only for a shutdown from the ovp chip.
and yes you can cut the trace as i did first.
but it is easer to remove the resistor i found with a soldering iron.
here is a pic that you can see the cut better in.you notice i connected a vr resistor to the solder points .this way you still get use of the shutdown.but in the end i just removed the vr and run without anything....i know now i can run up to 2.2vcore with no problems.
Is this d reason why my board shutsdown when I set my 1800+T-Bred A @ 170FSB?
I already change to water block cooling.
Some say its my power supply. Is it so?
Just like to know also is it safe to find the stable highest Real Clock Speed?
Is the CPU thermal protection effective, already E-mailed the EPOX headqrtrs but didn't give a helpful answer but said they don't condone overclocking & board water cooling.
Thanks for those who would help!
My gear:
300 Watts iCute(www.casepower.com.tw [model 42h-p CASE])
8RDA+ jan 29 Bios
Thoroughbred A 1800+ (RIRDA Stepping)
Samsung 256mb 2700 cas2.5
GeForce Ti 200 64mb
Maxtor 40 & 20gb 7200rpm
PLexwriter 16x, LiteON 52x writer
Internal Modem
Pinnacle TV Tuner
4pcs case fans
Listen guys the real fix for all these probelms is the new revision 8RGA+ that use a separate 12v connector just for the CPU.
This is how the board should have been made in the first place for overclocking.
I fixed my problem by cutting Pin 16 on the 3055 IC vcore chip, putting heatsinks on the Vcore VRM IC, and on all the mosfets.
I'm not running my 2400+ at 2703 using a Prometeia and at 2.1v
I ran Prime yesterday for 11 hours at 2.1v
No shut down no reboots. I'm also using a Antec True Power 430 Watt PSU.
Worked great for LN2 expiriment and i ran 2.2 vcore at 3172, Removing r678 was the best mod i could done. Thanks for making my OC possible
Quote:
Originally posted by youthemandan
Worked great for LN2 expiriment and i ran 2.2 vcore at 3172, Removing r678 was the best mod i could done. Thanks for making my OC possible
You're welcome! ;)
Very interesting info guys! Thanks. Couldn't figure out why the board kept spontaneously rebooting for no apparent reason. Turns out that this Sparkle PSU is supplying more current than the Antec I was using. With the Antec I was fine at 1.95v, but with the Sparkle I get random reboots. I thought it was condensation, but the machine works fine at stock volts. I'll be doing the mod later on today. I'll keep you posted as to how it works.
DoGMaN,Quote:
Originally posted by DoGMaN
Very interesting info guys! Thanks. Couldn't figure out why the board kept spontaneously rebooting for no apparent reason. Turns out that this Sparkle PSU is supplying more current than the Antec I was using. With the Antec I was fine at 1.95v, but with the Sparkle I get random reboots.
I don't recommend this mod for the symptoms on your board. It's not for random reboots, only shutdown problems at high Vcore.
It's the other way around on the Sparkle vs. Antec issue. Power supplies have a certain amount of current that they are able to provide, but they don't push current through the mobo. The mobo DRAWS CURRENT from the power supply. The power supply does however PUSH VOLTAGE to the mobo. I know it's a subtle difference, but it can be an important concept to keep in mind when troubleshooting.
My Sparkle 400W works fine on my 8RDA+. Your Sparkle may be too weak (or not a 400W model). It's really critical to use a good quality, high wattage PS on this board.
My Sparkle is a 460W. I don't think its having any issues keeping up with the board. Maybe I'll just pitch the Antec back in and let it be.
I guess the reason I thought it was over current protection, is that it has the symptoms as you described. Only the board does not shut down, it reboots. Only at 100% load and completely at random times. Very odd indeed.
There ya go. That's what I would do. ;)