Quote:
Originally Posted by sswilson  No problem with that... Seeing what hoops you need to jump through will probably help somebody in the future who's in the same boat.
You're doing it right though... baby steps to get it up to where you want, and testing all along the way to ensure that you're fault-finding the right snag.
Have you played with the VTT yet? I'm not completely sure what it does, but it's related to the handshake between the cpu and the northbridge. Of all the voltages I ran into when I first started playing with C2Ds it's the one that helped push me over the edge once it seemed I'd hit a wall.
As far as PCI/PCIe freqs go... I'm not sure there is a way to monitor that, but Everest would be a good place to start. I normally just set mine to 101 but that's just an old habit from boards which didn't lock the bus if you left it at auto/100. |
VTT is the FSB Voltage; I've played with it.. I didn't bother at first but when I was almost hitting 1.5vcore I thought maybe I should try and raise my VTT/FSB voltage because I had increased the speed of it so I had an inclination the VTT would help.. went from 1.20 to 1.25, TINY amount but it allowed me to drop my core voltage all the way down to 1.3 and I believe much lower when I can test more, I think I can do 1.2** area at 3.0ghz in a 1:1 with my memory at 667, and I'm HOPING i can tighten my timings to 4-4-4-12 from 5-5-5-12, the lower speed should allow for at least a tweak of a couple of my timings.. I'm hoping lol, won't be but hurt if i don't.