Guide Thread

Printable View

Show 100 post(s) from this thread on one page

07-10-2008, 09:34 AM
The Nemesis

I never got much over 400FSB stable with my q9450. I just figured the p35 or the DFI had issues with the chip and it would never happen. I put an E8400 in instead and the q9450 has been back in the box ever since.
07-10-2008, 10:02 AM
kitfit1

Quote:

Originally Posted by Praz

^^^^^^ About sums that up.

Well, i think it was about time someone said something about all the "Snake Oil" claims and settings list that populate this forum and the rest of the clocking world. It's idiot stuff like that, that gives people unrealistic expectations of what they may clock to, and then to add insult to injury puts people in a postion where they could probably end up killing a good cpu. I'm shure that Praz is of the same view as me on this, i just wish more people would flag up this sort of rubbish for what it is. If i have offended anyone i'm sorry, i don't get annoyed that often, but this sort of stuff really get's my back up.
07-10-2008, 10:02 AM
mad_skills

Quote:

Originally Posted by kitfit1

With all due respect mad-skills, because i know they arn't your settings. That list of bios settings is just about the most thoughtless list i have seen. Anyone that has been around 45nm's for any length of time knows that just throwing voltage at it does not work. I will lay odds on, that clock was never stable, and the chip is now useless if it was run for any length of time anyway.

I doesn't work even with 65nm let alone 45nm. :)
Sry man, just wanted to help - didn't mean to upset you in any manner.:up:
07-10-2008, 10:13 AM
kitfit1

Quote:

Originally Posted by mad_skills

I doesn't work even with 65nm let alone 45nm. :)
Sry man, just wanted to help - didn't mean to upset you in any manner.:up:

You hav'nt upset me mad_skills :up:

I was just generalising about lists and claims of that sort. I'll go back and hide in the cupboard now :D
07-10-2008, 10:53 AM
Praz

One of the shortcomings of the Internet. Anyone can throw out garbage and it's assumed to be of value until refuted by someone.
07-10-2008, 11:47 AM
mrcape

So today I'm testing this Biostar P45 board, just feeling it out, taking measurements and getting ready for some LN2 I'll be doing with it.

I figured I'd attempt to accomplish the same 24/7 settings as I run on the gold standard DFI UT P35. For now I just swapped boards in my air setup, so it should be a good comparison. The DFI will go back in as my 24/7 for sure though. Even out of the setup and sitting there, it still looks as badass and tempting as it did six months ago.

First thing I notice in Biostar bios (which is pretty good), is that gtl settings are way fewer and not as fine grain - only allow certain combinations.

Another annoyance was that I had to use a slipstreamed xp sp2 disc, whereas the DFI allowed the original xp and SP to be separate.

Edit - so far it's really easy to get 600+ FSB @ low voltages with the Biostar, but getting a good clock with tight timings is a pain. So I would say the DFI is still ahead so far in my comparison.
07-10-2008, 11:52 AM
Praz

Quote:

Originally Posted by mrcape

First thing I notice in Biostar bios (which is pretty good), is that gtl settings are way fewer and not as fine grain - only allow certain combinations.

That may not be a bad thing though. A lot depends on the design of the circuit.
07-10-2008, 11:55 AM
mrcape

Quote:

Originally Posted by Praz

That may not be a bad thing though. A lot depends on the design of the circuit.

Cool. for now I'm using 61 58 for cpu vs 59 59 of DFI. Seems fine so far.
07-10-2008, 01:40 PM
saint-francis

Quote:

Originally Posted by Volkswagen

Anyone Guys.....Just something like a base to work off?

http://csd.dficlub.org/forum/showpos...76&postcount=3
07-10-2008, 03:22 PM
Powersurge

Hey there,

