|"You're not gonna be overclocking the RAM so there should be no need to change the timings. Just make sure the RAM voltage is set as per manufacturer's spec...do not use AUTO."|
Gotcha. The reason though I've been using auto is that when I first built the PC I orginally had it set to 0.4+ (2.1 voltage) as per manufacture spec. Problem was I was getting frequent BSODs and when I looked into it further people were saying that it wasn't needed and could possibly fry the ram. I set it to auto from there and at 4-4-4-12 everything seemed to be fine. I'll try a +02 though and see how that works.
"Your default clock settings *should* be 9 x 333MHz with the RAM configured to run at 667MHz. To get the CPU to 3.6GHz, all you need to do is increase the CPU frequency to 400MHz & configure the RAM to run at 800MHz. My guess is your problem relates to your RAM settings, probably the System Memory Multiplier...it should be set to 2.0 & left that way."
Yep that's default. About the SMM, I do have it at two and since the ram is 6400 I should have no problem running it at 400 since that's the default speeds, correct? I've been running it at 400 for two years now before I decided to overclock and just wanted to keep the 1:1 so I guess the ram is fine?
"There are a few other settings that you'll need to set & forget:
- lock the PCIe at 100MHz
- disable CPU EIST (Speedstep)
- disable CPU Halt (CE1)
- disable CIA 2
- disable all Spread Spectrum options (if there are any)"
Already done. :)
Now a few more questions. Should I raise the NB voltage? I've heard that it should be left alone but maybe it'll help get it stable if all else fails. Also, should I be worried about these temps? And what in your opinion is the best program to monitor temps for C2Ds? I'm using speed fan and right now at idle it's saying 35C for core 0 and 37 for core 1. In your opinion is this good for and idle overclock temp (I'm now at my 3.6 overclock 1.43vcore but obviously not running orthos or anything)? Earlier though I was hitting 68C! at 30 mins in orthos but it didn't fail (more like BSOD) until almost two hours in...
Going to try messing with the ram now and running orthos again.
Also, thanks again for the help, Jam.
EDIT: I put the vcore up to 1.43 and set the ram manually to +2 (which since my board doesn't show the actual voltage I guess would be 2.0v). I upped the NB and FSB by +1V each (another thing my motherboard doesn't actually show and only gives +3 options for) then went into orthos - lastest about 2 hours and 30 mins this time before BSOD.
Side note - I added another fan to the side of my heatsink and it's blowing air into it now. I don't know if the ambient temps in my room here have changed (feels about the same) but I'm only hitting 63C max now so I don't think that's a limiting factor.
So I'm wondering where I should go from here? My vcore seems excessively high for a 3.6 overclock so I don't want to raise that more unless I have to. So what I did was raise the ram by another +1 so it's at +3 now (2.1v). I'm going to go into orthos again now and if it fails again I'm thinking maybe up the FBS and NB +1 each?
All thoughts appreciated.
Final Edit: This time at 1.4375vcore, 2.1memv, and +1 to GMHC and FSB I achieved over 6 hours running two instances in orthos. However, shortly after I BSODed....
Now for all the experts out there I could use a final bit of advice. First off, as I've said before I don't want to raise the vcore above 1.43 as it just seems too excessive for this 3.6 clock.
So what should I do? Should I forget about orthos altogether because, well, technically nothing will ever stress my system for over 6 straight hours as much as that. Or should I try raising FSB voltage a notch, or maybe think about lapping and reappling HS and paste?
My temps were about 68C before BSOD but they were that way for an hour before as well so I'm not exactly sure heat was the factor... or maybe it is?
Basically in your expert opinion(s) should I just quit while I'm ahead, or worry about getting more hours in orthos - maybe I should also forget about ram and just stress CPU as well?