New CPU and the Corsair Low-latency is unstable at 166MHz...

[brigden]

Before I begin, here are the system specs:

Athlon XP 2700+
EPoX 8RDA+ (Rev. 1.1 - Latest BIOS flashed)
512 MB of Corsair TWINX512-2700LLPT (2-2-2-5)
ATi Radeon 9700 Pro
Maxtor DiamondMax Plus 9 (6Y080P0) 80.0 GB @ 7200 RPMS
Sony CRX1611
Enermax EG365P-VE FM 350 Watt ATX PSU

Vdd: 1.58V
Vcore: 1.68V
Vdimm: 2.65V
+5V: 4.91V
+12V: 12.28 to 12.34
-12V: -12.52 to -12.61
-5V: -5.34 to -5.40
VBAT: 3.24V
5VSB: 5.04

CPU and DIMM voltages are set to auto.

Now, the 2700+ is brand-new. The previous processor was an 1800+, and along with the RAM running underclocked, but synchronously at 133MHz with timings of 2-2-2-5, the system was rock-solid, passing memtest86 error-free and hours of 3DMark2001 SE and 3DMark2003.

I carefully popped in the new 2700+, reset CMOS, and re-entered the appropriate BIOS values. The motherboard reported no problems and posted. Windows quickly booted and I thought all was well. Within a few minutes I started getting errors all over the place. IE would fail, Outlook would fail, Explorer would crash, etc. I even got a few BSODs.

I got so fed up with all the errors I was receiving I simply decided to reformat and reinstall.

With the RAM running at 166MHz, no matter what the CPU's FSB was set at; 100, 133, or 166MHz, the Windows XP installation would fail. Yet with the RAM running at 133MHz, and the CPU's FSB at 166MHz the Windows installation was sucessful.

Upping the DIMM voltage from 2.65 to 2.77 allows me to install Windows error free, but once installed I experience errors. For instance, when I attempt to execute the 128MB SP1a file I received the following dialogue:

"File is corrupt."

I redownloaded the file, but receive the same error.

I booted up Memtest86. With the memory speed at 166MHz, timings at 2-2-2-5, and voltage set to 2.77, I received a few hundred, even over one thousand errors before test 4 had even completed. Inserting one DIMM and even swapping the slots made no difference.

I turned the FSB down to 133MHz and as I type this, Memtest86 is currently running test #8 with no errors thus far...

Keep in mind, when I first bought this memory I tested it along side my 1800+ with the FSB at 133MHz. I ran the RAM synchronously at 133MHz and passed all tests over a six hour period. Not one error.
I popped in two modules of Kingston ValueRAM with Infineon chips, and even though Memtest86 finds errors in test #8, the RAM is so far stable.

This leads me to believe the Corsair RAM is unstable and the cause of the errors. However, the RAM is allegedly tested at 166MHz with timings of 2-2-2-5. So, why is this RAM unstable at its default speeds? Could the CPU be at fault? Could it be the motherboard? I need help isolating the offending hardware so I can RMA appropriately.

 

[boyRacer]

Try vdimm at 2.7 or 2.75

 

[mechBgon]

Originally posted by: boyRacer
Try vdimm at 2.7 or 2.75

word The 8RDA+ has discrete settings of 2.63V and 2.77V, and I seem to recall it defaulting to 2.63V, so try 2.77V. Good luck brigden!

 

[brigden]

Thanks for the replies, guys!

I've set the voltage from 2.65 to 2.77, which was the next option up according to my BIOS. I've upped the memory's frequency to 166MHz and now Windows appears to be installing without error.

Once Windows is installed I will run memtest86 to check the stability.

 

[brigden]

Windows installed fine, but when I tried to execute the 128MB SP1a file I received the following dialogue:

"File is corrupt."

I redownloaded the file, and put it on a brand-new CD-R, and even that file wouldn't install...

Why? Is this problem related to the memory? The new processor?

 

[xenontech]

Originally posted by: brigden
Windows installed fine, but when I tried to execute the 128MB SP1a file I received the following dialogue:

"File is corrupt."

I redownloaded the file, and put it on a brand-new CD-R, and even that file wouldn't install...

Why? Is this problem related to the memory? The new processor?

