Q9450 & DFI X48 UT (help!)

[korbus]

DFI X48 UT DDR2

Q9450 @2.66mhz
E-VGA GeForce 9800 GX2 KO
4gigs (2x2) OCZ Reaper HPC 5-5-5-18
Thermaltake 850W Power Supply

Stock voltages:

VCore: 1.125
NB: 1.265
SB: 1.510
VTT: 1.10
DRAM: 2.10

 

[Fadey]

Try increasing your voltages , my cpu uses 1.239 at 3.2ghz i also add +0.1 to my northbridge and +0.05 to my fsb. I use a gigabyte board not sure what the defaults are.

 

[graysky]

@korbus - we need more details dude... hardware and all your relevant bios settings such as vcores, strap, mem settings, mem timings, etc.

 

[aigomorla]

sorry but you picked the wrong board if you dont know how to overclock. :\

I think you missed it where i and all other DFI owners kept warning people not to buy this board unless your an experienced ocer. Even then the bios still scares the experienced OCer.

For now the only recomendation i can give is for you to do some research on the board.

But im 100000000000000000000% sure its your GTL settings, and your VTT settings. <this is only done by research, someone cant tell you what to plug in.

The board is the best overclocking board only if you know what your doing. If you dont, its gonna give you TONs of nightmare and headache.

This problem will be hard for someone to recomend you. Expecially since a lot of people dont own this board. I have this board, and i am fully aware of how difficult it can be.

Do some research on GTL and VTT. If you still dont get it, you need to swap boards to an asus.


I ask the people who help him from now on be those that fully know GTL values, and VTT properties AND OWN a DFI LT/UT P35 or X38 or X48. If you dont have this board, you can and might lead the op into damaging some seriously hardware. [which is why im not recomending him in doing anything. Sorry its more in regards to saftey since this is a 45nm chip as well.]

GTL is not something you should mess with unless you know what your doing.

 

[graysky]

@aigomorla - it's not that tough to o/c on these boards... I actually love the LT P35-T2R I have. I wouldn't mess with GTL values (level them disabled) unless you know what you're doing and actually need to squeeze that last 5 % out of your hardware.

@OP - Maybe a good place to start is my c2d/c2q overclocking guide. If the first part bores you, read the minimizing vcores section that can probably help you out here.

 

[aigomorla]

Originally posted by: graysky
@aigomorla - it's not that tough to o/c on these boards... I actually love the LT P35-T2R I have. I wouldn't mess with GTL values (level them disabled) unless you know what you're doing and actually need to squeeze that last 5 % out of your hardware.

@OP - Maybe a good place to start is my c2d/c2q overclocking guide. If the first part bores you, read the minimizing vcores section that can probably help you out here.

thats the problem tho.

On the X38 and X48 there much more GTL sensitive then the P35's.

I have a P35, and a X38. I didnt buy an X48 cuz i heard ruby complain about how picky the GTL was.

This is why im 10000000000000000% sure its GTL problems on his end. :T

 

[bryanW1995]

graysky, that mobo is designed EXACTLY for people who write 10 page overclocking guides for anandtech. it wasn't desgned for n00bs like the OP who clearly have little to no overclocking experience. I almost bought one of the p35 mobos the other day when they were $99 shipped open box at newegg just for fun, but I know what I'm getting into with one of those mobos. I already have quite a bit of oc'ing experience on core2-based cpus, and even then that was just the p35 version so I was fairly confident that I could figure out any quirks fairly easily.

 

[aigomorla]

OP dont get me wrong.

I seriously like helping people, but your seriously stuck in a dangerous place.

Its like teaching someone how to drive in a ferrari stick shift when you never drove b4.

Under most conditions we could tell you bump this voltage and bump that voltage, but on the DFI, cuz of the GTL values, a slight voltage bump could lead to a very bad situation expecially if your GTL is set at 160.

This is why i am telling you to only take advice from people who have this board and know what GTL values do.

Also VTT values, these are very dangerous to play with as well on 45nm. In short, i dont feel comfortable giving you recomendations on how to overclock because i know how "sensitive" the hardware is that your working with.

You need to research yourself and you need to teach yourself the board. Its gonna be tough and long, but the outcome when you understand the board is so much worth it.

 

[korbus]

Okay (for the record) I knew what I was getting into when I got the DFI board. I'm not a damn moron. I just have NEVER seen OCCT report such strange CPU % numbers before. I was wondering if anyone else here has?

That's all I was asking.

 

[Big Lar]

OCCT may not recognise the board as it is so new, or because the bios is so new. I'm sure another version will come out soon, until then maybe just try Orthos Blend and Small ffts.

Clunk has alot of info as to GTL's on his site. There is also an article on the X48 on Anand written by Raja that has a GTL table that appears to work.

I don't have a quad, or I might be able to give more insight, but I am sure you will do well

Larry

 

[aigomorla]

Originally posted by: korbus
Okay (for the record) I knew what I was getting into when I got the DFI board. I'm not a damn moron. I just have NEVER seen OCCT report such strange CPU % numbers before. I was wondering if anyone else here has?

That's all I was asking.

