Road to Perdition (ub3r OC)!

Status
Not open for further replies.
Hey........

My core 0 is super weak. Core 1 is much stronger. But I will use brute force. For now I have set my target at 2.7 Ghz @ < 1.5 Vcore for 24/7.

Now running @ 2.601 Ghz but Prime95 fails within 1 sec on Core 0. So running K7BURN on it right now.

The rails seem stable........ idle @ around 12.18 V and when both cores full load, comes to around 12.05 V. +5V is unaffected :D (rock steady @ 5.01V) All this from DMM, not from Comp Sensors.

Also, now I have configured SpeedFan nicely and it is helping me cut down the noise levels immensely when I am not on full load.



I could hv been luckier with a stronger core 0......... but heck, you cant have everything na :D
 
goldenfrag said:
Use nalla roll walla camera and get the Pics scanned :bleh:...
Post some scores biatch....
4th page of your Overclock thread and no scores by you yet.
Wth are you upto :bleh:

Edit : Btw, what is a DMM called in India Lang? No guy hre understands if i say DMM :S..
Click to expand...
this is known as the Sampsa effect :D
 
give it 1.5 or 1.525 and run it at 2.7

see if it primes on both cores on that voltage or not.

And let it burn in on dual prime.

And afterall even 2 exact same stepping cpus dont always oc the same. Switch would back me up on this ;)
 
Agree with funky... Same steppings doesnt at all mean same results.. Overall they will perform same... Out of ten if one reaches 3G then 7 will reach 2.8 for sure... 2 will have trouble reaching 2.6...
 
kiddo gr88 continue ocing :bleh:
dont forget to blow up something over it orissa is real real real hotttttt@!!! place.
 
Hmm, a little unoptimized Sp1M run.



Also, check out the idle temparatures. I hope things will improve a bit further once i lap the HS base and apply some AS5+

My current quest now is to make my CPU stable @ 2700 Mhz. Funky, i tried 1.53 VCore @ 2700 Mhz. Core 1 as usual was a winner. It was happily priming away. I knew for a fact that Core 0 was unstable, so didnt even try SP2004. I just started a BURNK7. Then I got a BSOD. Ah well looks like it is not even BURNK7 stable @ 2700 @ 1.53 Vcore. I have dropped the HTT to 295 now and am gonna do burn in sessions. Lets see where i can take this baby.

Regards,

Karan
 


This i obtained after i started the AirCon. The ambient temparature inside the case was around 27C (checked using a thermometer) as the AirCon is situated across the room. So the Hyper6+ is preety efficient eh? (only about 5C delta over ambient at idle)

Edit: Now running 100% dual load without (ambient temp inside room = 27C, its higher inside cabby due to crappy fans)



Lets see how long this runs....
 
hmm.

Weird, at that voltage i expected it to hold at 2.7ghz.

anyway what are the background services running.

I got everything nice and stable only after fresh install of windows and installation of AMD drivers and DC fix patch.

Before that it was never 100% stable.

If one of the core is failind at 2.7 then run both at slower speed but keep dual sp2004 running. Let it burn in.

Also too many background services running on 1 core can also cause it to error in prime.

Best of luck.
 
funkymonkey said:
hmm.

Weird, at that voltage i expected it to hold at 2.7ghz.
anyway what are the background services running.
I got everything nice and stable only after fresh install of windows and installation of AMD drivers and DC fix patch.
Before that it was never 100% stable.
If one of the core is failind at 2.7 then run both at slower speed but keep dual sp2004 running. Let it burn in.
Also too many background services running on 1 core can also cause it to error in prime.
Best of luck.
Click to expand...

hmm, intriguing..... this is my old install of win2003 64 ee........... and because there are no DC patches released for this platform, i just did the /usepmtimer and the AMD X2 drivers install.

also, BURNK7 is more suited for the burnin process as it allows me to burn in at the desired speed (now @ 2655 Mhz) where as SP2004 would fail instantly. the crux of the matter is to make the cpu utilization 100%.

some food for thought:

