Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by graysky

  1. Cool... please do. What are you doing at work on a Sunday?
  2. @neddamttocs: I want the ability to switch from 9x266 @ 1.1275V to 9x333 @ 1.2625V. I just installed the latest AI Suite and it's stable. I can't find the option to set vcore though... can I dial in the vcore I want and where is it? What mode do I need to run it to access it (Booster or NOS)? Thanks!
  3. Interesting... too bad it crashes when I run it! What a POS.
  4. neddamttocs: are you sure? I actually had that installed but whenever I went to change the settings, it prompted me for a restart. Plus I can't do the vcore with it... are you using it?
  5. Thanks, that's cool. Too bad there isn't anything that can do vcore as well. Saving a few profiles like 9x266 @ 1.1125V, 9x333 @ 1.2625V, etc. would rock; sort of a shift-on-the-fly o/cability.
  6. Here are the results from little experiment I just finished wherein I ran p95v2 with 4 threads doing large FFTs for ~1 h on a Q6600 @ 9x266 under two different vcores: 1.2625V in BIOS or 1.232V in CPU-Z and 1.1125V in BIOS or 1.080V in CPU-Z. I had the logging disabled so these aren't average temps, just "instant" temps although I they really did level out. Results @ 1.232V: Core0=55 Core1=56 Core2=51 Core3=52 Results @ 1.080V: Core0=49 (6
  7. It's too bad. I have all the settings worked out for a 9x266 and 9x333 w/ minimized vcores. I'd be nice to switch between the on-the-fly.
  8. I think the answer is "no", but here goes: is there a utility (or more than one) that allows one to alter BIOS settings from within Windows WITHOUT restarting? For example the AISuite from ASUS requires a restart as I understand it and it can't modify the vcore. I'd be most interested in changing these two parameters specifically: FSB and vcore. Thanks!
  9. Read my experiences w/ a q6600 here. Get wet/dry high quality sand paper. Cut it into thin strips and tape the strips down to a piece of glass or mirror (something flat). Lap using front-to-back motions with minimal pressure; let the sandpaper do the work and remember: the key is FLAT. You can do about 20-30 strokes, then rotate 90
  10. No hard feelings at all... I guess that stupid angry face icon I used gave the pissed off impression on my part. Thanks for the compliment. Truthfully, I found this place through an unrelated google search and figured it'd be good to post a few threads I put a little time into with the hope that people will find the information useful; it's always good to give something back to the community. @kingdingeling: that's why I posted it and other threads on multiple sites. Just casting a larger net I suppose.
  11. From what I've read, front-to-back/back-to-front is the better technique since circular or figure-eight motions can introduce uneven surfaces; you have more control when you minimize the angular motions. I have always used soapy water (like 1 drop of dish soap in 1 liter or so of water). I wouldn't recommend that you do it without. The water lubricates as well as immobilizes the metal partials. As to your last question about 1000 or 2000 grit... I think the most benefit you'll get out of lapping is a flat surface; you can make it smooth beyond say 600 or 800 grit, but as I understand it through reading, the extra mile doesn't give you much if any additional benefit.
  12. Thanks for the kind words, hardnrg. I'd caution you about extrapolating beyond the upper and lower range of the graph though; it may not continue to be linear.
  13. Plus, C2D and C2Q chips don't have any pins to bend which makes it much easier
  14. Jammin hit the nail on the head: as long as the vcore you've selected falls within the manufacturer's range. For example, Intel gives a range of 1.100V-1.372V for my processor. I dunno about the FX55, but I'm sure you can find out from AMD.com
  15. The overclock should scale with voltage, or I think really the overclock is a function of the vcore. It [overclock (given FSB x given multiplier)] can be limited by the temps produced, but long as that overclock is stable to an others test for a good amount of time @ the vcore you're running, you will be minimizing those temps by running at the lowest vcore that's stable. Does that make sense?
  16. Of course it is! :angry2: I do reference other materials in my guide, but provide credit to the original authors.
  17. Wow dude, I dunno about the dented part, but when I called TR and asked if that rough, uneven surface was normal the tech told me it was that way *by design* which I didn't understand. Unless... it could be that they think or have some lab tests etc. showing that more surface area gives better contact. I find this hard to believe given my results. More than likely, TR does it this way to maximize profits or they didn't design it like this at all, and these are made in China where quality controls don't exist. Maybe these are no different than the recently publicized poisoned toothpaste, pet food, etc. that comes out of that country. You ever read "The Jungle" by Upton Sinclair?
  18. @hardnrg: Glad you like it. Always glad to give back to the community. I wasn't aware of 120mm fans that exceed 1600 RPM. That's really a lot of mass to move that fast when you think of it. How fast and how loud are they fastest ones (probably deltas)?
  19. Cool (literally)! That would be consistent with these findings as well. We usually keep the place pretty cool in the winter since gas prices are so high; I will say that this past winter my machine ran really cool under full loads. That kinda prompted me to do this experiment to try to understand the effect better. Cheers.
  20. I read Verran's Guide on overclocking basics of Core 2 Duo chips but wanted to post my own guide. He did a great job, but mine is sort of a different flavor of chocolate. Have a read and see if you find it helpful. Edited on 08-Jun-2008: Guide is now version 1.7
  21. Sounds pretty simple, but you'd be surprised how many people don't know about how much vcore can affect your load temps. Temp and frequency (FSB) have a linear relationship whereas temp and voltage have an exponential relationship. Conclusion: minimize voltage. Here is the Intel document that helps explain it, see page 31: Same thing holds true for speed in a car: energy = 0.5mv^2 where m is mass and v is velocity. This is the basis of the old expression, "speed kills." You generate way more energy driving 75 MPH than you do driving 55 MPH since energy and velocity have an exponential relationship. Anyway, to test how low you can go, simply manually set your vcore for something low. I started @ 1.2375 for my Q6600 running @ 9x333. If you can boot into windows load up a couple instances of orthos. If you have a quad make sure you set the CPU affinity such that one of the orthos gets cores 0 and 1 and the other gets cores 2 and 3. Let em run for a while. If the vcore is too low, one or both will give an error message. Orthos checks e when for rounding errors that can occur when the system isn't stable due to vcore, or temp, etc. Using a vcore of 1.2375v for my system gave an error pretty quickly: If you don't get an error after say, 30 min, lower the vcore in the BIOS and repeat until you do get an error, then start working your way up until you can run them with no errors for a good 6-8 hours. In a nutshell, that's it. Enjoy.
  22. I was curious just how much room temperature can affect the temperature of the PC. I chose to look at the CPU since Speedfan can monitor and log temps for each of the 4 cores in my Q6600, and since of all the components, the CPU is probably the most sensitive to changes in air temp. since mine is air cooled. Anyway, I did the same x264.exe encode that I have been doing for all my temperature comparisons and monitored room temp. with a calibrated digital thermometer at several points during each encode. These were averaged and graphed against the averaged reported core temp* values from Speedfan for the entire second pass of a 2-pass x264 encode of the same video file. I was happy to see that for the different room temps used, the increases were pretty linear (certainly within error). Result: You can see by the slopes of the regression line that every delta
  23. What is a better overclock? Good question. Most people believe that a higher FSB and lower multiplier are better since this maximizes the bandwidth on the FSB. Or is a low bus rate and higher multiplier better? Or is there no difference? I looked at three different settings on my Q6600: 9x333 = 3.0 GHz (DRAM was 667 MHz) 8x375 = 3.0 GHz (DRAM was 750 MHz) 7x428 = 3.0 GHz (DRAM was 856 MHz) The DRAM:CPU ratio was 1:1 for each test and the voltage and timings were held constant; voltage was 2.25V and timings were 4-4-4-12-4-20-10-10-10-11. After the same experiments, at each of these settings, I concluded that there is no difference for real world applications. If you use a synthetic benchmark, like Sandra, you will see faster memory reads/writes, etc. with the higher FSB values -- so what. These high FSB settings are great if all you do with your machine is run synthetic benchmarks. But the higher FSB values come at the cost of higher voltages for the board which equate to higher temps. I think that FSB bandwidth is simply not the bottle neck in a modern system... at least when starting at 333. Perhaps you would see a difference if starting slower. In other words, a 333 MHz FSB quad pumped to 1333 MHz is more than sufficient for today
  • Create New...