Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

product26

Cancelled
Original poster
May 30, 2005
777
9
Yesterday I successfully installed two BSEL modded e5320 xeon CPUs in to my Mac Pro. Booting in to Windows confirms that they are running at 2.33ghz. The apple system profiler and 'about this mac' only show the default clock speed of the CPU, but having achieved 69.6 gigaflops in powerfractal, I can safely assume that they are in fact running at 2.33(x8) in snow leopard.

I ran a number of stress tests including but not limited to Handbrake encoding, 8 simultaneous instances of Apple's Chess (computer vs computer), CPUTest (all tests, 8 instances).

Before upgrading I used the ZDNet Clock to overclock my stock 2.66 dual core CPUs to just shy of 3.2ghz with no issues at all. Being adventurous and thirsty for processing power I decided to launch ZDNet Clock after the transplant.

Here is where it gets FUN! Because OS X only reports the default clock frequency of the CPU installed, ZDNet Clock shows 1.86 as the starting frequency before any adjustments. Does that mean that any adjustments will be multiplied? Or is it simply increasing as it says, only adding on top of 2.33 rather than 1.86?

Worth noting is that I have 8gb of ram from 2008 mac pros, so they are capable of 800mhz, making them great for FSB overclocking.

I am able to crank up ZDNet a few notches before the mouse starts jumping around the screen when moved. I don't get any error messages in the console but with a jumpy mouse, i backed down on the clock speed. I am leaning towards each adjustment being multiplied by the amount that the system is already overclocked, but who knows.

anybody with BSEL modded e5320s have anything to add?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.