Moose83

Damn crazy men:D

Hey Mr. leghooft, are u there for the bunnys only?

I thought it means der Bauer the farmer

:banana:

Not bad keep pushing:)

Lol:D

DJ ftw:D

Dennis de Server Men:D

For Phenom 2 990 Boards are the way to go;)

Forget Athlon:D Is your 555 pretested?

Time to crap out my 555 BE too:D

Nice me like:)

Mine does 5.3 on Cascade 1.7V and 6.5 Wprime 1.81V Ln2:)

How high can u go Ln2?

Nice:) So next Ranking to fight for Points:D

So not that much in 3D:)

Farjam for King of Iran:D

U should gain an Archievment for this of course:D

Trololol:D

F...ck yeah:D Awesome Farjam:) So you killed not all your Hardware:p

0 Marks:D

Like it:)

Damn Thomas, you work hard atm:)

Wich subs? I havent issues in my Orb, and scores are checked by Pro;) Time measuring inaccurate This message indicates funny business with the system clock during benchmark run. In most cases, this means that, no, you cannot cheat in 3DMark by adjusting Windows timers during benchmark run or otherwise tampering with the measurements done by the benchmark. If this message persists and you have not done anything out of the ordinary, it may indicate a hardware issue with the real time clock of your system or a presence of a background program that somehow twists the time-space continuum of your operating system in such a way that this anti-cheat detection is tripped.

But Orb looking bad...Time messuare...we all now what this mean;)