I have the same problem too with my XP2700+ and my Corsair XMX DDR 3200 CAS 2 memory on DFI NFII Lanparty Ultra. I cannot achieve a 2-2-2-5 timing. So I just leave it as "optimum". I have my CPU voltage = 1.75V and DRAM voltage = 2.8V and chipset = automatic. I still get the IE error or get an error blue screen from time to time. The only thing I did to mine was set the CPU speed to 210Mhz (equivalent to FSB of 420Mhz), CPU multiplier of 11, and DDR ratio of 1:1. But, my system is terribly unstable. Probably XP2700+ is not a good overclocker. I wished someone could help.

 

[brigden]

But I'm not overclocking! I'm running EVERYTHING at stock speeds! This is so frustrating...

 

[brigden]

I booted up memtest86. With the memory speed at 166MHz, timings at 2-2-2-5, and voltage set to 2.77, I received a few hundred, even over one thousand errors before test 4 had even completed. Inserting one DIMM and even swapping the slots made no difference.

I turned the FSB down to 133MHz and as I type this, memtest is currently running test 8 with no errors thus far...

Keep in mind, when I first bought this memory I tested it along side my 1800+ with the FSB at 133MHz. I ran the RAM synchronously at 133MHz and passed all tests over a six hour period. Not one error.

So, the Corsair will run error-free at 133MHz, but freakout at 166MHz? Could the processor cause this? I never tried testing the RAM asynchronously at 166MHz with the 1800+...

 

[brigden]

I've edited the first post to reflect the testing I've done.

 

[brigden]

I swear to god I'll smash this system and buy a Dell...

 

[BuckNaked]

Relax your memory timings and run Memtest again.... I bet it will run without errors... I had some Corsair PC3200LL stuff that would do the same thing at default speeds. I relaxed the memory timings and it ran fine. Then I RMA'd it for another set that ran fine at 2,2,3,d on a 200MHz FSB....

Dave

 

[brigden]

Originally posted by: Buck_Naked
Relax your memory timings and run Memtest again.... I bet it will run without errors... I had some Corsair PC3200LL stuff that would do the same thing at default speeds. I relaxed the memory timings and it ran fine. Then I RMA'd it for another set that ran fine at 2,2,3,d on a 200MHz FSB....

Dave

Guess what? You're right. I relaxed the timings to 6-3-3-2.5 and it ran Memtest with no errors. But why did it run 2-2-2-5 at 133MHz? Is it bad RAM? Is it the mobo? The CPU?

 

[BuckNaked]

The memory timings are related to the FSB speed... the 2,2,2,5 timing is operating at a higher frequency at 166MHz than at 133MHz... If its PC2700 RAM, and its rated for 2,2,2,5 then its bad RAM and you should exchange it for another set. You might want to double check the rating though, Corsair has relaxed there memory timings for later versions of RAM because alot of people are having issues similar to yours.... Some of the retailers still show older (faster) memory timings in there ads than what the memory is currently rated for by Corsair.... Not sure if that made any sense... PM me if you have any other questions...

Dave

 

[brigden]

We popped the RAM in my brother's P4 2.4c running on a P4P800 and still got errors at 166MHz. I'm still not convinced the RAM is totally the cause of the problem.

Running the Kingston ValueRAM at 133MHz and I got no errors, same as the Corsair, but running both at 166MHz and we experienced errors.

The only way I don't get errors at 166MHz is if I relax the timings. Could the mobo be an issue?

I think I'm going to RMA the RAM anyway, and if I get new stuff back and still get the same problems the mobo will be on its way...

 

[IQJUMPuw]

You have a bad ram. Trust me on this. I know for a FACT that it's your ram. If your ram runs fine at 166MHz in relaxed timings, but not at 2-2-2-5, it's the ram. I've had the same exact problem with my axp 2000+ and kingston hyperx 512mb 2-2-2-5. whatever I did, the ram would not run at cas2, 1t command speed. It wouldn't install windows 2k. So I just ran it at cas 2.5 speed until I got a Corsair XMS 512mb pc2700 and that fixed the problem. I'm now running the ram at 166mhz with the most aggressive timings (turbo mode) with default voltages. If you have to increase the voltage just to run at the advertised speed, you got a bad ram my friend. RMA it back and get another one and hope the new one will be good.

 

[brigden]

Thanks for the reply. I will RMA the RAM this week.

Now I need to find a replacement...