[URL=http://img137.imageshack.us/my.php?image=37mins49c9ua.jpg][/URL]

i checked the rails again @ dual load and they are @ 5.01V and 12.03V respectively.

PS: remember the USP is also powering my monitor and my cable modem. so the PSU is holding out nicely.

@funky: man, how can u even say this "Also too many background services running on 1 core can also cause it to error in prime." lol all the processes, drivers and services are demand switched by default (they have no set affinity and will migrate as per demand based scheduling) and therefore there is no too many services in 1 core. you need special software to set their affinities to either of the 2 cores. (like your trusty old Task Manager)

but maybe i will try doing a fresh install of Windows XP 32 bit. Lets see...
 
I dont think a Frest Install of XP 32 will help your cause.

Just re-install XP 64.

Plus the Drivers thing which you have done is more than mine :bleh:...

I have just a Recognition Patch and the /pmtimer thing (Which you told me to do :P)..

So im more at loss :bleh:. I just wish i had Phase Change to push this damned CPU to 5 Ghz and then compete with you people :D :bleh:...

Anyways, nice scores Kido, let the OC Burn in :)...
 
kidoman said:
hmm, intriguing..... this is my old install of win2003 64 ee........... and because there are no DC patches released for this platform, i just did the /usepmtimer and the AMD X2 drivers install.

also, BURNK7 is more suited for the burnin process as it allows me to burn in at the desired speed (now @ 2655 Mhz) where as SP2004 would fail instantly. the crux of the matter is to make the cpu utilization 100%.

some food for thought:

