PDA

View Full Version : Curious Kingston ValueRam PC2700...


Maxvla
12-06-02, 12:21 AM
ram is quite stunning at cas2 but won't boot at any speed cas1.5 or cas2.5

and even with the abit board i can't push reset and hold insert to clear the bootup. i hafta manually clear cmos with the jumper.

anyone else?

larva
12-06-02, 04:09 AM
My stuff will run at cas 2.5, but of course I never do as cas 2 works out so well. cas 1.5 at the type of clock speeds we are running is just a dream at present.

On the subject of handling of too agressive settings, the Asus boards do a lot better than Abits. On my BD7-II when I run the ram too fast the system plays a siren type sound out the PC speaker. I can then press reset, and hold the insert key as it reboots and it will come up on the defaults. If I run the cpu past its limits, the thing won't re-boot, won't play a tone, and does require the dreaded cmos clear proceedure to revive it. An Asus will come up on the defaults all by itself in this situation, and report cpu failed due to overclocking. This can make finding the limits of new hardware somewhat of a pain, but when those limits are higher than on other boards it doesn't seem such a bad compromise :)

Maxvla
12-06-02, 11:53 AM
Originally posted by larva
My stuff will run at cas 2.5, but of course I never do as cas 2 works out so well. cas 1.5 at the type of clock speeds we are running is just a dream at present.

On the subject of handling of too agressive settings, the Asus boards do a lot better than Abits. On my BD7-II when I run the ram too fast the system plays a siren type sound out the PC speaker. I can then press reset, and hold the insert key as it reboots and it will come up on the defaults. If I run the cpu past its limits, the thing won't re-boot, won't play a tone, and does require the dreaded cmos clear proceedure to revive it. An Asus will come up on the defaults all by itself in this situation, and report cpu failed due to overclocking. This can make finding the limits of new hardware somewhat of a pain, but when those limits are higher than on other boards it doesn't seem such a bad compromise :)
well obviously i wasn't expecting it to do 218mhz cas1.5... i tried it at 133mhz and it didn't work got the siren. tried it at 100mhz got the siren.

and when i went for cas 2.5 faster than 218mhz every time i had to clear cmos. now i know my chip is good up to 166mhz yet i was having this trouble at 164mhz.

larva
12-06-02, 05:12 PM
It's been my experience that the no siren/clear cmos stuff happens when you hit the cpu's limits rather than the ram being out of it's league. But it's hard to say, this may just be a trend rather than a rule. Have you tried 166 (since you got the Kingston) at 1:1? It is possible that the ram change (or others) may have cost a little fsb capability. With a system as close to the edge as yours is strange interactions can occur.

Maxvla
12-06-02, 07:37 PM
Originally posted by larva
It's been my experience that the no siren/clear cmos stuff happens when you hit the cpu's limits rather than the ram being out of it's league. But it's hard to say, this may just be a trend rather than a rule. Have you tried 166 (since you got the Kingston) at 1:1? It is possible that the ram change (or others) may have cost a little fsb capability. With a system as close to the edge as yours is strange interactions can occur.
actually no i havent and thats a good point about the fsb capability.

i will try that later tonight.