PDA

View Full Version : Somethings wrong but I just can't figure it out


J☼E
02-11-05, 03:04 PM
I can't seem to go any higher than about 286-287 with my 3.4E D0, xp-90/tornado, P4c800-E Deluxe(vdroop). I don't know what the problem is, I try to change my RAM timmings all around but I just can't get any that will work with 290fsb. My boards timmings all maxed are 3 4 4 8, I have read in many guides that the last number(TRAS) should be 11 not 8. But I don't know if thats the problem, I am 100% stable at 280fsb with 3-4-4-8(I have listed my current bios settings in the pictures below) I have tried changing the divider to the next lowest setting 5/4, but I can't find any timmings that work with 5/4.
I have tried to boot to 285 fsb with these timmings:

2.5-4-4-7 = I get to the desktop but after about 5-10 seconds a little crack comes from the speakers and the screen freezes up (system completely locked up)

2.5-3-3-8 = freezes at windows "welcome" screen

3-4-4-8 = was able to boot and browse the internet for about 1.5 hours and play 10 minutes of garry's mod (hl2) I am not sure of the stability of this setting under constant load. By the way my load temps are around 47-53 (can't remember). So my question is, is there some bios settings that I have wrong or should change? Or something that I am missing to make this chip go higher. I am considering water cooling but my fear is that I get it all set up and I am not able to overclock any higher.

I have also tried a neopower 480 watt psu in my system and it yielded no more overclocking ability than my current one. also sorry for the big pics

here are my current bios settings and some cpu-z/probe shots:
http://goon.no-ip.biz/pictures/pooter/9.jpg
http://goon.no-ip.biz/pictures/pooter/2.jpg
http://goon.no-ip.biz/pictures/pooter/3.jpg
http://goon.no-ip.biz/pictures/pooter/4.jpg
http://goon.no-ip.biz/pictures/pooter/5.jpg
http://goon.no-ip.biz/pictures/pooter/6.jpg
http://goon.no-ip.biz/pictures/pooter/7.jpg
http://goon.no-ip.biz/pictures/pooter/8.jpg
http://goon.no-ip.biz/pictures/pooter/1.jpg

Sentential
02-11-05, 03:14 PM
Could be maxing out the chipset / CPU vcore. Have you tried raising either?

J☼E
02-11-05, 03:19 PM
yes but there is no difference, If I raise it to 1.5 since my board is vdrooped it would be like 1.6 in windows, what do you mean by chipset vcore?

Stratcat
02-11-05, 03:59 PM
yes but there is no difference, If I raise it to 1.5 since my board is vdrooped it would be like 1.6 in windows, what do you mean by chipset vcore?
~ Sorry Sentential - Not trying to step in front of you ~

Until he pops back online, & explaines, he's probably referring to how raising the Vagp on your particuliar Asus mobo also raises the voltage powering the Northbridge (MCH). Kinda' like raising the cpu's Vcore, only it's raising voltage to the NB, instead of the proc - Sometimes it helps memory performance/stability, especially at higher FSB's.

Strat

J☼E
02-11-05, 04:59 PM
~ Sorry Sentential - Not trying to step in front of you ~

Until he pops back online, & explaines, he's probably referring to how raising the Vagp on your particuliar Asus mobo also raises the voltage powering the Northbridge (MCH). Kinda' like raising the cpu's Vcore, only it's raising voltage to the NB, instead of the proc - Sometimes it helps memory performance/stability, especially at higher FSB's.

Strat

so raising my vcore raises nb voltage? so I should try and raise the vcore ?