[URL=http://img137.imageshack.us/my.php?image=37mins49c9ua.jpg][/URL]

i checked the rails again @ dual load and they are @ 5.01V and 12.03V respectively.

PS: remember the USP is also powering my monitor and my cable modem. so the PSU is holding out nicely.

@funky: man, how can u even say this "Also too many background services running on 1 core can also cause it to error in prime." lol all the processes, drivers and services are demand switched by default (they have no set affinity and will migrate as per demand based scheduling) and therefore there is no too many services in 1 core. you need special software to set their affinities to either of the 2 cores. (like your trusty old Task Manager)

but maybe i will try doing a fresh install of Windows XP 32 bit. Lets see...
Click to expand...

well windows xp 64 as your primary os is definetly a no no. ive got it instelled as my secondary os and its buggy as hell, even the new forceware driver, 8,3 i think are buggy and causes BSODs, id recommend you to do a fresh windows xp 32 install and then do further testing, if required, u can keep x64 as your secondary os...
 
Kido, what i meant is if you have any background services running that use considerable amount of cpu even in spikes the prime tends to fail.

If you are running prime at highest priority and suddenly if AV pops up warning prime fails sometimes or if you try to play some high resolution file while priming it can fail.

Either leave the pc idle or shut down things like AV and then prime. Prime is already stressing the core and if you have set the prime to high priority then if other service starts it sometimes causes prime to fail.

Just wanted to tell ya this happens.

And seriously drop x64 as your primary os for now. MS still hasent issued the fix for x64, and yes similar problem does exsist for x64 version too thats now patched in 32 bit.
 
funkymonkey said:
Kido, what i meant is if you have any background services running that use considerable amount of cpu even in spikes the prime tends to fail.
If you are running prime at highest priority and suddenly if AV pops up warning prime fails sometimes or if you try to play some high resolution file while priming it can fail.
Either leave the pc idle or shut down things like AV and then prime. Prime is already stressing the core and if you have set the prime to high priority then if other service starts it sometimes causes prime to fail.
Just wanted to tell ya this happens.
And seriously drop x64 as your primary os for now. MS still hasent issued the fix for x64, and yes similar problem does exsist for x64 version too thats now patched in 32 bit.
Click to expand...

lol i was just pointing out that "on one core" was a wrong concept. + u can never turn off all the services, some have to keep running (like the infamous RPC and all)

hmm i am thinking about switching to 32 bit...... but that would be foolhardy that many many software packages are being optimized for 64 bit now.

@Rave: the 64 bit forceware drivers are not at all buggy. they cant be, since they are just a recompile of the 32 bit version with changes to the word length. i have used 64 bit for over 3 months (when I had the 3000+) My system was rock stable. Just that the patch has not been released for 64 bits .
 
Last edited by a moderator:
YES!!!!!

Priming @ 2.610 Ghz now........ earlier it was unstable beyond 1 min. GG!



Burn in is already helping!

EDIT: Lol the P95 crashed after Test 5! So more burning in left to do!
 
funkymonkey said:
Kido, what i meant is if you have any background services running that use considerable amount of cpu even in spikes the prime tends to fail.

If you are running prime at highest priority and suddenly if AV pops up warning prime fails sometimes or if you try to play some high resolution file while priming it can fail.

Either leave the pc idle or shut down things like AV and then prime. Prime is already stressing the core and if you have set the prime to high priority then if other service starts it sometimes causes prime to fail.

Just wanted to tell ya this happens.

And seriously drop x64 as your primary os for now. MS still hasent issued the fix for x64, and yes similar problem does exsist for x64 version too thats now patched in 32 bit.
Click to expand...

hmm funky, hv a read.....

x64 based windows releases dont have the bug so dont need the patch, which is essential for a 32 bit windows release running dual core.

JUST IN:

funky, for the patch to work on the affected x86 oses (even after you have done the registry fix), you need to ENABLE Cool'n Quite..... SOURCE.... from what i understood, the symptoms only show up when Cool'n Quite is enabled. so no point in applying the patch when Cool'n Quite is disabled. just RTFA...

http://www.amdzone.com/modules.php?op=modload&name=News&file=article&sid=3964&mode=thread&order=0&thold=0

http://www.amdzone.com/modules.php?op=modload&name=News&file=article&sid=3951&mode=thread&order=0&thold=0

Some quotes from the Article:

Re: Windows XP SP2 Dual Core Performance Fix (Score: 1)

by _Shorty on Oct 08, 2005 - 09:56 PM

(User information | Send a message)

Don't forget, this only affects machines that have Cool N Quiet enabled. Disable that and then this problem won't affect you. It has to do with when the CPU changes speeds, and this only happens when Cool N Quiet is enabled.
Click to expand...
 
aare it throttles even now. with C&Q disabled.

That slow gaming issue is long fixed.

But throttling is still there, even with C&Q disabled.Thats the first thing i tried after having a look at the current sp2 issue.

It gave me BSOD with externam memory dump the minute i got into the windows xp x64 welcome screen.

In safe more it booted and installed all drivers and again on next boot gave me BSOD with memory dump.

Next boot booted and rebooted as soon as i started cpuz :@

Left it and installed 32bit. Iorny is i have legit copy of x64 :(

and it still does not support all my pheripheral devices.grrrr.
 
funkymonkey said:
aare it throttles even now. with C&Q disabled.
That slow gaming issue is long fixed.
But throttling is still there, even with C&Q disabled.Thats the first thing i tried after having a look at the current sp2 issue.
It gave me BSOD with externam memory dump the minute i got into the windows xp x64 welcome screen.
In safe more it booted and installed all drivers and again on next boot gave me BSOD with memory dump.
Next boot booted and rebooted as soon as i started cpuz :@
Left it and installed 32bit. Iorny is i have legit copy of x64 :(

and it still does not support all my pheripheral devices.grrrr.
Click to expand...

this is very strange yaar....... i hv no issues at all with any devices in x64. i didnt hv any issues with any devices. also, the crashes are because of a unstable core 0 and not of windows doing any thing with the CPU power. See it cant do it, unless CnQ is enabled. thats the whole point of it, init?
 
the two critical components that i have dont work in x64. One is printer and other is scanner. Both of them dont have x64 drivers.

Next time i format i will record a movie with my cam showing throttling.

And mind you both C&Q and thermal throttle are disabled in the bios.

And it does that abnormally.

There is weird behviour in windows even at stock speeds.

Atleast its fixed now for 32 bit.

For now its running nicely for me. 2.7ghz(1.48vcore) prime 2414 and dual sp2004 stable.

Running dual 2414 for couple of hours now.
 
I am hoping to reach to ur freq re...... slowly and slowly its getting more stable. And the good thing about dual cores is, u can arram se burn in one core while you are working/doing normal work using the other core.
 
Status
Not open for further replies.
Top Bottom