Problems with running ram at 133mhz. could it be my psu???

[Tomas]

I just found out how to get my ram to run at 133mhz and it seemed stable at 1.1@1.2 109fsb. But it crashed sometimes when i played mp3s/videos or games just freezed. Then i tought it was that i ran the fsb to high so i putted it back to normal speed and then it wouldnt even boot into windows and if it did it would lock up after a few sec. Then i took my ram back to 100mhz and all worked fine both on default speed and on 1.2ghz. So i think its a bit strange that it boots on 1.2ghz(109fsb) and not on 1.1(100fsb)
So i wonder may it be my psu?? its 300watt tought it was enough for a tbird not oc. Also i noticed the fans seem to change sound when i load my cpu but i cant see any changes in the speed. I just hope it isnt the psu since i just bought this tower chase

[Tachyon]

If you had your RAM set to Hostclk+PCI, and had FSB at 109, you were running above 133. I'd guess that your RAM won't do that.

[Tomas]

yeah it isnt stable at that speed so u tought so too but when i put the fsp back to default speed it wont boot at all. Either freezr on windows boot screen or a few sec after i got in. but when i run it at 109fsb i get into windows but its really unstable like suddently lock if i run a mp3 or things like that. Yeah i know its strange i runs better at 109fsp.
Also tried too take out one od the ram and use only on in chase it was conflict between them but it freezed on both.

[Tachyon]

Tomas (Feb 19, 2001 01:49 p.m.):
I just found out how to get my ram to run at 133mhz and it seemed stable at 1.1@1.2 109fsb. But it crashed sometimes when i played mp3s/videos or games just freezed. Then i tought it was that i ran the fsb to high so i putted it back to normal speed and then it wouldnt even boot into windows and if it did it would lock up after a few sec. Then i took my ram back to 100mhz and all worked fine both on default speed and on 1.2ghz.

When you run at 133MHz you seem to have problems. When you set the RAM at 100MHz you say it runs fine. It appears that your RAM won't run at 133MHz. Are you at CAS2 or CAS3??


So i think its a bit strange that it boots on 1.2ghz(109fsb) and not on 1.1(100fsb)
So i wonder may it be my psu?? its 300watt tought it was enough for a tbird not oc. Also i noticed the fans seem to change sound when i load my cpu but i cant see any changes in the speed. I just hope it isnt the psu since i just bought this tower chase

[Tomas]

what is CAS2 and CAS3?? I just bought some 133mhz cheap ram. but i have tried too differente brand its the same so it must be this ****ty mobo

[Tachyon]

If you have CAS 3 RAM and you're running it at CAS 2, that may be the cause of your problem.

[Tomas]

how do i change CAS setting in kt7(non raid)?

[kat]

first go to soft menu and bump your core volts to 1.80 then set your i/o voltage to 3.50 then set your dram clock to hclk+pciclk fast cpu command decode to high, cpu drive strenght to 3,,,,, esc go to advanced chipset feature and set all three bank`s to fast and bank dram interleave to 4 way ...sdram cycle length to 3 this should get you to 109-110 fsb with out a problem ;D

[Tomas]

Im running it at (109)fsp 1.80volt, 1.1@1.2ghz stable but when i put my ram at 133mhz it gets really unstable. freezes either when im playing mp3/video or a game. So then i tought it was too high fsb for my ram so i bumbed the fsb back to default but then it wont even boot windows with my ram running on 133mhz:( So the odd thing is that if i set the fsb on 109 and ram speed on 133mhz it boots windows fine but isnt very stable when plaing games or running cpu intensive programs. I tought it should be the other way that it runs better on its default speed than it does oc. hmm WEIRD

[Tomas]

btw here is one problem i also have when running it at 133mhz. it freezes after memory count when timing set to lower than turbo. found out that it should be a bug in the bios:
Reported bugs


System fails to get past memory check during POST when Bank x/y DRAM Timing is set as Normal in Advanced Chipset Features setup and an SDRAM Cycle Length of 2 is used. [nb. Using WCPREDIT to look at the CMOS settings, it appears that the Normal setting sets an incorrect CAS Latency of binary 11 ("reserved") in the BIOS rather than the valid 2T or 3T options. This occurs when an SDRAM Cycle Length of 2 or 3 is chosen, but only seems to cause a system hang with the former.]

Havent checked which version of the bios i got but will it help if i update the bios?

[kat]

im not 100% sure but if setting back to 100 wont let you boot i would guess that the bois is at fault that is not at all normal!

[Tomas]

so i should try to update the bios??? Havent still tried CAS3 yet. should do it tomorrow. If not im thinking of a bios update

[kat]

for sure try cas 3 first, i also had generic ram and was only stable at 3 when running a high FSB when i upgraded to mushkin rev 3 i can know hit 114

what happens when you try 8/10 ns

[Tomas]

freezes after memory count:( it will only boot at turbo but then freezes on windows boot screen or a few sec after windows is booted. on both win2k and 98

[Tomas]

im off too bed now so il try it tomorrow morning. will post an update then

[Tomas]

I did not find any CAS3 and CAS2 in bios but i found md strength and when i changed that too low it booted at 133mhz and seems even to be stable at 1.1@1.2(109fsb) 1.75v But after running 3dmark2000 the temp rised too 47c so im thinking of ordering a Taisol CGK742092 Heatsink this link: http://www.overclockers.com/articles337/ and artic silver!! But i dunno if i should have artic silver glue or artic silver2. artic silver 2 was cheaper.

[DaveB]

Don't use the glue. It's for applications like a video card H/S fan where there's no clip to attach it.