Support NeoGAF

[Biff Hardbody]

Hi All,

I noticed my browser started to shut down recently. The last time it did this was because of failed memory. So, I booted up memtest and sure enough I got a bunch of errors immediately. When I had this problem before, I changed the ram voltage and it fixed everything. But now, I have no idea what to do. I could mess with the cas latencies, but I'm not sure if that'll do anything. I imagine sending the ram back would be the next step.

I'm using Crucial ballistix ram pc-3200. DDR voltage is 2.8 V and the cas latency is at 2-2-2-8. Any advice is appreciated.

 

[Biff Hardbody]

I've tried the following cas latencies-

2-3-2-8
2-3-2-6
2-3-2-10

The ram fails the test instantly. My DDR voltage is at 2.8v I'm unsure of what to do, as the only problems I've heard of being able to fix are cas latencies and DDR voltage. I've messed with all of them, and it still fails the test instantly. I know OS corruption is not far behind, and I'd like to fix it as soon as possible.

Anyhow, here's my other info in case you can help me.

Athlon 3800
ASUS 939 Motherboard
Crucial Ballistix RAM
GeForce 6800 GT
Neo Power 480 Watt
200 GB Seagate IDE HD

Here is the info in my memory configuration.

Mem CLK: 100 MHZ

Memclock Mode: Limit
Dram over 4G remaining: Disabled
Bank Interleaving: Disabled
Node Interleaving: Disabled
Burst Length: 8 beats
Cas Latency: 2.0
TRC: Auto
TRFC: Auto
TRCD: 3 CLK
TWR: Auto
TRWT: Auto
TRAS: 6 CLK
TRP: 2 CLK
TWCL: Auto

Asynclat :Auto
TWCL: Auto

Like I said before, I tried the above cas latencies and the memory fails instantly in memtest. The voltage is at 2.8v

Any help is appreciated.

 

[Biff Hardbody]

OK, I just noticed the ram was set to DDR200 instead of the correct DDR400. I fixed that. I still get memories in the memory test though, even after that change and different cas latencies.

Any ideas?

 

[Pfucata]

Run your ram at the specified CAS rating -- if it still fails, see if you can try it in a different mobo -- if that's still broken, go ahead and contact Corsair and take advantage of the lifetime warranty

 

[Biff Hardbody]

Thanks for responding. I've tried the specified CAS settings, but no go. I don't have another mb to try them out on. If there's nothing else I can do, I'll be returning it...bumping this thread for anymore advice.

 

[seanoff]

new RAM!!

by whatever means u can get it. If its free all the better. Once its gone, forget it replace it and get on with life.

 

[Joeholley]

RAM failures in a good memory testing program (memtest86 is what I recommend) don't ALWAYS mean bad RAM, but if you have the lifetime warranty, that's the best place to start.

 

[Biff Hardbody]

I also noticed that mem test reports two things that I found odd. Not sure if they are of any consequence though.

It says my cpu is running at 2403 mhz, when I have it listed in the bios as 2400 mhz.

I also noticed it reports me as having 1023 mb of ram, not 1024.

Anyhow, a slew of fails are being reported. I'm sure if I left it on for a few hours it would be in the tens of thousands.

I've done some reading about crucial's ballistix line on hardoc forum, and I see many people have had the same problem...apparently the ram is very shoddy. In the end they all returned it and switched to a new ram. I am hoping this isn't the case for me, and some setting I haven't changed yet will fix it.

I guess I'll call crucial tomorrow...

 

[metsallica]

I had a similar issue, and the way I fixed it was kind of strange. Maybe it'll work for you. When I build a new computer, I like to stress-test it with prime95 for at least 24 hours (a good idea generally when making a new machine). My most recent PC would crash prime95 in seconds. I discovered that the RAM voltage was set too low, so I fixed it. After that, it would make it about 20 minutes in prime95. At that point I was stumped. I was eventually checking some settings with CPU-Z when I noticed my processor speed was a bit over the 2.4 ghz (FX-53) it was set to operate at in the BIOS. After that, I bumped up my CPU voltage the smallest allowed increment, and it solved all of my problems. Prime95 ran for 30+ hours (I eventually stopped it) and I've used the computer for a few months without issue.

Give it a shot; see if it helps. I honestly think you're still dealing with a RAM issue but I figured my .02 might help.
Prime95: http://mersenne.org/gimps/p95v238.exe

Also, have you tried the other RAM slots on your mobo?

 

[Biff Hardbody]

Thanks man, I'll run that test tonight or tomorrow.

Like I posted above, I noticed my cpu is listed as 2403 mhz in the memtest setting, but in my bios its at 2400mhz. I tried upping the voltage. First 1t .25, then all the way to 1.0 higher. Nothing changed.

I'm wondering if there's a way to change the mhz so its listed in mem test at what it is in the bios.

Again, thanks. I'll run that test tomorrow. I have to do some stuff on the pc tonight and tomorrow morning.

 

[Biff Hardbody]

I switched the two sticks around, and noticed that in one instance memtest reports 999.1 mb failed, but in the other switch it reports only 539 mb failed. When using 1 stick alone, the pc does not boot up.

I'm guessing this means boths ticks are bad, but one is really bad and they need eachother to work...

augh, this sucks. I'm calling crucial tomorrow.

 

[Biff Hardbody]

bump

 

[Shompola]

sounds like the mem is a bad one, return it for a new one or refund.

 

[Diablos]

New RAM, or lower the FSB speed. There is simply no other way around it. RMA is your friend.

 

[Biff Hardbody]

Thanks for responding, fellahs. It sounds like I'll have to RMA. Still, I want to make absolutely sure there's not some setting I'm missing.

I'm using CPU-Z right now. There's one stat I'm unsure of.

FSB: DR Ram: CPU/12.0

Is that correct? I see most people have a 1:1 setting in reviews of the memory, so I'm wondering...

Anyhow, I'd call crucial today but they closed. So, I'll do some more research and see if theres anything I can do.

Thanks again.

 

[Sander]

I also noticed that mem test reports two things that I found odd. Not sure if they are of any consequence though.

It says my cpu is running at 2403 mhz, when I have it listed in the bios as 2400 mhz.

I also noticed it reports me as having 1023 mb of ram, not 1024.

A slightly different clockspeed is normal. The clockgenerators used aren't 100% accurate.

That 1MB RAM difference is a common occurrence.

I'm using CPU-Z right now. There's one stat I'm unsure of.

FSB: DR Ram: CPU/12.0

Is that correct? I see most people have a 1:1 setting in reviews of the memory, so I'm wondering...

Yes that is correct. The 3800+ runs at 2.4GHz and your memory at 200MHz (CPU/12.0). 1:1 refers to the ratio between FSB (or Hypertransport for A64's) and memory.


As for the problem at hand, if this started happening without you changing any settings it seems as if your RAM simply has gone bad. You can try setting the RAM timings to 3-3-3-8, or even 4-4-4-8. But even if that alleviates the problem, it's just circumventing it.

 

[Pfucata]

Misread you as having Corsair ram. But no worries, both Corsair and Crucial have lifetime warranties on their premium ram.

 

[Biff Hardbody]

Thanks guys...I appreciate you taking the time to explain it to me. I'm going to have to RMA.

Thanks again.

 

[Biff Hardbody]

Fellahs, just 1 more question.

My pc is working right now and I'd like to continue to use it. Will this corrupt ram hurt any of my other hardware until I can get a replacement? I know it may corrupt my os, but can it hurt my cpu, graphics, card, motherboard, ecd?

If thats the case I'll just shut it off.