host clock control not saving with ram upgrade and vista

[Starmonger]

I have been running my OC stable for about a year. e6600 @3.4, but then i just installed vista a few weeks ago, and also got more ram. So now i have 4 gig ram. But i only just noticed yesterday that My OC has been turned off by the bios. So i turned it on and it was back at 3.4 according to cpuz. But today i realised that it keeps being reset. All it is though, is that the Cpu host clock control setting is being turned off each time, though occasionly it will stay on and i can check that it's what it should be in cpuz, however most the time i try it wont save so when it gets into windows it's not oc'd. I have a xp and vista but on 2 seperate hard drives. I don't know much about oc'ing, i just followed someones guide for oc'ing the ds3, and eventually i got something stable. These are my settings: fsbx9 @ 378, system multi 2.00, timings: 5,5,5,12, ddr2 +0.1v, fsb +0.1v, mch +0.1v, cpu 1.43125v. The cpu temps are fine, however i just use the stock northbridge cooler, but have never come into any problems. like i say, it has been stable for a year untill i got the ram/vista. I just tried updating to the latest bios (f130) but still same.

vista x64
Core 2 DUO E6600 3.4GHz
Gigabyte GA-965P-DS3 (F10) rev 1
4GB DDR2 XMS2-6400C5 TwinX
evga 8800GTX (latest drivers) 650, 1580, 1000
Western Digital Caviar 250GB SATA-II
Hitachi Deskstar sata2
Sony DWG120A 16x16 DVD±RW
Creative Sound Blaster X-Fi Xtreme Music
OCZ GameXStream 700w Silent PSU

 

[jitpublisher]

Might be the memory causing this, 4 sticks can be a little tricky to get to work at times. Try upping the memory voltage slightly, or relaxing the timings a little.
See what that does.

 

[shadowthor]

The extra stick of ram, probably made the system unstable at the overclock, thats my guess.

 

[Starmonger]

Im afraid im a little outdated in overclocking, is the memory voltage mch? I remember when i was doing the OC a while back, it was said that upping the mch might make the northbridge hot. Im scared

 

[Starmonger]

the timings were on their default settings of 55512, and also the ram was underclocked by 20mhz due to the system multiplyer. what exactly does loosening the timings do? should i add another notch of vcore?

 

[major53]

starmonger this should help you out I had same mobo before I got the p35 ds3l:http://www.tomshardware.com/forum/239125-29-overclocking-gigabyte
I would still put fan on the norhtbridge.I did and it help the overclocking.hope this helps you out.good luck

 

[Evilonigiri]

the timings were on their default settings of 55512, and also the ram was underclocked by 20mhz due to the system multiplyer. what exactly does loosening the timings do? should i add another notch of vcore?

You, good sir, need to read the OCing Sticky up on the top for C2D. It explains it all.

 

[Starmonger]

I may have fixed it. i reset the bios and reinstalled the f10, and reapplied the same settings. I suddenly realised that i think i had pcie frequency set to auto instead of 100 like i should have. So ive put it back to 100 and so far so good. What would happen if the frequency was set to auto?

also can anyone explain why people set the pcie volatage/frequency to 101, cant remember which of the 2 settings that is.

 

[Starmonger]

nope... still broken

 

[Starmonger]

i tried adding +1 do the ddr2, and tried adding another notch of vcore. But with the extra ddr2 it didnt help, and the vcore made it not post. next ill try loosening the timings. if that fails, what's the next step i should take?

 

[Starmonger]

edit: i have lowered the timings to 66612, and also tried 66618 but still the problem persists.