Dolphin OC Benchmark Top 10!

[manbearpig]

"Dolphin.exe has stopped working" - Where am I going wrong?

Code:

Description
Faulting Application Path:    C:\Users\Kieron\Desktop\Dolphin-Benchmark\Dolphin.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    Dolphin.exe
Application Version:    0.0.0.0
Application Timestamp:    52d95c88
Fault Module Name:    nvoglv64.DLL
Fault Module Version:    9.18.13.3750
Fault Module Timestamp:    533347fd
Exception Code:    c0000005
Exception Offset:    0000000000b5f194
OS Version:    6.3.9600.2.0.0.256.48
Locale ID:    2057
Additional Information 1:    fe24
Additional Information 2:    fe24d21bec2bdd38dbc9a83fe715ec76
Additional Information 3:    f8ff
Additional Information 4:    f8ff459b1007bfccc45ad35134da2d07

Extra information about the problem
Bucket ID:    e90fee645ce7fcdda1be1548e51f405a (85919562963)

[DJBarry004]

Seems to be your driver...

[kinkinkijkin]

Are you using the latest version of the driver? If so, that's what happened.

[AnyOldName3]

Yay, now I have some motivation to see how high mine can go, as Delroth said he didn't want more OC results before I got around to doing an OC last time, and everything I do is GPU bound.

[Kodiack]

7 minutes 1 second on my 4.3 GHz Core i7-4770K. I was originally overclocked to 4.4 GHz when I first benchmarked, but didn't care for the warmer temperatures and higher power draw for a performance gain of <2.5%, so I lowered my OC.

I have a pretty darned run-of-the-mill Haswell chip. It gets a moderate (but not remarkable) overclock, runs at decent enough power levels and temps if I don't feed it crazy voltages, and performs extremely well in this particular benchmark when compared to older processors.

[Anti-Ultimate]

That's kinda higher than it should be. My i5 does around ~6:40 on 4.4Ghz.

[Kodiack]

Well, it certainly doesn't help that I couldn't be arsed to stop using my computer while benchmarking. I wasn't playing the games while running the test, but I was browsing the Internet quite heavily and had who knows how many programs running. It wasn't anything particularly intensive, but enough to infrequently peg CPU usage and add just a few seconds to the final result.

Alas, this is a thread about flexing ePeen! 6 minutes 54 seconds is my result with the benchmark left unattended as I went through my morning routine. I'm still at 4.3 GHz. I could easily run the benchmark with an unstable overclock to 4.5-4.6 GHz, but again, don't really care enough. I'm plenty satisfied with my performance.