*** Official SuperPI Leaderboard ***

[Kaktus69]

Cracking scores guys, I'm almost embarrassed to post my result. Only a few seconds faster than wazza300 managed at 4.8ghz

My chip resolutely refuses to boot into Windows at 5.2, managed a run at 51x100 but it was slower then at 49x104. Motherboard is P8Z77-V.

EK PreciseMount is in the post though doubt that will help in this case. RAM holding back the score aswell as the chip.

 

[Nickolp1974]

Cracking scores guys, I'm almost embarrassed to post my result. Only a few seconds faster than wazza300 managed at 4.8ghz

RAM holding back the score aswell as the chip.

nothing wrong with that score chips fine, like you said "RAM" never even knew there was a 3T, learn something new everyday

 

[Kaktus69]

It's this RAM. I had no intention of overclocking or watercooling the system when I started building it (was originally just going to be a new case for old Q6600/GT7800 system but it morphed into a new PC).

With hindsight I wished I'd gone for 3820 on a RIVE and a larger case

 

[illuz]

Cracking scores guys, I'm almost embarrassed to post my result. Only a few seconds faster than wazza300 managed at 4.8ghz

My chip resolutely refuses to boot into Windows at 5.2, managed a run at 51x100 but it was slower then at 49x104. Motherboard is P8Z77-V.

snip

EK PreciseMount is in the post though doubt that will help in this case. RAM holding back the score aswell as the chip.

What you on about mate, that's a crackin score! I'll add it now

RAM is *definitley* holding you back. Get yourself the Samsung Green

 

[wazza300]

did you try for 5.2ghz illuz?

 

[illuz]

Definitely can't get it mate, just tried disabling HT and knocking ram down to 11-11-11-28-1T 1600MHz to get it stable, just requires silly silly volts!

Stress testing 4.8GHz at v1.4-408 now and it seems to like it.

 

[setter]

New submission with upgraded ram, (8gb of samsung green).

Running at, 2133mhz, 9-10-10-21, 1.57500v. 1T cmnd rate.

 

[wazza300]

is it better than your old score? I forget what it was

timings are good though

EDIT: yeah its a lot faster

 

[setter]

Cheers wazza, old score was 7m 41.3 secs. Havent tested yet for stability, just trying a few settings that illuz and i were discussing on origin yesterday. Ill have to test it properly with ibt or p95.

 

[wazza300]

couldn't you do 1.55v dram?

heres what im getting on my asus z68 @4.5ghz

Spoiler

you should be able to do 1.55v dram and set trfc to 96

 

[setter]

Ill try dropping it to 1.55v, trfc is currently at 96, (default was 128 iirc). Also bumped vccsa to 0.950, (0.925 at stock)

 

[illuz]

Ill have to have a go at dropping my volts but that's a massive improvement mate! I get crashes below v1.6 I think.
I'll add the new score tomorrow, out the house tonight.

 

[setter]

Pretty impressed with the ram tbh. Added bonus now that i dont have to remove the front fan on the k2 if adding any more ram. Bit of a hassle when i went to install/remove the second 8gb of vengeance i had a while back.

 

[wazza300]

its good stuff,you might notice a little in games

 

[horrorxpunk]

*** UPDATED ***

This is my submission for tonight :

Spoiler

 

[setter]

Blue screened just now in game, 0xc4. Who crashed report.

On Tue 09/04/2013 21:39:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040913-24819-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA8007217620, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Seems to point to an nvidia gpu driver issue?

 

[horrorxpunk]

which drivers are you using setter?

 

[setter]

Ver 314.22

 

[illuz]

I found them buggy setter, moved back to 314.21 and my system was running smooth again.

Nice score @ 5.25GHz ill add it tomorrow, tune that RAM to gain top place

 

[horrorxpunk]

I found them buggy setter, moved back to 314.21 and my system was running smooth again.

Nice score @ 5.25GHz ill add it tomorrow, tune that RAM to gain top place

Thanks dude I just got the timings right for 2133 + 2200 but they don't tune aswell with the BCLK than 2000 does.