I can't get my UT to shutdown and stay down. Whatever way I turn the machine off (Windows shutdown, 4 sec power button etc.), it stays off for about two seconds and then starts up again. I've never had such a behavior with any machine I've built before and thus am a little confused. Could I have connected something wrong (which I'd have to have done several times then, as I've assembled the system three times in two different cases and it's always been that way), or has someone else had that phenomenon with this board ? Any ideas on what I could have done wrong or overlooked ?
07-12-2008, 04:25 AM
sofarfrome

Just got the board from newegg (open box). When trying to OC I can't raise the vid control above 1.25vcore without the the system failing to boot after restart. It stops at the C1 code. However, if I leave vid control on auto and use vid special add I can increase vcore as high as I want and the system boots fine. I have tried different bios' and still have the same issue. I have also tried all of the known "DFI tricks" but the problem remains.

Perhaps this is why the board came back to newegg in the first place.
07-12-2008, 04:39 AM
mad_skills

When you used vid control, was the vdroop control enabled or disabled? If you use vid control and enable vdroop c. it can sometimes make the mobo unstable and not boot.
07-12-2008, 04:46 AM
C-N

Quote:

Originally Posted by sofarfrome

Just got the board from newegg (open box). When trying to OC I can't raise the vid control above 1.25vcore without the the system failing to boot after restart. It stops at the C1 code. However, if I leave vid control on auto and use vid special add I can increase vcore as high as I want and the system boots fine. I have tried different bios' and still have the same issue. I have also tried all of the known "DFI tricks" but the problem remains.

Perhaps this is why the board came back to newegg in the first place.

My board does that at about 1.3~1.35v with my E8500 but it works fine with my E8190 right up to 1.6 + (I havent tried anymore with this chip)

I have never had this issue with any other CPU Q6600, E6850, E8200, E8400 etc maybe its chip specific :shrug:

CN :)
07-12-2008, 04:49 AM
sofarfrome

vdroop was "enabled" but this allows for the standard intel vdroop. If it is "disabled" then there is zero vdroop.

I did a 6 hour bios clear (battery out, PSU unplugged) and when I restarted into bios I loaded optimized defaults and rebooted. Then I changed only the vid control and whenever I get above 1.25vcore set the system won't boot. At 1.25 it boots fine. One more notch and it is dead.
07-12-2008, 04:52 AM
sofarfrome

Quote:

Originally Posted by C-N

My board does that at about 1.3~1.35v with my E8500 but it works fine with my E8190 right up to 1.6 + (I havent tried anymore with this chip)

I have never had this issue with any other CPU Q6600, E6850, E8200, E8400 etc maybe its chip specific :shrug:

CN :)

I set vid control at several levels above 1.25 (as high as 1.5vcore) and still no boot. Right now I am running P95 at 4.2GHz with 1.312 vcore (115.?? % on vid special add) and all seems to be fine. I guess I can live with that but vid control should work above 1.25v.
07-12-2008, 05:05 AM
mad_skills

Can you try to ask DFi to replace the board?
I personally prefer adding vcore with special add option but this is wrong...:D
07-12-2008, 05:08 AM
C-N

Quote:

Originally Posted by sofarfrome

I set vid control at several levels above 1.25 (as high as 1.5vcore) and still no boot. Right now I am running P95 at 4.2GHz with 1.312 vcore (115.?? % on vid special add) and all seems to be fine. I guess I can live with that but vid control should work above 1.25v.

Yup I know what you mean it should work but at least there is a way round it.

I have run 9+ hours at 4.0, 4.1, 4.2, 4.3 & 4.4GHz with something like + 101 ~ 110 or so % & its run flawlessly so I guess its just the way its going to be.

I have run higher than 110% & indeed run + 125 + % with my Q6600 so I'm sure the special add is sound enough to run higher voltage.

CN
07-12-2008, 05:23 AM
sofarfrome

Quote:

Originally Posted by mad_skills

Can you try to ask DFi to replace the board?
I personally prefer adding vcore with special add option but this is wrong...:D

