| |||||||
| Results Share your benchmark results here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | |
| Today I decided to wind up my 4600+ and see if I could earn back a few HWBoints. Now this is without "chained" tweaks, leaving the voltage and all timings as before, just boosting the FSB. First I tried wPrime. That would run, even the long 1024M version, at speeds as high as FSB=215 (which delivered 2596MHz and a POST screen of "2.61GHz"). At FSB=218 and 220, it also completed, but the system would bomb when I tried to restart everything so I could submit results. (for best scores, I strip down everything, including the 802.11g card driver, to bench) At FSB=225 and 230 with reduced timings (DDR333 memory settings, LDT 4x instead of 5x), it failed to boot. 230 stopping after POST, 225 during the Windows load. Then I tried 3DMark03. At 215, it ran two tests then bombed to desktop. SuperPi 1M would either fail the first test, or if I tried a second test, at 210 and higher. I didn't bother trying anything between 200 and 210. So all I got out of it were some new wPrime scores, which don't even actually move the needle that I can see except to allow me to say I've pushed my CPU over 2.5GHz. Has anyone else noticed similar phenomena-- that some benchmarks are far more forgiving of overclocking than others? | ||
| | | |
| Sponsored Links |
| | #5 (permalink) | |
| Depends on the particular hardware involved. For instance, when I had the Firestix for a while (and now the same thing is happening with a current review item), the stock voltage that my mobo put the RAM at was 1.8 or 1.9, but to get DDR2 1000 (which is it's rated speed) a slight bump in voltage is needed. | ||
| | | |
| | #6 (permalink) | |
| Well, I looked, and it doesn't matter because my mainboard tops out in terms of CPU voltage at 1.40 (which is stock for the X2 as far as I can tell), and the RAM is good to 220 or so-- I recall being able to get that high on my old 3200+ | ||
| | | |
| | #10 (permalink) | ||||||||||||||||||||||||
800MHz will help overclocks. What board do you have? | |||||||||||||||||||||||||
| | | ||||||||||||||||||||||||
| | #11 (permalink) | |
| ASRock 939SLI32-eSATA2. ULI M1695 chipset (yes, it theoretically will do dual-X16 SLI, if you use very specific hacked driver versions, but what I liked about it was that it was fanless unlike almost every nF4 board) Edit: Knocking the HTT to 4x and the memory timings down to DDR333 settings seems to allow SuperPi 1M at FSB=220. Of course, 177MHz memory clock is not hugely great for overall performance. ![]() Last edited by Hak Foo; 01-April-07 at 02:51 PM. | ||
| | | |
| | #12 (permalink) | ||||||||||||||||||||||||
Damn it. It's still not stable enough for long runs. I thought it was heat (dialed the rear fan to full blast, no benefit) but I fear it's voltage which I cannot fix. One of the more spectacular failures: wPrime 1024M. Core 1 stops trickling results at about 64%. Core 2 keeps ticking to 65%-- like 3 updates of the screen unmatched. Enough time to go o.O. Eventually the system finally gives out with a resounding front-panel-speaker beep. | |||||||||||||||||||||||||
| | | ||||||||||||||||||||||||
![]() |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Slashdot // "Market Share" "Installed Base" and Consumer Electronics | Gizmo | Slashdot RSS | 0 | 18-March-07 12:30 PM |
| Ars Technica // Conservapedia hopes to "fix" Wikipedia's "liberal bias" | Gizmo | Ars Technica RSS | 0 | 05-March-07 12:11 AM |
| Ars Technica // Blake Ross has a "tip" for Google: stop using "tips" | Gizmo | Ars Technica RSS | 0 | 29-December-06 05:30 PM |
| Ars Technica // Cable and phone companies call Net neutrality "silly," "mumbo jumbo" | Gizmo | Ars Technica RSS | 0 | 07-September-06 10:01 PM |
| Ars Technica // Women's "don't date him" gossip site sued by "victim" | Gizmo | Ars Technica RSS | 0 | 30-June-06 02:01 PM |