hey off topic but is anyone having trouble with loggign on to MSN at the moment - it says some weird crap like it cant access my contact list... been like this for a fair while now...

hope it's not cos i've been logging in /out at an average of like once per minute, lol... cos of all the freezing that was taking place while running superpi before i figured out the problems... ahaha ban me from MSN is like taking a chunk of my life away.

with all the stuff you mentioned you'd be able to shave off at least 30-60 seconds....

what sort of temps are we talking about at load.....

what happens past 1.5V groove.....does it throw it out due to heat.....i think that's what me and blackjocker have been experiencing with Freezer64 but could be wrong donno

By groovetek

i dun think the time should be taken seriously at all yet, cos, firstly i haven't optimized any memory timings...

secondly i was doing other things while running it

thirdly i'm on a mega dodged up corrupt windows install from my old nf3 rig, and i haven't yet installed proper drivers, cept for graphic card so that scrollling in IE doesn't lag, hah...

if it means anything though... i got a time of 25m 58 sec... i know in the whole scheme of things it's not bad, but clearly there is plenty of room for optimiastion... ideally i'd take 30 seconds off that, once i've fixed up my rig.

experimenting with max async latency and preamble now - the other timings seem fine.

superpi32m has yet to fail since flashing to 704-2 and using my current settings, and i have lowered my max async latency and preamble down... pretty happy the way it is... i upped the vcore to 1.525 in BIOS, cos somehow this morning, at 1.500 setting caused stressCPU to jump out after bout half an hour... so yeah, had to up it slightly... no biggie...

current a64t shot of rock solid timings (shown is Trfc of 16, testing 12 atm, up to loop 5 in spi32M):