- Joined
- Mar 7, 2004
- Location
- Phoenix, since 03/2014
Copy/paste of my post from the A64 results collection sticky:
My turn.
model number: ADA3700DAA5BN
core description: San Diego s939 SH-E4
5-letter code: KAB3E
week-code: 0548
4-letter code: RPDW
13-letter code: 1377869L50147
CPU frequency: 2906MHz, 11 x 264MHz, Prime95 stable for 36 hours
CPU voltage: 1.5 V
temperature (system idle/load, CPU idle/load): CPU 28/42 (Don't know system at the moment, but can edit later)
cooling: Thermalright XP-120 with 120mm Panaflo fan for CPU. System has 120mm fan for intake and an identical one for exhaust
motherboard: Asus A8N-SLI Deluxe, 1016 BIOS
memory: OCZ 2 x 1GB DDR400 OCZ4001024ELPE
memory bus frequency: 207MHz
memory timing: 2.5-3-3-5 1T
memory voltage: 2.6 V
HT frequency: 264 x 4
power supply: Fortron Sparkle 550w
Adventures in overclocking land: I decided to overclock my San Diego, after having had it for several months. I did full stability tests at 2410 (11 x 219) and 2600 (10 x 260), both of which passed. I got eager at this point, so I did brief stabilty tests using only Super Pi 32M at 2706 (11 x 246) and 2809 (11 x 255). All of this was on stock volts. 2600 was fully stable at stock volts, but I didn't do the full run of stabilty tests at 2700 and 2800, so I don't know if stock volts would have sufficed. Though it passed Super Pi 32M at both of those speeds, as you will see next, that might not necessarily have been enough for full stability.
Determined still, I went to 2906MHz (11 x 264). I increased the volts 1 step at a time by way of BIOS, in smallest increments possible, and attempted stability tests each time. At 1.4000, my computer locked up while trying to calculate initial value in Super Pi for 1M. At 1.4125 it locked up during the 1st loop of 1M. At 1.425 it locked up again, this time around the 7th or 8th loop of 1M. At 1.4375, it completed 1M Pi, but also every other Pi calculation from 16k through 32M. However, while still at 1.4375, it failed Prime95 after 1 minute. At 1.4500 it failed Prime95 after 4 minutes. At 1.4625 it failed Prime95 after 5 minutes. At 1.4750 it failed Prime95 after 25 minutes. At 1.4825 it failed Prime95 after 5 hours.
So finally, at 1.500v, it ran Prime95 for 36 straight hours before I manually quit (see screenshot). I was doing the smallest voltage steps possible and then running stability tests each time for the purpose of seeing how low of a voltage I could get it stable at. The process was tedious, but very rewarding in the end. I'm running 2.9GHz on 1.5v on air, with idle temps of 28 and Prime95 load temps of 42, which I think is pretty good when all put together.
Here's the screenshot.
I do have an intake fan, which is identical to my 120mm exhaust fan, but we all know speedfan only reports 3 fans, and the 3rd one happens to be the super high winding chipset fan. But yeah, I do have intake, FYI.
I do want to try 3GHz sometime, but I'm happy with my 2.9GHz and am tired of stability testing for hours on end - I wanna play with it now!
My turn.
model number: ADA3700DAA5BN
core description: San Diego s939 SH-E4
5-letter code: KAB3E
week-code: 0548
4-letter code: RPDW
13-letter code: 1377869L50147
CPU frequency: 2906MHz, 11 x 264MHz, Prime95 stable for 36 hours
CPU voltage: 1.5 V
temperature (system idle/load, CPU idle/load): CPU 28/42 (Don't know system at the moment, but can edit later)
cooling: Thermalright XP-120 with 120mm Panaflo fan for CPU. System has 120mm fan for intake and an identical one for exhaust
motherboard: Asus A8N-SLI Deluxe, 1016 BIOS
memory: OCZ 2 x 1GB DDR400 OCZ4001024ELPE
memory bus frequency: 207MHz
memory timing: 2.5-3-3-5 1T
memory voltage: 2.6 V
HT frequency: 264 x 4
power supply: Fortron Sparkle 550w
Adventures in overclocking land: I decided to overclock my San Diego, after having had it for several months. I did full stability tests at 2410 (11 x 219) and 2600 (10 x 260), both of which passed. I got eager at this point, so I did brief stabilty tests using only Super Pi 32M at 2706 (11 x 246) and 2809 (11 x 255). All of this was on stock volts. 2600 was fully stable at stock volts, but I didn't do the full run of stabilty tests at 2700 and 2800, so I don't know if stock volts would have sufficed. Though it passed Super Pi 32M at both of those speeds, as you will see next, that might not necessarily have been enough for full stability.
Determined still, I went to 2906MHz (11 x 264). I increased the volts 1 step at a time by way of BIOS, in smallest increments possible, and attempted stability tests each time. At 1.4000, my computer locked up while trying to calculate initial value in Super Pi for 1M. At 1.4125 it locked up during the 1st loop of 1M. At 1.425 it locked up again, this time around the 7th or 8th loop of 1M. At 1.4375, it completed 1M Pi, but also every other Pi calculation from 16k through 32M. However, while still at 1.4375, it failed Prime95 after 1 minute. At 1.4500 it failed Prime95 after 4 minutes. At 1.4625 it failed Prime95 after 5 minutes. At 1.4750 it failed Prime95 after 25 minutes. At 1.4825 it failed Prime95 after 5 hours.
So finally, at 1.500v, it ran Prime95 for 36 straight hours before I manually quit (see screenshot). I was doing the smallest voltage steps possible and then running stability tests each time for the purpose of seeing how low of a voltage I could get it stable at. The process was tedious, but very rewarding in the end. I'm running 2.9GHz on 1.5v on air, with idle temps of 28 and Prime95 load temps of 42, which I think is pretty good when all put together.
Here's the screenshot.
I do have an intake fan, which is identical to my 120mm exhaust fan, but we all know speedfan only reports 3 fans, and the 3rd one happens to be the super high winding chipset fan. But yeah, I do have intake, FYI.
I do want to try 3GHz sometime, but I'm happy with my 2.9GHz and am tired of stability testing for hours on end - I wanna play with it now!