I may do just that as I don't want to go thru newegg again so soon. I just had to return a new Biostar TpowerI45 board as there was something amiss with the PCIe buss. They were very good to deal with as I got all of my $$$ back without a restocking fee but this is a little different as the board certainly performs well at stock settings and I can even run at 4GHz stable since I only need 1.216vcore to get there. But I would like the vid control to work.

I guess I will play with this for a week or so and see if I am comfortable with this and perhaps I will just live with it as is. If not I will contact DFI.
07-12-2008, 05:40 AM
Praz

I'd send the board back to NewEgg. DFI is only going to warranty an open-box purchase for 90 days.
07-12-2008, 06:20 AM
sofarfrome

Quote:

Originally Posted by Praz

I'd send the board back to NewEgg. DFI is only going to warranty an open-box purchase for 90 days.

I recieved the board from newegg on 7-10-08. So do I have 90 days from that date to deal with DFI? And if I choose to go thru DFI what are my options? A new board or $$$ back? Thanks for your input.

EDIT: I have requested an RMA from newegg. Hopefully they will again waive the $20 restocking fee and the $10 to ship it back to CA.
07-12-2008, 06:42 AM
Praz

Within the 90 day time frame starting at date of purchase DFI will repair your board and send it back to you.
07-13-2008, 01:31 PM
nfm

What kind of times do you guys get at 3.6Ghz in SuperPI 32M runs? I'll start off...

9/13 BIOS
Q6600 9 x 400
DDR1200 5-5-5-15 @ 2.12v
No tweaks, except High Priority run and LargeSystemCache = 1
http://img175.imageshack.us/img175/3...ddr1200hi1.png

I could go much tighter but I prefer Prime95 Blend stable.
07-13-2008, 10:55 PM
Apache0c

I'm new here and I just got this board. I've read about 50% of this thread so far and working on the rest. Looking forward to learning more. If anyone wants to point me to any key sections to read, that would be great.
07-18-2008, 12:03 AM
C-N

Quote:

Originally Posted by sofarfrome

Just got the board from newegg (open box). When trying to OC I can't raise the vid control above 1.25vcore without the the system failing to boot after restart. It stops at the C1 code. However, if I leave vid control on auto and use vid special add I can increase vcore as high as I want and the system boots fine. I have tried different bios' and still have the same issue. I have also tried all of the known "DFI tricks" but the problem remains.

Perhaps this is why the board came back to newegg in the first place.

Forgot to add I flashed back to 0317 BIOS & my board's "CPU VID Control" works fine again so I am convinced its a BIOS issue rather than a board issue.

CN :)
07-18-2008, 07:13 PM
tonytouch

first extreme posting here

first off thanks for the admins for activating my account

so i read all 150 and man AMAIZING i had to get me a setup like this

so for my first system heres my specs

DFI LANPARTY LP LT P35-T2R

Intel Core 2 Quad-Core Q6600 G0 SLACR 2.4 GHZ

OVERCLOCKED TO 3.7 GHZ

BUS SPEED 415.3 MULTIPLIER BY 9 RATED FSB 1661

G.SKILL PC 8500 1066 DDR2 MEMORY RUNNING AT 1250

ARTIC FREEZER 7 PRO CPU COOLER

PALIT 9600 GT SONIC 512 MB VIDEO CARD

TEMPS
CPU 42C IDLE PWM 44C IDLE CHIPSET 45C IDLE

CHECK OUT MY PICS ON MY PAGE

WILL BE OVERCLOCKING AGAIN SOON WHEN I GET MY NEW Thermalright HR-05 IFX CHICPSET COOLER

WILL BE LAPPING CPU, CPU COOLER AND CHIPSET COOLER

GONNA GET SOME INSANE CLOCKS GUYS

:clap::clap::clap::clap::clap::clap::clap:

Show 100 post(s) from this thread on one page

All times are GMT -8. The time now is 03:51 PM.

XtremeSystems

**Official DFI LanParty UT P35-T2R Review/Overclock/Guide Thread**

Official DFI LanParty UT P35-T2R Review/Overclock/Guide Thread