Set cpu-NB at 2400mhz, HT at 2400. Take cpu-NB voltage to 1.25v.
Mine takes 1.50 Vcore to get 3.8ghz stable, but yours may be different.
Multi-Threaded Super-Pi Contest
- Thread starter Jet
- Start date
Set cpu-NB at 2400mhz, HT at 2400. Take cpu-NB voltage to 1.25v.
Mine takes 1.50 Vcore to get 3.8ghz stable, but yours may be different.
G25r8cer
Active Member
What freq for nb?
poke349
New Member
I feel like giving this thread a slight bump. 
Here's my 24/7 OC.
All resource-intensive background programs paused/killed + Real Time priority. No other tweaks.
3.5 GHz - Always trust CPUz.
y-cruncher can't detect Turbo Boost.
(For the screenshot, I had to restart my background crunching to force the CPU out of power-saving mode and show 3.5 GHz.)
Here's my 24/7 OC.
All resource-intensive background programs paused/killed + Real Time priority. No other tweaks.
3.5 GHz - Always trust CPUz.
y-cruncher can't detect Turbo Boost.
(For the screenshot, I had to restart my background crunching to force the CPU out of power-saving mode and show 3.5 GHz.)
Jet
VIP Member
I think the warning should be bolded, if it is that intense. However i haven't tried out this program, probably because of the warning.
It's not that big of a deal--just letting you know that making a suicide run probably isn't the best idea
.
poke349
New Member
Only on Core i7 with HT enabled is it more intensive than prime95 and Linpack.
And even then, it's not like one benchmark is gonna kill your system.
It took 7 months under near continuous load for it to burn out my mobo - and that was because I didn't have enough mosfet cooling. (now I do... )
I know of only one other person that has burned out a mobo with this program - and that was because his overclock was far from safe under prime95.
EDIT: As far as I can remember, that person was making a "near" suicide run. Suicide for something like SuperPi... But since y-cruncher is multi-threaded, it pushed his rig way beyond its limits... and after a few benchmarks, it finally blew out his mobo. Fortunately, his processor and everything else survived though.
Anyhow, it was still enough for me to put up the warning on my thread over at XS.
Basically, I don't think he would've dared to run prime with that fatal OC. But it was y-cruncher on Core i7 with HT...
And even then, it's not like one benchmark is gonna kill your system.
It took 7 months under near continuous load for it to burn out my mobo - and that was because I didn't have enough mosfet cooling
. (now I do... )I know of only one other person that has burned out a mobo with this program - and that was because his overclock was far from safe under prime95.
EDIT: As far as I can remember, that person was making a "near" suicide run. Suicide for something like SuperPi... But since y-cruncher is multi-threaded, it pushed his rig way beyond its limits... and after a few benchmarks, it finally blew out his mobo. Fortunately, his processor and everything else survived though.
Anyhow, it was still enough for me to put up the warning on my thread over at XS.
Basically, I don't think he would've dared to run prime with that fatal OC. But it was y-cruncher on Core i7 with HT...
Last edited:
2048Megabytes
Active Member
I will post my marks on the 32M when I get home with an Athlon 7750+ Dual-Core. The marks will put me way above the Intel Atom Processor, but I will have number 17 place.
Oh I dunno, are you overclocked any? Maybe at about 3.2ghz you may beat a stock 8750 X3. I think you will be 14th place.
2048Megabytes
Active Member
I don't want to overclock my Athlon 7750+ Processor because I may sell it within a year and it lessens the resale value.
My Athlon 7750+ Dual-Core at stock 2.7 gigahertz speed. 32M marks:
My Athlon 7750+ Dual-Core at stock 2.7 gigahertz speed. 32M marks:
Dude even now that CPU is barely worth $50, doubt you would sell it for that because the Athlon II 240 is about that much with better performance. In a year, it will probably only be worth it's weight in scrap metal. Now pump the juice and see what it can do!
It should do 3.0ghz on stock voltage, just bump the multiplier to 15 and see if you get a BSOD. When I had that chip, I believe I had around 1.425 Vcore to get 3.2ghz stable, and I hit a wall at 3.3ghz maxing out 1.55 Vcore. But there are some batches I've seen overclock to 3.4ghz on that 1.425 Vcore.
Thats what I said basically, if he overclocks to 3.2 ghz he'd be around low 40's seconds and in 14th place