fried my RAM

  • Thread starter Thread starter anon5391
  • Start date Start date
A

anon5391

I think I've fried my RAM.

I've got 2 sticks of PC2100 DDR RAM; 1 x 256MB Kingston, 1 x 256MB Generic
(the sticker says "elixir")

I've been messing around with overclocking & went as far as 135FSB. I
started getting BSOD "driver IRQL not less or equal" (XP) and random
freezes/reboot.

I set everything back but the problem persists. I've removed the generic RAM
& I'm now running with just the 1 stick of Kingston. So far so good. How
likely is it that I've fried the generic RAM with just this slight
overclock? A 2mhz o/c seems negligible to me. Appreciate your comments. TIA
 
anon5391 said:
I think I've fried my RAM.

I've got 2 sticks of PC2100 DDR RAM; 1 x 256MB Kingston, 1 x 256MB Generic
(the sticker says "elixir")

I've been messing around with overclocking & went as far as 135FSB. I
started getting BSOD "driver IRQL not less or equal" (XP) and random
freezes/reboot.

I set everything back but the problem persists. I've removed the generic RAM
& I'm now running with just the 1 stick of Kingston. So far so good. How
likely is it that I've fried the generic RAM with just this slight
overclock? A 2mhz o/c seems negligible to me. Appreciate your comments. TIA

You need to test one stick at a time
Click to expand...
peter
 
anon5391 wrote:

I set everything back but the problem persists. I've removed the generic
RAM & I'm now running with just the 1 stick of Kingston. So far so good.
How likely is it that I've fried the generic RAM with just this slight
overclock? A 2mhz o/c seems negligible to me.
Click to expand...

If it causes problems going 2 mhz over, it was bad to start with! ANY 133
ram should easily clock to 140 and even if it didn't, shouldn't damage it.
 
BigA:

Like the book sez ... 'he who lives by the hack, dies by the hack ...'

r hartman
*****************
 
anon5391 said:
I think I've fried my RAM.

I've got 2 sticks of PC2100 DDR RAM; 1 x 256MB Kingston, 1 x 256MB Generic
(the sticker says "elixir")

I've been messing around with overclocking & went as far as 135FSB. I
started getting BSOD "driver IRQL not less or equal" (XP) and random
freezes/reboot.

I set everything back but the problem persists. I've removed the generic RAM
& I'm now running with just the 1 stick of Kingston. So far so good. How
likely is it that I've fried the generic RAM with just this slight
overclock? A 2mhz o/c seems negligible to me. Appreciate your comments. TIA
Click to expand...

test before you stress

http://www.memtest86.com/

Gordon
 
On Sun, 16 Nov 2003 12:15:48 +0800, "anon5391" <[email protected]>
wrote:

You haven't fried it. It is typical behaviour of generic RAM.
There are two things you can try. Try use Generic RAM only instead of
the Kingston Memory. You might still get a stable system. If that is
the case, you have some compatibility problem [Very usual for Generic
RAM].

There is another thing you can try if the above still give you BSOD,
try lowering your memory frequency way down to the slowest your
motherboard can support, don't use "By SPD". If it runs fine, that
means the memory manufacturer has programmed some overly optimistic
memory timing into EEPROM on the memory.

If it still failed, chuck it away, the memory was faulty in the first
place. [May not have exhibit the faultiness when you mix with other
RAM but will do so when the system is heavily stressed]
 
I think I've fried my RAM.
Click to expand...
I've got 2 sticks of PC2100 DDR RAM; 1 x 256MB Kingston, 1 x 256MB Generic
(the sticker says "elixir")
Click to expand...
I've been messing around with overclocking & went as far as 135FSB. I
started getting BSOD "driver IRQL not less or equal" (XP) and random
freezes/reboot.
Click to expand...
I set everything back but the problem persists. I've removed the generic RAM
& I'm now running with just the 1 stick of Kingston. So far so good. How
likely is it that I've fried the generic RAM with just this slight
overclock? A 2mhz o/c seems negligible to me. Appreciate your comments. TIA
Click to expand...

Try put it all the way to CAS 3 [Very conservative and slow], if
problem persist return your RAM to the manufacturer, the RAM is faulty
in the first place.
 
anon5391 said:
I think I've fried my RAM.

I've got 2 sticks of PC2100 DDR RAM; 1 x 256MB Kingston, 1 x 256MB Generic
(the sticker says "elixir")
Click to expand...


for the small savings in price...it;s just not worth it to bother with
generic ram!
 
philo said:
for the small savings in price...it;s just not worth it to bother with
generic ram!
Click to expand...

While such advice may at first glance seem too simplistic for anon, it's by
far the best advice given in response to his post. I've been assembling
systems for myself, friends, family, coworkers, etc. for about 15 years now,
and it's amazing how much hassle you'll save yourself ifyou avoid generic
(sometimes called "broker grade") RAM. Generic baked beans compared to
brand-name baked beans might be OK if you're lucky, but your chances of
getting generic memory to work reliably with a given motherboard are much
slimmer, IMHO. It's just not worth it. I would always recommend spending
the few extra bucks and getting brand-name memory. As for my personal
("production") system, I have a 512MB stick of Mushkin 2-2-2 Hi Perf
"Black"... the Rolls-Royce of memory! Yeah, it ain't cheap, but gosh is it
good stuff. :-)
 
anon5391 said:
I think I've fried my RAM.

I've got 2 sticks of PC2100 DDR RAM; 1 x 256MB Kingston, 1 x 256MB Generic
(the sticker says "elixir")

I've been messing around with overclocking & went as far as 135FSB. I
started getting BSOD "driver IRQL not less or equal" (XP) and random
freezes/reboot.

I set everything back but the problem persists. I've removed the generic RAM
& I'm now running with just the 1 stick of Kingston. So far so good. How
likely is it that I've fried the generic RAM with just this slight
overclock? A 2mhz o/c seems negligible to me. Appreciate your comments. TIA
Click to expand...

Well its as simple as this before your attempts to overclock the generic ram
was ok and after it was faulty. Either the generic ram was going bad anyway
or that small overclock damaged it.
 
Back
Top