• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Overclocking problems with E6400

B

Backslash

Weaksauce
Joined
Jul 15, 2006
Messages
95
I'm currently running an E6400 and P5B Deluxe, and so far I'm extremely impressed with the overclocking potential of my E6400. I have it undervolted to 1.1v, and even then it's still going strong at 2.712 Ghz (339x8). I didn't expect it to overclock that much at such a low voltage. I have a feeling I could push it even more without raising the vcore.

However, even though I'm able to run dual prime with no problems for 10 hours (or more, I didn't have the patience to run it for longer) at that speed, I get a "not exact in round" error in SuperPi 32M within a few seconds. I'm running my Corsair memory rated at DDR2 800 5-5-5-12 at DDR2 678 5-6-6-18, so I'm fairly sure sure my memory's not the problem. All voltages other than vcore (1.1v) and vdimm (1.9v) are on auto.

So what's my problem? I know it isn't the CPU or the memory. Does small FFT prime test motherboard FSB for stability?
 
Maybe I'm missing something, but why are you undervolting the C2D again? I can see someone doing it if they're going to try for a quiet environment with passive cooling, other than that... :confused:

Does it pass the tests at stock voltage?
 
Go back to stock voltage and see if it errors out. Keep lowering the voltage until you get the error.
 
All right, I'll try that. I'm pretty sure it isn't the CPU because it's prime stable for 10 hours, but you never know.
 
Okay, I've been diagnosing the cause of the BSOD and it seems to be an unrelated problem. Apparently, the driver "aegisp.sys" is corrupted. Anyone have any idea what this is and what to do about it?

And also, does anyone know why I'm getting the rounding errors in pi?



EDIT: I'm editing this post to avoid quadruple posting.

I've figured out that "aegisp.sys" is a driver that was installed from my motherboard driver CD with the Realtek wireless ethernet driver. I tried replacing it from the motherboard CD, but driver verifier was still BSODing. Apparently it's a noncritical file and used in only certain situations, so I just deleted the damn thing.

Well, that problem's solved. Still haven't figured out what's causing the round error in pi though.
 
You must log in or register to reply here.
Back
Top