Looks like it is set up for 1/4" am I wrong? I hope so
I sent the email hope somebody over there can read English.
Seems the headers are in English but all the rest is in German?
I wonder.... hi or low flow
are the nozzles changeable
etc
Printable View
Looks like it is set up for 1/4" am I wrong? I hope so
I sent the email hope somebody over there can read English.
Seems the headers are in English but all the rest is in German?
I wonder.... hi or low flow
are the nozzles changeable
etc
Ive had a bit of correspondenace with MIPS over the past week or so and indeed they speak great english, are very friendly and sell a great product! Their gear is not cheap, but it's handmade and makes every board it's fitted to quite unique :)
Yep they use 1/4" thread... so all the usual DD and EK barbs will fit to the MIPS blocks no problem I believe!
BARBQ: How would you freeze memory? Just unplug your MB, swap the jumper over and then back again, reboot into BIOS and check your VDIMM voltage and you're good to go!!
The DFI board requires very little CMOS resetting :)
dont forget to ask for availability. if they dont have all coolers in stock it could take some time.
you can use any common barbs. for too long threads they deliver distance rings with any cooler.
http://www.mips-computer.de/images/messingringe.jpg
hmm... i dont even want to feed my ram's with 3,04v for seconds :(Quote:
BARBQ: How would you freeze memory? Just unplug your MB, swap the jumper over and then back again, reboot into BIOS and check your VDIMM voltage and you're good to go!!
The DFI board requires very little CMOS resetting
[QUOTE=hmm... i dont even want to feed my ram's with 3,04v for seconds :([/QUOTE]
As I understand it, this only happened when loading a saved BIOS profile, not at every BIOS clear.
Hi everyone I just got one dfi 680i, priming my e4300 at 3150mh@1.4vcore(bios)1.36vcore(actual):) . found 2 main problem 1) quite a serious vdrop in vdimmn, nb and core even though I using the updated bios. 2)have to clear cmos whenever oc failed to boot:confused: . Any guide here to get away from the desparated on & off and any way to fix the vdrop?
Wow lots of action in here this weekend... some thoughts:
@Borgod/MikeMK - it looks like the Enermax mystery is solved? Use the 4+4 and not the 8 pin ATX connector?
@MikeMK - If you haven't given up on the DFI... I've had most success with the 2CTEST 521 BIOS on my quad (X3220). You may want to try that. I found with the 4C version, that I couldn't change my multi and that it wasn't stable at lower voltages like the 2C version.
BTW, what OC did you get on the DFI board before you switched to the EVGA?
@Borgod... 80-Deg on the NB?!? :eek:
@Grinch... your image of your new sweet spot isn't showing up for me... where are you at now?
@Jobeo, I'm sorry to hear your supcomm story... what's the latest? Have you found anything in particular that is causing the instability with that program?
There is definitely an undervolt between what you set and what you get in BIOS for CPU VID and NB Voltage... just dial in some extra to compensate. There's more info on my blog (via the link in my sig). VDIMM is similar but not as bad... what exactly is the gap you are observing?
The actual droop under load of these values is not bad. CPU droop is much better than most and NB and VDIMM is insignificant.
When you can't boot due to your OC, use the power/reset button trick as described in the manual to quickly clear CMOS. Keep your baseline settings in a "CMOS Reloaded" profile and you can quickly get back to where you were in no time.
Yes 4+4 only with the Galaxy on quadcore. I have been using that since day dot with my DFI since the meltdown of my aforementioned QuadGT.
Yep my NB temps hover around 80degrees. It's not the weight of the 80mm fan pulling it off the core as I have moved the HSF up and down and the temps only get worse - very quickly.
I'm going to watercool it with a mips kit anyway.
Over the weekend I was considering hard how to lower my CPU temps. I came up with an awesome idea of a double loop system with no less than 2x PA120.3 for the CPU and a PA120.3 and PA120.2 for the SLI 880GTX, NB, PWM and SB.
I devised a superb unobtrusive mounting method that would of made it the ultimate water cool system for myself.
But then I did the costs and realised how quickly it added up.
Now I am considering using my existing PA120.2 and PA160 to cool the SLI, NB, PWM * SB and phase change the CPU. kayl lives a 15min drive away from me, it works out cheaper, will be a lot less work and I'll be able to crack 4000Mhz with ease :)
That power/reset button trick is a life saver for sure.
As for the voltages, I think you mean there is a significant undervolt on the CPU/NB... and while there is a bit of droop (as expected on the CPU) there is no droop on the NB right?
Undervolt = gap between what is set in BIOS and what you get
droop = difference between idle and load voltage
i haven't messed with it today but i'm gonna try some stuff right now. someone recommended 3dmark a few pages ago and i have several versions of that i will try.
in supcom the instability seems related to heavy load. somehow the game is pushing the components harder than prime testing... i blame it all on the 400 FSB OC settings i'm using. something is off and i'm just not sure what it is. with those settings i'm barely overclocking the CPU itself by using a lower multi.
from what i've seen the VTT/GTL's are seriously important for 400 FSB. at stock FSB i could raise the multi to 11-12-13 without tweaking the VTT or GTL's...
i'll see what i can do and hopefully report back something good =/
well i got somewhere... installed 3dmark03 and loaded my sketchy settings... the reboot crash occured during the benchmark, which actually made me happy cause now i had a better way of testing it.
i tweaked the NB volts higher that didn't help. even tried running the test non-SLI and it seemed to reboot even faster. all of the reboots were occuring at different times during the test there seemed to be no pattern.
so i started fiddling with the GTL's ... i had them set at the "sweet spot" of 1.44v and 170 95 85... tried them a bit higher and the test seemed to run a bit longer before rebooting. finally ended up with GTL's of 180 100 90 and 3dmark03 passed for the first time ! ! i ran the test 3 more times and it passed each time. then ran the 3dmark05 and 3dmark06 tests and both passed. loaded an old supcom save with a lot of units and that seemed to go OK too...
SO.... to make a long story short... i mean, i knew the GTL's were important cause i've mentioned them in almost every post these past couple days.. but MAN they are _really_ important. unless i'm mistaken we're talking about tweaking millivolt settings yet it seems to have a huge impact on stability.
so i think i've found a new sweet spot at 1.44 and 180 100 90. which doesn't really add up cause the Nvidia GTL reference table says the VTT should be 1.55 at those GTL's but whatever works i'll take it... i'll probably need to test further with another prime blending session but for now things are looking good.
Even with a dual core the GTL's make all the difference not for the CPU's sake but for the NB.
I am still working on getting 3.7GHz running 8 hours + Orthos stable & have increased my reboot/crash time from 3 to 6 hours tweaking GTL's.
I think GTL's are going to take forever to workout & understand as even the smallest variant in CPU/NB puts you back to the start again with the GTL's.
When they first start up they're a bit noisy - sounds a little like a fridge. However when they're running the noisiest part is usually the fans that cools the condensor, and the bigger compressors may be a little noisy aswell.
I'll get mine custom made so it won't be too noisy of course.