I run an Athlon64 3200+ CPU on an MSI K8N Neo2 nforce3 motherboard with 1024mb of corsair TwinX 4400c25pt DDR550 RAM.
I do a lot of video editing on my system and handling large files sometimes causes CRC errors in WinRAR. I have a large 8gb file that almost always causes errors when decompressing unless I use only 1 stick of RAM, however the file always works fine on an older nforce2 athlon 3200+ dual channel system.
I have been waiting for a new bios from MSI which officially supports the E3 (venice) stepping of the Athlon64 in case that might help but now that its been released (v1.90) there has been no difference in stability.
I have tried running memtest86+ and Prime95 memory and CPU stress tests with new installations of windows 2000 pro and Windows XP pro as well as hard drive tests, changing all the IDE & SATA cables and changing the power supply from a 550W to a 500W one from another PC. I have found that if I use only 1 stick of DDR ram, so the athlon64 uses only a single channel memory interface, the errors disappear.
When it comes to overclocking there is some odd behaviour too. Memtest takes these sticks up to 293Mhz and 297Mhz each at 2.5-4-4-10 @ 2.8v before errors creep in. Dual channel works up to about 281Mhz. Using the 166Mhz divider the HT bus goes up to about 315Mhz. With 1 stick of RAM in single channel, the CPU is stable in Prime95 at 10x264Mhz (2640Mhz) or 9x293Mhz (2637Mhz) with 1.5v. Dual channel seems stable at 10x251Mhz (2510MHz) but, strangely, only up to 9x266 (2397Mhz) in Prime95 but the WinRAR problem always occurs until I wind down to 2230Mhz (10x223Mhz) where there's a better, but not 100%, chance of it succeeding in extracting the large file.
I have been struggling with this issue for a few weeks now and I'm starting to suspect that the onboard memory controller on this particular CPU may not be working correctly... or is it the Motherboard? ...Or the RAM? The socket 939 Athlon64 should work perfectly well with the dual channel certified corsair memory but i have been reduced to only using 512mb of the 1024mb I purchased to ensure error-free operation.
Anyone have any thoughts on what the problem could be?
I do a lot of video editing on my system and handling large files sometimes causes CRC errors in WinRAR. I have a large 8gb file that almost always causes errors when decompressing unless I use only 1 stick of RAM, however the file always works fine on an older nforce2 athlon 3200+ dual channel system.
I have been waiting for a new bios from MSI which officially supports the E3 (venice) stepping of the Athlon64 in case that might help but now that its been released (v1.90) there has been no difference in stability.
I have tried running memtest86+ and Prime95 memory and CPU stress tests with new installations of windows 2000 pro and Windows XP pro as well as hard drive tests, changing all the IDE & SATA cables and changing the power supply from a 550W to a 500W one from another PC. I have found that if I use only 1 stick of DDR ram, so the athlon64 uses only a single channel memory interface, the errors disappear.
When it comes to overclocking there is some odd behaviour too. Memtest takes these sticks up to 293Mhz and 297Mhz each at 2.5-4-4-10 @ 2.8v before errors creep in. Dual channel works up to about 281Mhz. Using the 166Mhz divider the HT bus goes up to about 315Mhz. With 1 stick of RAM in single channel, the CPU is stable in Prime95 at 10x264Mhz (2640Mhz) or 9x293Mhz (2637Mhz) with 1.5v. Dual channel seems stable at 10x251Mhz (2510MHz) but, strangely, only up to 9x266 (2397Mhz) in Prime95 but the WinRAR problem always occurs until I wind down to 2230Mhz (10x223Mhz) where there's a better, but not 100%, chance of it succeeding in extracting the large file.
I have been struggling with this issue for a few weeks now and I'm starting to suspect that the onboard memory controller on this particular CPU may not be working correctly... or is it the Motherboard? ...Or the RAM? The socket 939 Athlon64 should work perfectly well with the dual channel certified corsair memory but i have been reduced to only using 512mb of the 1024mb I purchased to ensure error-free operation.
Anyone have any thoughts on what the problem could be?