Epox 8RDA+ - Shut off at high vCore

[CCW]

Im on the wat to 2.5GHz at the moment bu to get there I want to use 1.9v at least. However I thin kmy board might have the 8RDA+ high voltage shut off bug except Im not totally sure it is. When this bug was first discovered in January this year by Spartacus he reported the system shutting down completely however after raising my voltage to 1.9v or higher on pressing F10 to save new settings and rebooting I just get the EF error code on the 8RDA+ Debug Panel. So the system does not actually completely shut its self down, I then have to shut it down (basically, pull the plug as Im running caseless), clear the CMOS and boot back up. So does this mean it is the 8RDA+ high vcore shutoff bug? As my system does not completely shut downa and also what is the EF code please? I am unable to find it in the BIOS. Ive just been reading about the bug here at MotherboardFAQs and here on Xtreme Systems where Spartacus originally posted his findings about this bug. This is why Im not sure if this is stopping me booting at 1.9volts as my system does not completely shut down, it just displays EF on the debug panel and i have to clear the CMOS.

Any help you can give me is appreciated!

Thanks,
Craig

[CCW]

*Bump*

[AcEmAsTr]

bump for mate

[Devilman]

As I said RE: my post, its definatly not the bug which was discovered earlier in the year with the 8RDA+

That bug is actually an over-current protection kicking in, which symptoms are different. And since over-voltage seems to be something which completely kills the system (refuses to power up) its not that either.

I dont know exactly what *is* going on and without access to various other hardware which is known to take / give high Vcore successfully, I cannot test it any further.

What I have come up with, is the fact it seems to be the chip which is at fault, not the board. That is unless epox have, for some reason, implimented chip-based overvoltage (which changes when different type CPUs are in the rig), which I find doubtfull.

What I really need, is access to both a Barton2500+ which is known to take Vcore in excess of 2.0v and another board (preferably another 8RDA+, for consistancy) that is known to be able to give in excess of 2.0vcore to a Barton 2500+ (that bit is important tbh. We need to keep the systems the same to prove whats going on, I already know my 8RDA+ will give in excess of 2.1v on the core to a duron, but that doesnt prove if it will to a Barton 2500+)

[CCW]

I know and understand this which is why I am bumping this thread to see if someone can answer and knows why I am having this problem as it is not the over-current protection kicking in. Im bumping this thread to see if someone has any more ideas.

Maybe Holst may know...

Craig

[Evil_Spork]

i have the same EXACT problem. cpu speed and all.

ill test it with my 2100+ thats known to love voltage. if it still locks its my mobo. it not then its my 1700 not liking voltage.


*edit* ive done the hgh vcore shutoff fix, no help.

[Holst]

What revision board is this?

I assume you have lifted pin 16 on the vreg (rev 1.1) to disable the OCP.

What voltages are you running?

[Devilman]

Well, while I cant speak for others, on my board (which I think is a 1.1), I have done the over-current mod by lifting pin16 and it still goes bad with the barton in there.

With my duron in, its fine, taken it up to 2.1 without any hitch, but with the barton, I think its about 1.875 and it gives up.

[CCW]

Originally posted by Holst
What revision board is this?

I assume you have lifted pin 16 on the vreg (rev 1.1) to disable the OCP.

What voltages are you running?

I havent disabled the OCP by cutting pin 16 on the vReg chip, the initial post is asking if this will fix the problem as thats what I was wondering. I was running 1.825v fine but now it starting to seem like it doesnt like it or higher voltages even when CPU temps are perfectly fine.

Craig

[Devilman]

From what I have read of the overcurrent problem (which is what pin16 controls on the VREG) its not what you have.

Overcurrent seems to usually kick in once the system has booted and "settled down" and tends to shut the rig down after a few mins.

Have you checked what the error code your getting means in the back on the manual?

[CCW]

I couldnt see it in the manual, that was the first thing I checked...

[Devilman]

Originally posted by CCW
I couldnt see it in the manual, that was the first thing I checked...

Interesting. since when mine locks up, I seem to remember I get error code 01, which I couldnt find in the manual either

[CCW]

weird *bump*