M860tu project

I presume that by this you are referring to also OC-ing the PCI-e bus, rather than the GPU itself. Can you please clarify?

Yes, I did notice that point being made elsewhere, thanks for underlining it again, it's good advice.

My M860TU should be arriving next week, with a P9600 - I couldn't get a P9500 with E0 stepping, but P9600 will do even if I have to RMClock the multiplier down by a notch.

Will report back with results in 10 days or so.

 

Sorry, yes I meant the pci express bus. Good luck. The p series oc really well.

 

Hmm... That is potentially concerning. 125MHz on PCIe is A LOT.

 

Finally got my M860TU after a lot of problem in getting it as I specced it. But got it all eventually. A few things that I deem worth sharing:

1) Crucial 1333MHz memory doesn't require re-flashing. I just bumped setFSB up to 1333MHz, and it's rock-solid. The SPD says it should be running CAS-9 at 1333, but mine isn't having any problem running at 1333 at CAS-7 timings as per 1066MHz settings. I love Crucial memory.

2) NHC doesn't seem to have 64-bit drivers available, which I find deeply disappointing (I'm running Win7 64-bit). So I'm having to use RMClock, which I find isn't as nice.

3) My CPU can't seem to handle any OC-ing. It's P9600 2.66GHz. RMClock offers 1.3625V for IDA, but I cannot adjust he multiplier down for that. For everything else, I cannot up the voltage past 1.25V. So I'm stuck at 2.66GHz, even with 25% FSB OC. :-( Is here a way to trick things into using the IDA voltage at a lower multiplier with RMClock?

 

You could try a volt mod:
http://forum.notebookreview.com/har...90696-bsel-mod-socket-p-explained-photos.html

 

Hmm... I decided to flash my SPD so the timings at 1333 are where they should be when I bump the FSB to facilitate reliable stability testing. I got a Thaiphoon Burner licence, and everything. But whenever I flash it, it doesn't seem to stick. Operation completes without any errors, I reboot, and the timings haven't changed. I have checked the PSW, and Thaiphoon Burner shows it as write-protectable, but the box isn't grayed out, which implies it's not already write-protected, at least by PSW. Any ideas? These are Crucial DDR3-1333 modules.

 

Are u sure ur p9600 need that much voltage ? My p8600 runs at 2.99 with 1.175v

 

I'm not, but I can't be sure until I can flash the RAM timings, and that's proving problematic.

 

OK, it turns out I was wrong. I have it all stable OC-ed without the need to flash memory SPD or anything else. I was making a mistake in my RMClock configuration. Here are the details of my setup:

CPU: P9600 (2.66GHz) @ 3.00GHz (266MHz -> 333MHz FSB, multplier limited to x9)
OC/Voltages:
333x6: 0.9250V (min)
333x7: 0.9500V
333x8: 1.0125V
333x9: 1.1000V

RAM: Crucial 1333, stable at 1066 timings (CAS7)

No observed problems at all from PCI-e 25% OC, runs Crysis benchmark and 3DMark06 happily all day without any errors.

All of the above OCCT tested for 24 hours.



Now if only there was a utility that combines the functionality of RMClock and SetFSB...