Upgraded CPU... Corsair Low-latency is unstable at stock 166MHz...

[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?

 

[MasterFlash]

Originally posted by: 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.

You meant changing the voltage from 1.65 to 1.77 right? If not, that's ridiculously high. It seems weird that you can even step to a x.77 V, but I've never had an epox board... You should check your CPU temp. It shouldn't be hitting 55C just booting up. The other thing that was mentioned was make sure you have latest BIOS, and maybe try reflashing even if you do.

 

[brigden]

No, I meant 2.65 to 2.77. My motherboard doesn't have any voltage setting lower than 2.5. In fact, isn't most RAM 2.5V?

 

[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 in an effort to organize my testing.

 

[brigden]

Anyone?

 

[sandorski]

Originally posted by: 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+...

No, this is not a cpu problem. It is either your ram(are you sure the ram is rated for CAS 2 at 166?) or a weakness in the motherboard/ram implementation. If your ram is indeed rated for CAS 2.0 operation at 166, then it's possible a future BIOS update may fix the situation, but it may never work. IIRC, some NForce 2 motherboards(Asus A7N8 comes to mind) have issues with certain brands/models of ram. If this is the issue, then there is some kind of incompatibility between how the ram works and the NForce 2 chipset. The only way to fix this problem(if it is the problem) would be to either get a different motherboard or a known to work stick of ram.

 

[brigden]

OK, I've just finished running Memtest86 on the two Corsair DIMMs.

Each DIMM was tested seperately, in all three DIMM slots. At 133MHz both DIMMs passed all tests in all DIMM slots. At 166MHz both DIMMs experienced thousands of errors in all DIMM slots.

Now, I'm testing some Kingston ValueRAM. So far, the first DIMM passes all tests at 133MHz, but at 166MHz I get errors.

Upping the voltage only seems to decrease the number of errors, but I still get errors every time. Could it be the PSU not getting enough power to either the CPU, or the system in general?

Tomorrow I will put my Corsair in my brother's system and test at both 133 and 166MHz.

Why is my system able to run the RAM at 133MHz, but not 166MHz? CPU? PSU? Motherboard? Again, my motherboard supports my RAM, and my RAM is set at stock timings and stock frequency, which is 2-2-2-5 at 166MHz...

 

[arcenite]

Originally posted by: MasterFlash

Originally posted by: 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.

You meant changing the voltage from 1.65 to 1.77 right? If not, that's ridiculously high. It seems weird that you can even step to a x.77 V, but I've never had an epox board... You should check your CPU temp. It shouldn't be hitting 55C just booting up. The other thing that was mentioned was make sure you have latest BIOS, and maybe try reflashing even if you do.

He's talking about his memory voltage, not his CPU voltage.

Bill

 

[brigden]

I swear to god I'll smash my machine and buy a Dell...

 

[brigden]

I need help, guys.

 

[thirdlegstump]

That's weird. I had nearly the exact same setup. Same board and memory and was doing 200fsb at cas 3 and 166 at cas 2 and never had any stability problems. I was even using an XP 1700+ at fairly low voltages.
You may have a problematic board. Were you able to run the ram at 166cas2 with another CPU on the same board?

 

[WinkOsmosis]

INCREASE THE CAS LATENCY AND SEE IF IT WORKS

 

[lordtyranus2]

Nobody has suggested this, but I think it is a motherboard problem.

Judging from what you wrote, the CPU works fine when the RAM is at 133 Mhz? I think your mobo is having problems with the 166 mhz setting.

Your RAM should be running 2-2-2-5 at default voltage at 166 mhz. Try it out on a friends computer and see if it works. If it does not, try on friends computer with increased CAS settings at 166 mhz.

 

[brigden]

I did as you and many others have suggested and relaxed the memory timings. I relaxed them to 2.5-3-3-6. I managed to run Memtest through one pass at 166MHz at default voltage with no errors.

Why?

These DIMMs are designed to run at 2-2-2-5, and they have no problem doing that in my setup at 133MHz, so why do they crap out at 166MHz at those timings?

Is it the board? Is it the CPU?

 

[lordtyranus2]

These DIMMs are designed to run at 2-2-2-5, and they have no problem doing that in my setup at 133MHz, so why do they crap out at 166MHz at those timings?

Because apparently the RAM can't handle 166 Mhz at those timings for some reason, even though it should.

I am not sure whether that last post was in reply to me. Have you tried it out on another computer or at least another motherboard?

 

[0roo0roo]

Originally posted by: xenos500
turn the FSB on your AMD down to 100 and try again, if all your problems go away then your CPU is DOA. RMA it with your retailer or AMD direct. I have seen this 3 times with Athlon XPs once on a retail and twice on OEM.

bull, if he could run his ram 133 and cpu 166 asynch and be stable theres no way in hell its his cpu.

i bet its his old m/b. only way to know is to test that ram in someone elses pc.

 

[OptimusRhyme]

Thanks for the replies. I'm at my bro's now and we're going to pop the RAM in his machine shortly. I'll post the results in a few...

 

[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 some 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...

I had the same problem with some Corsair PC3200LL that wouldn't run at its rated speed. An RMA did the trick...

Dave

Edit: I checked corsair, and your memory is rated for 2,2,2,5 at 166MHz, so it sounds like it needs to be RMA'd...

 

[brigden]

Thanks Dave, I really appreciate all your help.

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...

 

[HGC]

When you solve the problem please let us know what it was. I am very curious.

 

[lordtyranus2]

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

If you are having the same error on 2 different mobos, I'd guess its the RAM.

But you got the right train of thought. RMA the RAM, and if it doesn't work still, RMA the mobo.

If there are problems with both, I'd really complain to your retailer.

 

[brigden]

So far I'm able to get the system stable with the RAM at 166MHz and timings of 2-3-3-5.

Perplexing...

 

[lordtyranus2]

Quite perplexing.

Unless you are satisfied with those timings, I suggest RMA ASAP.