Sure - but, unfortunately there is no guarantee it will work for you as, you're probably well aware, even when using like-for-like compnents their ability to clock will usually vary slightly, sometimes majorly - but it will give you something to work on.
If by some happy circumstance is does works straight off – prime95 it for a few hrs and if it passes then incrementally lower voltages until it buckles and then go back to the last known stable setting. Oddly, I haven’t done this yet for my 3.5GHz because I just bumped the vCore down to 1.3v from my 3.8Ghz setting and I was fortunate enough for it to work – I plan on finding it’s lowest, stress stable limit when I’m back from holiday.
Aaanyway, here are my (present) settings:
- Multiplier - x12
- FSB - 292 (i rounded it up for convenience)
- PCI-e - 101
- Memory Divider - 3.33C (973MHz)
- vCore - 1.30v (I reckon I could get a lower stable voltage but I’ve yet to experiment. I’ve dropped from 3.8GHz to 3.5GHz since the summer kicked in as the 3.8Ghz became, at first, a bit unstable but then became too noisy to justify.)
- DRAM - 2.2v (This I know I can run lower but it’s set at 2.2v because my memory is so close to 1066MHz – and again I haven’t had time to stress test the 3.5GHz clock properly.)
- Timings set manually - 5 5 5 15 (You should try 5 5 5 18 first – use 15 once the system is stable.)
The system idles at a rather warm 49º but this is made irrelevant by the load temps which are 67º - i should really get a better cooler but as the load temps are ok i'm going to just ride out the summer at 3.5GHz.
Let me know how you get on.
i will try that
