- Joined
- Aug 12, 2005
- Location
- Montreal, QC
A bit of context first, sorry if it gets too long... Specs are as follows:
Mainboard: DFI Lanparty UT nF4 SLI-DR @ 623-3 BIOS, FSB200
CPU: Athlon64 X2 4400+ @ stock 2.2ghz
RAM: Crucial Ballistix PC4000 1gb (x2) @ 2-3-3-8
GPU: Asus GeForce 7800GTX (x2) @ stock
HDD: WD Raptor 74gb (x2 in RAID0)
PSU: Enermax 660W EG851AX-VH pricey, full of rails and stability
Case: Lian-Li PC-V1000+
I've been running my rig at stock FSB (200Mhz) ever since I got it, and I noticed that this RAM seemed good enough to run at 2-3-3-8 at this FSB, which was rather good for 1gb sticks.
However, about a month ago, I started getting random bluescreens, especially in memory intensive apps like Photoshop. It definitely seemed like a RAM problem to me, and since memtest86 didn't find anything, I ended up checking my voltages. Sure enough, while DRAM normally runs at 2.5V, these Ballistix are supposed to run at 2.8V. So I changed that, and had two weeks of uninterrupted uptime.
Then, a week ago, it craps out again. Except this time, it won't even boot into windows before BSODing, and memtest86 reports thousands of errors at random memory ranges. Loosening the timings to the specced 3-4-4-10 doesn't help, nor does swapping or reseating the RAM. I found it extremely weird that the RAM would mess up overnight like this and wondered whether the problem was actually elsewhere. Asking Crucial tech support got me a generic "Run Windows memory tester and ask for a RMA if it fails" response. I ran Windows memory tester, and sure enough, it got errors as well. So I took the sticks out while waiting for a RMA number.
Now this is where it gets strange. On a random fling, I decided to put the sticks back in while waiting and experiment some more. Timings are still 3-4-4-10. I start running windows memory tester and leave it on. It gets tons of errors for two or three passes, then... The errors stop. Leaving it overnight yields flawless results past the initial passes.
I figure what the heck, and boot into windows and play around a bit. Photoshop is smooth, Titan Quest as well, and get no crashes for 3-4 days. Today I decide to set the RAM back to the original 2-3-3-8 and see if that mysteriously fixed itself too. Memtest has been running for 2 hours now and it's absolutely clean.
I'm absolutely boggled at this, what might've happened? Divine intervention visited upon my aging, underexploited rig? Should I send in the RMA I asked for anyway, or chalk it up to a freak accident that won't happen again?
Mainboard: DFI Lanparty UT nF4 SLI-DR @ 623-3 BIOS, FSB200
CPU: Athlon64 X2 4400+ @ stock 2.2ghz
RAM: Crucial Ballistix PC4000 1gb (x2) @ 2-3-3-8
GPU: Asus GeForce 7800GTX (x2) @ stock
HDD: WD Raptor 74gb (x2 in RAID0)
PSU: Enermax 660W EG851AX-VH pricey, full of rails and stability
Case: Lian-Li PC-V1000+
I've been running my rig at stock FSB (200Mhz) ever since I got it, and I noticed that this RAM seemed good enough to run at 2-3-3-8 at this FSB, which was rather good for 1gb sticks.
However, about a month ago, I started getting random bluescreens, especially in memory intensive apps like Photoshop. It definitely seemed like a RAM problem to me, and since memtest86 didn't find anything, I ended up checking my voltages. Sure enough, while DRAM normally runs at 2.5V, these Ballistix are supposed to run at 2.8V. So I changed that, and had two weeks of uninterrupted uptime.
Then, a week ago, it craps out again. Except this time, it won't even boot into windows before BSODing, and memtest86 reports thousands of errors at random memory ranges. Loosening the timings to the specced 3-4-4-10 doesn't help, nor does swapping or reseating the RAM. I found it extremely weird that the RAM would mess up overnight like this and wondered whether the problem was actually elsewhere. Asking Crucial tech support got me a generic "Run Windows memory tester and ask for a RMA if it fails" response. I ran Windows memory tester, and sure enough, it got errors as well. So I took the sticks out while waiting for a RMA number.
Now this is where it gets strange. On a random fling, I decided to put the sticks back in while waiting and experiment some more. Timings are still 3-4-4-10. I start running windows memory tester and leave it on. It gets tons of errors for two or three passes, then... The errors stop. Leaving it overnight yields flawless results past the initial passes.
I figure what the heck, and boot into windows and play around a bit. Photoshop is smooth, Titan Quest as well, and get no crashes for 3-4 days. Today I decide to set the RAM back to the original 2-3-3-8 and see if that mysteriously fixed itself too. Memtest has been running for 2 hours now and it's absolutely clean.
I'm absolutely boggled at this, what might've happened? Divine intervention visited upon my aging, underexploited rig? Should I send in the RMA I asked for anyway, or chalk it up to a freak accident that won't happen again?