Ditto about the Vdroop comment from loonym...not bad at all...it is a VERY acceptable droop.
Printable View
Ditto about the Vdroop comment from loonym...not bad at all...it is a VERY acceptable droop.
Hmmm...well if the vdroop I'm seeing isn't too bad...maybe my chip is just not the best.
How high is 'safe' to go on vcore for a Q6700? I think I have my q6700 at 1.385 right now and I seem to be stable at only 3.2gig :(
I was hoping to hit 3.6 gig with this chip, but maybe that won't be happening. I haven't really tweaked my settings much yet, so maybe there is some more tweaking I can do. I am also using water cooling...so my chip stays fairly cool.
Basically all I have done is to change my memory multiplier to one that keeps it running in spec and upped vcore/vdimm voltage and upped the FSB. At 3.2, I was getting prime95 errors and I've had to raise the vcore to about 1.385 to make it stable.
How much higher can I try to raise the vcore? Are there any other tweaks I should be doing to help my OC at all??
Right now I'm just trying to find the limit of my cpu, so I will try to max out my ram later...
1.385v is nothing for a Q6600, especially for one under water.
I'm currently using a q6600 in the IP35-pro. The main voltages I concern myself with to get me stable are vcore, vdimm, MCH, ICHIO, and the gtl ref settings, although I also follow the suggestion here of setting ddr2 ref to +2% since it's never hurt me :)
Keep an eye on pwm temp since that is known to get exceedingly hot without extra attention. I think it's best to try and slowly nudge some of these voltages up and try to find your own best settings although there are many examples of people's successes posted throughout this thread that you could copy as a baseline.
Good to know...Quote:
Originally Posted by Cob
So what can I go up to on water safely? 1.40, 1.45, 1.5??
Whatever keeps your load temps below 70c tbh.
Tho everybody has their own ideas on what max load temops should be.
I was woundering if any one else tried my cpu ram compinations, because I am having some trouble setting clock, according to cpuz it is always 399 even though in uguru it says 420. My system give me a speed of 3.19 so i'm assuming cpuz is correct. does anyone have any suggestion as to what could be wrong, I hope it's not ram forcing the clock. I also tried both bios 16 and 17b04 and they both have the same problem.
i would say to hold 3.6 ghz under a P95 load will require vcore under load to be around 1.42 to 1.45...that is load vcore not idle vcore.Quote:
Originally Posted by bobn4burton
to support that P95 at 3.6 Ghz, pay attention to your FSB, MCH, ICHIO 1.5 and Vdimm.
i would try about 1.25 FSB; 1.48 or 1.5x MCH; 1.60 or 1.65 ICHIO and 2.0 to 2.1 Vdimm.
good luck!:)
Quote:
Originally Posted by spunlex
first of all, what bios are you using and what version of Uguru?
http://www.rebelshavenforum.com/sis-...;f=37;t=000124
a new addition to the ip35 bios!! from polygon @ rebelshaven
+1 for Avast. I've used it for several years and it usually catches everything. The one time it didn't was recently a virus came through a Steam server twice (once on DOD: Source then on TF2). Didn't activate until I started my browser - then BAM!Quote:
Originally Posted by Ace-a-Rue
Effed things up pretty bad the 1st time, had to do a complete wipe/reinstall. The 2nd time Avast caught it tho'.
Avast also uses much less in the background than AVG, but most of the unneeded AVG stuff can be turned off.
hmmmm...interesting stuff...i'll get around eventually to trying it..hehehe
sounds like the 2nd time the code for the virus pattern was written to catch it coming via that port...sounds like you have another dimension in accessing the net.Quote:
Originally Posted by aztec
Or just bad luck.Quote:
Originally Posted by Ace-a-Rue
Thing is, I though Avast would have caught the 1st one since I force update it at least daily, not counting whatever auto-updates it does. Also I didn't have it set to boot-time scan but I do now.
Quote:
Originally Posted by aztec
you know that you can set the updates to every 30 minutes by going into "Program settings" (right click on the "A" blue icon).
also, there is "On-Access Protection Control" that allows you to increase "Resident Protection" from "Normal" (default) to "High"
Of course I've been through the settings, Ace. :) All were at "High". But I don't want it updating that often. I do it manually and it does auto as soon as any update is ready anyway. Most likely Avast didn't have a fix for that particular virus yet.
I don't like a boot-time scan on every reboot, but the short wait might be better than a virus not getting picked up in time.
I am currently susing a beta bios 17.b04, but I had the same problem with bios 16. I am using the bios to atempt to oc, but I am using uguru version 3.1.0.3.Quote:
Originally Posted by Ace-a-Rue
that uguru version is the wrong version to use...i am using 3.107 and i found that to be the best and most accurate.
that should be a good bios...i am using it but it is the modded version, which is fine but about the same as 16.B10 which i was using for an extended time.
Quote:
Originally Posted by aztec
don't take it personally!;)...just making sure you were aware.
I just updated my uguru, but I am still getting the same problem. Which ap can I trust more, cpuz or uguru?Quote:
Originally Posted by Ace-a-Rue
Quote:
Originally Posted by lefy
i have the same problem with cpuz showing 1.64 volts. it happened ever since i updated to bios 17. i have every thing as auto in bios except the vcore i set to 1.225. uguru and everest show the correct voltage that i have in bios. idk whats up with the cpuz reading either. :confused:
Uguru is the one to believe...the Vcore will be within 0.01v...on my board, it was more like 0.005v within actual as i measured it with a DMM.Quote:
Originally Posted by spunlex
CPUz is a very good program but take it with a grain of salt when it reports the vcore.
ok thanks, which one for bus speed?Quote:
Originally Posted by Ace-a-Rue
No offense taken. I just let you know that I had been through the settings.Quote:
Originally Posted by Ace-a-Rue