• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Bad ram?

R

Rahminator

Senior member
OK, my computer was running absolutely flawlessly for over a month, and yesterday it started acting up with BSODs. Today, I got random reboots and my comp failed to post until I cleared the cmos. Then it got past post, but wouldn't boot into Windows (stuck at Verifying DMI pool data). I rebooted several times and noticed that it only detected 512MB of 640MB that I have (2x256, 1x128 - all Crucial). I tried to seat ram in all possible slot combinations, and the 128MB stick gets detected only sometimes (when it feels like it =/), and when it gets detected I have big problems in windows and in general. Could my overclock have killed it? My fsb is only at 135MHz and I think I can rule that out as a possible cause since I've seen people with >150fsb with this ram and no problems. Could it really be the aggressive timings that killed it (CAS 2, 4 bank interleave, 2t, 5t, 2t, 4 level, 1t command timing)? The only difference between the 128MB stick and the 256MB sticks is that the former is single-sided but I doubt that has anything to do with it (then again, I'm not a ram expert so enlighten me if you can). System specs:
Athlon XP 1600 1.4 @ 155 (135x11.5)
Shuttle AK31A
PNY Verto GeForce 2 Ti (250/440)
SB Audigy
Linksys 10/100 NIC
Seagate Barracuda 4 40GB
Nec 8/40 DVD
Plextor 12/10/32A
300W Antec PSU (5V is at 4.92-4.95 idle, 4.89 load)

Again, with 512MB my system is running like it always was. *Boogle*. Thanks for help in advance 🙂.
 
OK, I've tried one more thing. I removed 2x256MB and tried posting with just the 128MB. My comp just gave two long beeps (it maybe would have given more beeps but I turned off my comp and concluded that 128MB is indeed dead). Oc killed it or was it just a ticking timebomb that was bound to explode sooner or later? I will call Crucial and get replacement part.
 


<< ... or not fully seated - sometimes have to push them in pretty firmly. >>



I've seated and reseated the ram many times. I'm 100% positive that it's dead. Now I'm asking is it possible that aggressive timings killed it?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top