New pc133 cas2 chip is failing memory test on my ABIT KT7 but still boots...weird sandra results also...

[shurato]

I just got my pc133 cas2 generic chip and it seems to fail the memory test in the bios any time i set it to pc133 mode whether its cas2 or cas3. I have my abit board set to hclk+pciclk which should set it to 133 mode. It doesnt have a problem in the bios memory test when i set it to pc100 mode. Sandra is also giving me wierd readouts, stating my memory bus speed is at 150mhz.... the information on the dimm is ...
128mb 16x(8mx8) SDRAM pc143u-333-522 (CL3 upto 143mhz)
besides the fact that my memory bus speed reads 150mhz, my PCI bus speed is reading 50mhz also... speed multiplier is set to 1/2x. Shouldnt this be at 33mhz? I cant find anywhere in the bios to change this. Im getting error messages in sandra stating my agp, pci, isa/dma speed is too high and to reduce the FSB or the multiplier. How do i do this in the bios? I must be overlooking something. I hope i dont have a bad memory chip.

 

[jinsonxu]

Not sure about your first problem. But don't worry about Sandra, certain versions (Yes, even the latest) have problems with the KT133 chipset. The Asus board has the problems with Sandra's reports too.

 

[Harrisment]

I oredered some memory like that too, did you get it at Premier Systems? Mine comes in tomorrow, I'll post my experiences. I'll be using it on an MSI K7T Pro

 

[shurato]

Yes i purchased my memory from Premier systems....which might bite me in my ass... well thats what i get for trying generic memory... anyone got any idea why it fails the memory test in the bios? Should i definitly return this chip or continue to try to see whats going on.

 

[BobsBigBoy]

Try testing it with Doc Memory, which you can get at simmtester.com for free. Excellent memory tester.

--- BBB

 

[shurato]

docmemory keeps locking up on me after i do the first burn test cycle...it happened on my older pc100 memory also.

 

[shurato]

ok i got docmemory to work and the chip itself tests out fine but that doesnt determine if this chip is truely rated for pc133. I called their support and the CSR told me that i was supposed to set my memory to pc100 in the bios and that the internal "spd"? would set it to pc133. Is this correct? that means he wants me to set it to hclk instead of hclk+pciclk. That doesnt make sense, when i do that, i dont get a memory test error in the bios and in sandra it shows the memory bus speed as 100mhz. And my scores are slightly lower than when i used my pc100 corsair 128meg chip in it. I've even set my corsair 128 to pc133 before without a memory error on startup. Did i get a bogus chip here?

 

[jinsonxu]

Post you score.

 

[DaddyG]

From your specs this is not CAS2 memory but CAS3. Turn the memory speed down to slowest (8ns maybe), set memory clk to host+pci, then crank up the speed slowly.

 

[Modus]

<<I called their support and the CSR told me that i was supposed to set my memory to pc100 in the bios and that the internal &quot;spd&quot;? would set it to pc133. Is this correct?>>

Nope, that's BS. He just wants your system stable so he can get rid of you. I would do what DaddyG said, try really conservative RAM timings and slowly work your way up until you loose stability. If you can't reach PC133 CAS2 at all, return the sucker for a refund or exchange, because you bought it under that pretense.

Modus

 

[Possum]

shurato, how did you get DocMem to stop crashing on you in the middle of the first cycle? It happened to me no matter what FSB I had set, and what memory settings I used (both fastest and slowest/most stable).

 

[aUt0eXebat]

The Anandtech review recommends using this type of RAM for the KT7 Raid MB: here

 

[AMB]

My Crucial PC133 CAS 3 will run at CAS 2 happily

 

[Harrisment]

now i'm all nervous, hopefully mine will work

 

[shurato]

Possum: i got my docmemory to work by trying to create the boot disk with multiple floppies, i think i finally just copied over the system files cuz the install program just wouldnt do it. and i also plugged in my ps/2 mouse to control it instead of using the keyboard. (i have a usb mouse). I dont know how that helps but it worked for me. BTW, i just returned the memory back to Premier Systems. I am hoping it was just a fluke on my chip....please post your results here if you want. I'd like to see how others do with the memory.