im gonna try this as soon as possible
this may explain how my cpu will only prime at 2.725 but will pi at 2.925 i thought those figures should be closer hmmm
ill try to report back
________
Honda ST series (minibike)
Printable View
im gonna try this as soon as possible
this may explain how my cpu will only prime at 2.725 but will pi at 2.925 i thought those figures should be closer hmmm
ill try to report back
________
Honda ST series (minibike)
Anyone with a non DFI nf4 board had any luck with this tip? So far, it seems to be only those with a DFI board that have had increases. I'll be testing on my Neo2 when my new chip arrives, hopefully tomorrow.
It's too soon to draw conclusions, but it would appear the commonality so far is a NF4 and the Venice core.Quote:
Originally Posted by CD 1986
Maybe the OP could keep an updated list of those people/configs that see improvement in turning off DEP? :stick:
Didn't help at all here, still stuck at 2.5GHz with 1.8v on my 3000+.
Did'nt help me either but.. i only have a FX-55 .130 core.
Winchester or?Quote:
Originally Posted by Walrusbonzo
:) Actually DEP doesn't ask much, it simply terminates application which tries to execute code from unallowed memory location.Quote:
Originally Posted by Jimbo Mahoney
It has nothing to do with antivirus software - different things.Quote:
Originally Posted by ettis
Think of DEP as protection from threats using buffer overlow for example, implemented on hardware level.
And serlv posted some excellent links there! Read on friends :)
This may sound stupid - but I wonder if this is what makes prime fail when OCCT and SuperPI 32m pass?
Trying it now....
another thing that would suck about this would be having to back off clock speed during a format & reinstall since it wouldn't be stable with DEP enabled....
Doing this actually gained me a few more fps in Q3 timedemo.
Sweet. I did this trick and I can now hit 2.7GHz....possibly more. I've never gotten past 2.645ish before, and I'm using a "Winchester". Try it and if it helps you great, if it doesn't then you can always change back to original boot setting. It feels like a new door has been opened for me :)
Could this be a solution to the 1T problem on the A8N-Sli you guys reckon?
Its a feature that every other ISA has had for many years that was not included in x86. AMD recently added it, and Intel followed suit. Basically it protects against some types of buffer overflow exploits. Turning it off will leave you somewhat more vulnerable to this class of attack.Quote:
Originally Posted by stryg
I'd be more concerned about why this was effecting your overclock. Its a physical circuit on the processor. If your system was so marginal that enableing a simple NX check crashes the system, its probably a good idea to back down a few MHz anyway.
Except for the fact that the difference can be dramatic.Quote:
Originally Posted by saratoga
For me, I simply could not boot into windows with more than 2.6 - 2.7 Ghz.
With XPSP1 or Win2k, I could prime all the way to 2.8 Ghz and 2.9 Ghz was SuperPi and 3DMark stable.
You don't format and install windows w/ your system Oc'ed do you? I hear it's bad, and it's not like it speeds the install up that much... if anyQuote:
Originally Posted by dnottis
I have to give this a try, I got stuck at a high 2.5 :( winnie 3200, but then I have CBBID anyway...
No increase here (yet). Neo2, winchester CBBID....
Could DEP, therefore, also have any bearing on the lower 3Dmark scores that people see with WindowsXP SP2 as opposed to earlier versions?Quote:
Originally Posted by B5I8
i would say so :)Quote:
Originally Posted by CD 1986
Quote:
Originally Posted by A Scream
yea, but my overclocks are 110% stable not a 1 time 1M Super PI run like most of the people on XS. I prime for over 24+ hours, Super PI32M, OCCT etc and do this multiple times a week. My overclocks are permanent once they are deemed stable.
Dean
It's not too difficut to lower the multiplier one notch when you're formatting and installing windows though! ;)
true, but I never would ;)Quote:
Originally Posted by CD 1986
I found that very wierd I can prime 24 hours @ 2.9ghz, did that tweak and prime failed in 9 minutes :stick:
I guess I wouldn't know because thats the first thing I change ;) A good 90% of the non firewall compatability issues with SP2 are resolved by making this change.Quote:
Originally Posted by Jimbo Mahoney
Eric
tryed it in win64 and a san diago on a dfi board. it didnt help my prime stable clock unfortunatly, but easy enough to try. didnt check any 1m super pi runs though :ROTF: