Welcome Guest ( Log In | Register )

41 Pages « < 27 28 29 30 31 > » Bottom

Outline · [ Standard ] · Linear+

 DFI Infinity 965-S Disscussion, Talk About How to Tweak

views
     
remysix
post Jun 29 2007, 06:06 AM

Hardcore Leecher!!!
******
Senior Member
1,311 posts

Joined: Jan 2003
From: Puchong/Deep Beach


QUOTE(Joseph Hahn @ Jun 29 2007, 04:46 AM)
NB Strap at default or 266MHz makes no difference. sad.gif

If i don't enable the AHCI it will just stuck there saying that the AHCI bios is not installed. doh.gif  How can you just bypass it ? ohmy.gif I tried increasing like all the voltages available. rclxub.gif
*
which bios version r u using...
r u running IDE, AHCI or RAID on ur hdd?
i'm running RAID0...no problem...but yes, the Interl StorageMatrix (AHCI/RAID) is kinda sux...really slow on detecting hdd especially if u have "sor-of-problematic" hdd...what if u plug out all ur hdd (pull-out the power cable), will it give the same prob...mmm...now i remember that whatever it is, it always said that AHCI bios not installed...same as mine but still it proceed with the detection...
when this actually happen...stuck at the AHCI/RAID bios screen...do u able to pass it on stock speed/setting?
Joseph Hahn
post Jun 29 2007, 12:02 PM

kpop k
*******
Senior Member
6,410 posts

Joined: Jan 2003
From: MLK
I just updated to the modded beta bios. I'll try again later.

I'm just using IDE mode. At stock setting and current setting in my sig, the AHCI BIOS page don't appear at all. It only appears at higher FSB. rclxub.gif I wonder why. sweat.gif
remysix
post Jun 29 2007, 12:11 PM

Hardcore Leecher!!!
******
Senior Member
1,311 posts

Joined: Jan 2003
From: Puchong/Deep Beach


hmmm...need the DFI Dark sifus here advise la like that one...i'm switching P35 based plak thumbup.gif
nuodi
post Jun 29 2007, 07:19 PM

Getting Started
**
Junior Member
216 posts

Joined: Aug 2005
From: KL


QUOTE(remysix @ Jun 29 2007, 06:06 AM)
which bios version r u using...
r u running IDE, AHCI or RAID on ur hdd?
i'm running RAID0...no problem...but yes, the Interl StorageMatrix (AHCI/RAID) is kinda sux...really slow on detecting hdd especially if u have "sor-of-problematic" hdd...what if u plug out all ur hdd (pull-out the power cable), will it give the same prob...mmm...now i remember that whatever it is, it always said that AHCI bios not installed...same as mine but still it proceed with the detection...
when this actually happen...stuck at the AHCI/RAID bios screen...do u able to pass it on stock speed/setting?
*
me also using raid0 and initially got problems.

its strange cos if i set to raid, it will not boot up.
Need to set AHCI 1st, reboot and then set to raid. This was done on the 1st day, after that no more problem till today.



Joseph Hahn
post Jun 29 2007, 07:39 PM

kpop k
*******
Senior Member
6,410 posts

Joined: Jan 2003
From: MLK

sHawTY
post Jun 29 2007, 10:54 PM

Frequent Reporter
********
All Stars
14,908 posts

Joined: Jul 2005

QUOTE(Joseph Hahn @ Jun 29 2007, 07:39 PM)
Haih really sad, hoping to use 500FSB with this board and cpu but this problem is bugging me. doh.gif Nevermind, i'll try looking all over the net for solution(s). cry.gif
*
Dude, tried 499? hmm.gif
Joseph Hahn
post Jun 30 2007, 01:07 AM

kpop k
*******
Senior Member
6,410 posts

Joined: Jan 2003
From: MLK
Er nope lol.

Ok here's a report. What i did just now is clear CMOS and load optimized default (as suggested by almostthere... thanks man). Then i tried your method of pumping up the NB voltage. Guess how much i need to enable me to type this post. 1.45V in BIOS. doh.gif At 1.40V load windows a bit then BSOD. Now running at 400x9 at 1.52V but Orthos fail straightaway i have no idea why but Windows Experience Index benchmark passed. Not enough VCore or what. shakehead.gif

What's been stopping me before is the CPU Thermal Management feature. When i disable it, i won't be able to boot into windows at all.


Added on June 30, 2007, 2:29 amOk 400x9 seems too much i keep getting BSOD when Orthosing even when VCore is at 1.55V mad.gif (isn't this batch supposed to be good... adoi... doh.gif... or is it the mobo...), now running at 400x8 at 1.42V. Orthos for a while seems ok. NB is at 1.5V. shocking.gif I will try to look for a sweet voltage spot at this CPU clock tomorrow.

About the BIOS, i seem to be able to change every other settings and made Windows boot EXCEPT the DRAM setting. If i touch any setting in that section i won't be able to boot at all. So i HAVE TO leave it at Auto. doh.gif It sets my memory at 5-4-4-12. shakehead.gif What's the use of the BIOS setting if i can't tweak it haih... doh.gif

Bah enough for tonight i'm tired. rclxub.gif

For good measures... doh.gif doh.gif doh.gif doh.gif doh.gif doh.gif doh.gif doh.gif doh.gif doh.gif

This post has been edited by Joseph Hahn: Jun 30 2007, 02:34 AM
sHawTY
post Jun 30 2007, 07:41 AM

Frequent Reporter
********
All Stars
14,908 posts

Joined: Jul 2005

QUOTE(Joseph Hahn @ Jun 30 2007, 01:07 AM)
now running at 400x8 at 1.42V. Orthos for a while seems ok. NB is at 1.5V. shocking.gif
*
There is something wrong with your setting.
Most e6600 can run at 400x8 at stock vcore [1.325] like what i'm using now.

I've tested 3 x e6600 from different batches and one e6600 ES, all of them manage to pass orthos more than 24 hours @ stock vcore.

Like my setting, i run my e6600 @ stock vcore @ stock NB and manage to run orthos more than 12 hours.

There is something wrong with your setting that i don't know what it is.
Hmm... hmm.gif
sup3rfly
post Jun 30 2007, 07:51 AM

Techno Slave
******
Senior Member
1,561 posts

Joined: Jan 2003
From: 秋葉原電気街


QUOTE(Joseph Hahn @ Jun 30 2007, 01:07 AM)
Er nope lol.

Ok here's a report. What i did just now is clear CMOS and load optimized default (as suggested by almostthere... thanks man). Then i tried your method of pumping up the NB voltage. Guess how much i need to enable me to type this post. 1.45V in BIOS. doh.gif At 1.40V load windows a bit then BSOD. Now running at 400x9 at 1.52V but Orthos fail straightaway i have no idea why but Windows Experience Index benchmark passed. Not enough VCore or what. shakehead.gif

What's been stopping me before is the CPU Thermal Management feature. When i disable it, i won't be able to boot into windows at all.


Added on June 30, 2007, 2:29 amOk 400x9 seems too much i keep getting BSOD when Orthosing even when VCore is at 1.55V mad.gif (isn't this batch supposed to be good... adoi... doh.gif... or is it the mobo...), now running at 400x8 at 1.42V. Orthos for a while seems ok. NB is at 1.5V. shocking.gif I will try to look for a sweet voltage spot at this CPU clock tomorrow.

About the BIOS, i seem to be able to change every other settings and made Windows boot EXCEPT the DRAM setting. If i touch any setting in that section i won't be able to boot at all. So i HAVE TO leave it at Auto. doh.gif It sets my memory at 5-4-4-12. shakehead.gif What's the use of the BIOS setting if i can't tweak it haih... doh.gif

Bah enough for tonight i'm tired. rclxub.gif

For good measures...  doh.gif  doh.gif  doh.gif  doh.gif  doh.gif  doh.gif  doh.gif  doh.gif  doh.gif  doh.gif
*
hey why dont u try to set ur memory manually as 5-4-4-12... like that also got problem??? if that the case u suspect ur memory is holding u back....btw how much vdimm are u using???? try to increase it a bit... try like 1.9 - 2.0 smile.gif
Eoma
post Jun 30 2007, 03:42 PM

- ,. -
Group Icon
Elite
4,603 posts

Joined: Jan 2003
From: PJ


QUOTE(sHawTY @ Jun 30 2007, 07:41 AM)
There is something wrong with your setting.
Most e6600 can run at 400x8 at stock vcore [1.325] like what i'm using now.

I've tested 3 x e6600 from different batches and one e6600 ES, all of them manage to pass orthos more than 24 hours @ stock vcore.

Like my setting, i run my e6600 @ stock vcore @ stock NB and manage to run orthos more than 12 hours.

There is something wrong with your setting that i don't know what it is.
Hmm... hmm.gif
*
Hmmm, mine won't pass Orthos either at 400x8; about 2 minutes then it fails. That was at 1.36v. It's fine now at 345x9 @ 1.36v, vDIMM 2.125v.
Joseph Hahn
post Jun 30 2007, 04:58 PM

kpop k
*******
Senior Member
6,410 posts

Joined: Jan 2003
From: MLK
QUOTE(sHawTY @ Jun 30 2007, 07:41 AM)
There is something wrong with your setting.
Most e6600 can run at 400x8 at stock vcore [1.325] like what i'm using now.

I've tested 3 x e6600 from different batches and one e6600 ES, all of them manage to pass orthos more than 24 hours @ stock vcore.

Like my setting, i run my e6600 @ stock vcore @ stock NB and manage to run orthos more than 12 hours.

There is something wrong with your setting that i don't know what it is.
Hmm... hmm.gif
*
I don't know whether to laugh or what now. doh.gif I'm running at default VCore now. Orthos failed in less than 1 minute, BUT, i play Test Drive Unlimited and NFS:Carbon for more than 2 hours and nothing happened! No hang no BSOD no reboot! doh.gif NB still at 1.5V. Maybe the error came out because the NB voltage is too high? I haven't try pulling it down maybe later, but i think if i go less than 1.4V i'll BSOD straightaway. doh.gif

QUOTE(sup3rfly @ Jun 30 2007, 07:51 AM)
hey why dont u try to set ur memory manually as 5-4-4-12... like that also got problem??? if that the case u suspect ur memory is holding u back....btw how much vdimm are u using???? try to increase it a bit... try like 1.9 - 2.0 smile.gif
*
Dunno bro. Maybe i'll try that later but i'm ok with this slightly loose timing now. My VDimm is 2.2V. It's the default voltage for my RAM at DDR1000 4-4-4-5 timing.
sHawTY
post Jun 30 2007, 06:57 PM

Frequent Reporter
********
All Stars
14,908 posts

Joined: Jul 2005

QUOTE(Eoma @ Jun 30 2007, 03:42 PM)
Hmmm, mine won't pass Orthos either at 400x8; about 2 minutes then it fails. That was at 1.36v. It's fine now at 345x9 @ 1.36v, vDIMM 2.125v.
*
QUOTE(Joseph Hahn @ Jun 30 2007, 04:58 PM)
I don't know whether to laugh or what now. doh.gif I'm running at default VCore now. Orthos failed in less than 1 minute, BUT, i play Test Drive Unlimited and NFS:Carbon for more than 2 hours and nothing happened! No hang no BSOD no reboot! doh.gif NB still at 1.5V. Maybe the error came out because the NB voltage is too high? I haven't try pulling it down maybe later, but i think if i go less than 1.4V i'll BSOD straightaway. doh.gif
*


I'm running orthos again as the last orthos i did i forgot to take a screenshot.

Right now running on these settings:

Processor: e6600 3.2GHz @ 400X8 @ Stock Vcore [1.325Volts]
Northbridge: 1.3Volts
Ram: Crucial Ballistix DDR2 PC2-8500 1066MHz 2GB Kit @ 801MHz @ 4-4-4-12 @ 2.1Volts

I'll post a screenshot on the orthos, CPUz and Smart Guardian all together in one picture.

How long do i need ey?
12 Hours? 8 Hours? or Full 24 Hours? hmm.gif

This post has been edited by sHawTY: Jun 30 2007, 06:57 PM
remysix
post Jun 30 2007, 08:03 PM

Hardcore Leecher!!!
******
Senior Member
1,311 posts

Joined: Jan 2003
From: Puchong/Deep Beach


QUOTE(sHawTY @ Jun 30 2007, 06:57 PM)
I'm running orthos again as the last orthos i did i forgot to take a screenshot.

Right now running on these settings:

Processor: e6600 3.2GHz @ 400X8 @ Stock Vcore [1.325Volts]
Northbridge: 1.3Volts
Ram: Crucial Ballistix DDR2 PC2-8500 1066MHz 2GB Kit @ 801MHz @ 4-4-4-12 @ 2.1Volts

I'll post a screenshot on the orthos, CPUz and Smart Guardian all together in one picture.

How long do i need ey?
12 Hours? 8 Hours? or Full 24 Hours? hmm.gif
*
anything more than 12 hrs can consider confirmed stability...but up to u...some just fire the orthos up for 8 hours...
Joseph Hahn
post Jul 1 2007, 12:04 AM

kpop k
*******
Senior Member
6,410 posts

Joined: Jan 2003
From: MLK
Well did some experiments again regarding NB voltage. Here's my report:

1.25V : AHCI BIOS came up.
1.30V : Disk read error.
1.35V : Load Windows and then BSOD straightaway.
1.40V : Windows is perfectly fine but game will crash after a while.
1.45V : Windows is fine, gaming is fine. icon_rolleyes.gif

I don't care about Orthos anymore. rclxub.gif


Added on July 1, 2007, 1:48 amuser posted image
I really need a fan for the NB. Will a 40mm fan do ? I wonder how to stick it there lol, can't put it on top, CPU fan already blocking. I think i have to put the fan on the side. doh.gif


Added on July 1, 2007, 1:52 amOh yeah my NB Strap is at default.

This post has been edited by Joseph Hahn: Jul 1 2007, 01:52 AM
almostthere
post Jul 1 2007, 11:26 AM

Kepala abah ko
Group Icon
VIP
3,773 posts

Joined: Jan 2003
From: Anywhere lah...as long got Kopi-O



Attached Image
Left's your's and right's mine. Compare LOL

Don't worry dude, mine' also pumped up that high too TBH.

And here's my advanced timings for Elpida's

All Precharge to Activate = 4
tRFC = 22
CS# to MCH ODT = 2
Write to Precharge delayed = 10
tWTR = 10
tRRD = 2
tRD_WR = 8
tRTP = 4
All precharge to ref. delay = 4
tRAS to tCAS = 4
RAS precharge = 4
tRAS = 9

Doing 8*400 on E6400 1.425v


Hyde`fK
post Jul 1 2007, 12:02 PM

D9s Killer
*******
Senior Member
2,378 posts

Joined: Jan 2003
From: Miri,Sarawak,Malaysia Status: Dead!



@Joseph Hahn

Tried set NB strap to 266 and lower down your NB voltage. I don't think need over 1.4v. My FSB is 457Mhz and my NB voltage is at default.
TStaxidoor
post Jul 1 2007, 12:20 PM

Regular
******
Senior Member
1,008 posts

Joined: Mar 2006
From: Kuantan Pahang



@Joseph Hahn
i think ur NB is too high...
Change ur NB voltage and change VTT higher... VTT is the way to success high FSB

@almostthere
ram timing so tight
Joseph Hahn
post Jul 1 2007, 02:13 PM

kpop k
*******
Senior Member
6,410 posts

Joined: Jan 2003
From: MLK
QUOTE(almostthere @ Jul 1 2007, 11:26 AM)
Left's your's and right's mine. Compare LOL

Don't worry dude, mine' also pumped up that high too TBH.
*
3140RPM. Is that your NB fan?? Seems like your NB voltage is 1.5V but temp much lower than mine haha. doh.gif I can see that you VTT is not default too. Hmm... hmm.gif

QUOTE(Hyde`fK @ Jul 1 2007, 12:02 PM)
Tried set NB strap to 266 and lower down your NB voltage. I don't think need over 1.4v. My FSB is 457Mhz and my NB voltage is at default.
*
Ok i'll give it a shot.

QUOTE(taxidoor @ Jul 1 2007, 12:20 PM)
i think ur NB is too high...
Change ur NB voltage and change VTT higher... VTT is the way to success high FSB
*
I see. Will try this.

Thanks for the suggestions. notworthy.gif


Added on July 1, 2007, 5:12 pmWell i tried pumping VTT and change NB Strap to 266MHz, doesn't make any difference at all to me sadly. sad.gif

Now trying 400x9 at a staggering 1.50V for both VCore and NB to get it stable. VTT and NB strap at default as in 400x8.

This post has been edited by Joseph Hahn: Jul 1 2007, 05:12 PM
sHawTY
post Jul 1 2007, 05:23 PM

Frequent Reporter
********
All Stars
14,908 posts

Joined: Jul 2005

Damn!
Just when orthos is reaching 23 hours, my house got black out! sweat.gif

No screenshot anymore since that stupid blackout. doh.gif

Anyway, my system running stable at this setting:
e6600 @ 400x8 @ Stock Vcore
NB @ 1.3
VTT @ Stock
SB @ Stock
Crucial Ballistix Tracer PC2-8500 2GB Kit at 800MHz @ 4-4-4-12 @ 2.1Volts

Everything runs stable on the last minute before the blackout. thumbup.gif
remysix
post Jul 1 2007, 06:57 PM

Hardcore Leecher!!!
******
Senior Member
1,311 posts

Joined: Jan 2003
From: Puchong/Deep Beach


QUOTE(sHawTY @ Jul 1 2007, 05:23 PM)
Damn!
Just when orthos is reaching 23 hours, my house got black out! sweat.gif

No screenshot anymore since that stupid blackout. doh.gif

Anyway, my system running stable at this settis long u know ng:
e6600 @ 400x8 @ Stock Vcore
NB @ 1.3
VTT @ Stock
SB @ Stock
Crucial Ballistix Tracer PC2-8500 2GB Kit at 800MHz @ 4-4-4-12 @ 2.1Volts

Everything runs stable on the last minute before the blackout. thumbup.gif
*
as long u know that ur proc ran 23hrs without fail is good enuff...sure stability...but a screenie would be good as well...running at that speed wif default vcore and WC summore...i guess ur temp is super duper low la like that...really gr8 to see the proc found the rite owner...good for you bro thumbup.gif

41 Pages « < 27 28 29 30 31 > » Top
 

Change to:
| Lo-Fi Version
0.0273sec    0.26    6 queries    GZIP Disabled
Time is now: 3rd December 2025 - 03:18 PM