As Lar states, OCCT will have some problems. However stress test shouldnt fail. It doesnt fail on my QX and my X38.


Right now your oc problems lies in the GTL tables. As i said im 100000000000000% sure. Fix your GTL values, and your overclock should pass.

 

[Rubycon]

I have that board and never have seen those strange anomalies with OCCT before. Something else must be going on there. Try resetting the CMOS (hold down power and reset for five seconds) and try again starting stock and work your way up. The more settings you have the more things can get crazy if you start changing a whole bunch of stuff at once. You need to walk before you run.

 

[korbus]

Edited my first post to give a better idea of my hardware and what voltages I know the system runs stable at (albeit stock).

I'm beginning to wonder if the problems may be stemming from my power supply. If so, there's not much I can do about it except run at stock settings and be happy.

Aigomorla - thanks for pointing out the GTL settings. I err on the side of caution there, though, because I don't know nearly enough about those to start tinkering. So, if ANYONE out there thinks they see something that could help me out, here, let me know. As it stands right now, nothing beyond stock will remain stable past 7 minutes on OCCT.

Tried a CMOS reset - same issues. For now I'm just keeping it at stock until I can get some input. This is driving me insane.... I'm a casual overclocker, but I have NEVER run into problems like this before. Hell, all I wanted was to hit 3.2 and be done with it.

 

[Rubycon]

Is EIST on or off?

 

[aigomorla]

ruby whatcha think?

he wants 3.2 which would require piss low voltage. VTT 1.3V

So im guessing 1.2875Bios Voltage with GTL values 85 110 90?

OR 110 115 85 ?

Wait for ruby's reply b4 you do this.

 

[korbus]

I've tried it with EIST on and off. The one thing I haven't disabled (yet) is Thermal Management Control.

If I get a chance to sit down with it today I'll post some shots of what I'm seeing in OCCT (with the wierd numbers).

 

[Rubycon]

Originally posted by: aigomorla
ruby whatcha think?

he wants 3.2 which would require piss low voltage. VTT 1.3V

So im guessing 1.2875Bios Voltage with GTL values 85 110 90?

OR 110 115 85 ?

Wait for ruby's reply b4 you do this.

Wow I would not think that GTL needs to be touched at 3.2. :Q 1.30 - auto (GTL) and overclocking damper (vdroop comp) turned OFF should make it stable.

 

[aigomorla]

Originally posted by: Rubycon

Originally posted by: aigomorla
ruby whatcha think?

he wants 3.2 which would require piss low voltage. VTT 1.3V

So im guessing 1.2875Bios Voltage with GTL values 85 110 90?

OR 110 115 85 ?

Wait for ruby's reply b4 you do this.

Wow I would not think that GTL needs to be touched at 3.2. :Q 1.30 - auto (GTL) and overclocking damper (vdroop comp) turned OFF should make it stable.

he's reporting problems tho when he starts 3.2

Which means his board is super sensitive. I highly doubt its his chip that cant do 3.2ghz.

Thats like saying a ferrari that cant break 100mph.

 

[khurios2000]

http://www.vimeo.com/937940/l:embed_937940

 

[aigomorla]

Originally posted by: khurios2000
http://www.vimeo.com/937940/l:embed_937940

1.55V on bio Northbridge.. umm..

ONLY and i say ONLY cuz the Northbridge on the DFI LT is the Dominator. :T

 

[Rubycon]

Originally posted by: khurios2000
http://www.vimeo.com/937940/l:embed_937940

Nice guide.

Originally posted by: aigomorla

1.55V on bio Northbridge.. umm..

ONLY and i say ONLY cuz the Northbridge on the DFI LT is the Dominator. :T

Nothing wrong with that. BTW I have a UT on the way and it's a different animal I am told. We shall see in about a week or so.

 

[lopri]

OP: You shouldn't need to touch anything in the BIOS for Q9450 @8x400 and 2x2GB sticks.

 

[korbus]

Yeah, in hindsight, I wish I would have bought a Q6700 instead of the Q9450. The system is 100% stable at stock settings - I just can't get it to overclock.

So, I've kind of given up for the time being. Trying to hit up some more experienced users to help out. =)

 

[Rubycon]

Originally posted by: lopri
OP: You shouldn't need to touch anything in the BIOS for Q9450 @8x400 and 2x2GB sticks.

I agree. Either that or that chip has thin margins.

I have a QX9650 that starts getting errors at anything above 3.2GHz at stock voltage. Yet another from the same lot does 4GHz at slightly below stock voltage. Talk about a cherry and a lemon. Bleh!

 

[Scotteq]

OP - How fast/hard are you running your RAM??? I ask becuase when I see people saying their stuff won't overclock at all, very often it's a case of unintentionally overclocking Memory.


FSB speeds also directly influence RAM speeds on Intel boards. For example: Starting with a 400 FSB and DDR2 800 at 1:1 is fine on stock settings. But when you bump the front side to bring your processor speeds up, your memory goes along for the ride: So at a 420 FSB, your RAM is now running at 840 Mhz. So UNDERclock your memory while playing with your CPU. You can revisit later.

Try and see does that help.