Asus P5b Deluxe
Core 2 Extreme 6700 (kentsfield) 1,33v
2gb Gskill pc6400 GA c3
Mach II cooling
http://valid.x86-secret.com/cache/127648.png
http://82.173.172.10/Rol-Co/1m4g.png
http://rol-co.nl/images/langer.jpg
Printable View
Asus P5b Deluxe
Core 2 Extreme 6700 (kentsfield) 1,33v
2gb Gskill pc6400 GA c3
Mach II cooling
http://valid.x86-secret.com/cache/127648.png
http://82.173.172.10/Rol-Co/1m4g.png
http://rol-co.nl/images/langer.jpg
I see. It's an engineering sample. Not really indicative of actual retail chips.Quote:
Originally Posted by Drag
But impressive.
But can you hold that with sustained load, or just a quick superpi 1m?
QX6700, Asus P5WDH, 2GB TeamXtreme D9GMH, Watercooled (PA120.3 rad, 1/2", Swiftec 655 pump)
3.5GHz - 48degC idle and 65degC load after 8 hours prime
Currently now priming small 8K fft @ 2.66 GHz with 1.14 vcore under load.
This was a test i did i while ago.
Cooling was my overklokk singlestager which doesnt get very cold but holds load pretty well.
Temp in bios is about +10C lol
Max fsb and clock
http://i107.photobucket.com/albums/m...anuar07002.jpg
100% stable speed
http://i107.photobucket.com/albums/m...eng_QX6700.png
Didnt do any screens of loadtesting @ 4,14GHz, but I thought it wasnt to bad for an singlestager.
Quote:
Originally Posted by loafer87gt
I just can not believe, that f***n nv4disp.dll BSOD
is from ti4200 prehistorical eon!!!!!
try google>nv4disp.dll fix etc....
VIA used to have some fix for that problem, it did work on some nonVIA based mobos.
ti4200, 5900,6600...and even 8800 have same problem?
Check nV+VIA forums for that fix.
Advice, try ti use D3D instead OGL, it is even more faster in MAX7,8,9.
regards!
http://img213.imageshack.us/img213/3...x4startnd3.jpg
P5B DLX
Scythe Infinity + SanAce 260CFM
Room Temp->10C
Bios set -> 1.63v
Windows idle-> 1.53v
load-> 1.45v
Hi, What is the real vcore for this frequency ? and is it stable or not ?Quote:
Originally Posted by nicepun
3350 mhz Quad prime @ 1.4v on a STORM.
3970 mhz on 1m/wprime 32m @ 1.55v on a STORM.
3910 mhz wprime 1024m
I will more testing but so far 1.55vcore for 320x11 (3.5Ghz) stable as hell. I will measure real vcore and let you know.Quote:
Originally Posted by pepinorang
http://www.hwbot.org/signature.img?iid=4300&thumb=false
vcore was 1.625v
I just got done building my rig a few hours ago and am still messing around, but so far, 3.6GHZ, 1.4 vcore. Temps from 30ish to 48ish so far but have not run anything heavy other than 4 instances of P95 for about 30 minutes, and 500% memtests. This is definitely foreign territory for me because that last intel board I had was the IC7-Max3. Also, when I went for 3.7, I don't know if it was ram, fsb, may both, but it would BSOD before Vista completed loading. PWM temps also shoot up pretty fast after 3.6/1.4vcore, so I think I'll hang around this OC with the CPU and concentrate on RAM now.
This bios on this IN9 is a little scary!
By the way, running 4 sticks of:
http://www.newegg.com/Product/Produc...82E16820227159
Think I'll get much more from it?
Propably, if you get rid of this Abit (and any Abit) board and buy something else, like Evga, Asus, Gigabyte, DFI, etc.Quote:
Originally Posted by Slammin
Have a look here ;)
Vapochill LS results.
Just the CPU dependant benchmarks.
Pifast - hwbot comparison
http://slidog.bigblog.com.au/data/2/...0220230901.png
PCMark05 - hwbot comparison
http://slidog.bigblog.com.au/data/2/...0220230930.png
wPrime 32M - hwbot comparison
wPrime 1024M - hwbot comparison
Also, 3DMark06
http://slidog.bigblog.com.au/data/2/...0227212121.png
Quote:
Originally Posted by Chosen.
Hmm,
I gues the latest bios must have taken care of it because I am 100% certain, at least by every measure (Everest, benchmarks, etc.) I can make that all cores are clocking together.
I never even booted into an OS with the shipping bios, but I did save it to floppy. If I ever get bored, I may load it just to play, but I doubt I get that bored anytime soon!
Edit:
I just checked with RMClock and sure enough, two cores with multi 11, and two with multi 10! I stand corrected! I hope abit fixes this!
qx6700 on xbx2 with latest bios..
266x11 = 3ghz, all voltages at default.. stable dual orthos, gaming, 3d benchies, without problem.
266x12 = 3.2ghz, all voltages at default.. unstable orthos for core 3 n 4, but stable gaming, 3d benchies..
will try higher when i got time to play with this new processor :)
Download an older version of CPUz, adjust the multiplier upwards (try 11, 12 or 13 for example) and then run CPUz 1.33-1.35, which allows you to see each of the 4 cores separately and get ready for a surprise :)Quote:
Originally Posted by Slammin
http://img459.imageshack.us/img459/793/ourtkw4.th.jpg
easy'r way :D
run s-pi 1m and set affinity to core 1 only and look at the result
run s-pi 1m second time and set affinity to core 4 and look at the result.
you be shokked :eek:
Quote:
Originally Posted by Rol-Co
er.. that's exactly what my screenshot is showing: one Spi1M @core1 and one @core3, 3 whole seconds difference, 12x300 from BIOS, 2 cores stuck at 10x300.
See My Sig. I'm sure others can do better, But I'm stuck with slow ram, So I'll make do until I can replace It. :D
Vcore for the OC in my sig is 1.60 on Striker
Im sure i can go much higher but I I am waiting for a new phase unit before I go higher..
http://valid.x86-secret.com/show_oc?id=169633
You can also use the -core parameter in the shortcuts for the latest cpu-z to see what individual cores are set at. RMClock is easier though.Quote:
er.. that's exactly what my screenshot is showing: one Spi1M @core1 and one @core3, 3 whole seconds difference, 12x300 from BIOS, 2 cores stuck at 10x300.
A fix to this is use CrystalCPUID. Example I have my multiplier set to 12x275 right now. If I run CrystalCPUID, go through each core and from functions select 'Intel Enhanced Speedstep Control' one of them shows up with a multiplier of 6. If I then change that to 12, all cores are then overclocked evenly.
I tested this with cinebench and my rendertime dropped from 15 seconds down to 12 seconds, so it does work.
RLM
i played with 3dmax this morning and yes, the nv driver problem appeared! :(