Sunef Posted October 30, 2004 Share Posted October 30, 2004 I bought two 512Mb modules about 24 months ago. Over the past two years I've had trouble when entering bios to change settings. Once in a while when changing bios settings, the result would be a blank screen after saving and restarting. It could be something as ordinary as changing boot devices, nothing related to overclocking or tweaking memory. In the end I simply let the bios settings alone and left them at default. About one month ago the screen was blank again when I started the computer one day. Reseting bios didnt help, nothing did. So I figured, because of the bios problems, that the motherboard was at fault. I returned the motherboard to the reseller and got it back 2 weeks later thouroughly tested and with no errors found. I reassembled the computer and the screen was still blank. So, I decided to buy a new motherboard and CPU, and got it a few days ago. I assembled it and the screen was still blank. Now I was beginning to suspect something different, so I brought my two computers to a friend to try the parts on his computer. On all three machines the screen is blank with either of the Corsair memory modules. Using my friends DDR on any of the setups results in flawless boot and behavior. So my conclusion is that the Corsair RAM is at fault. Here are the stats: Memory: 2 modules of Corsair CMX512-3200C2 XMS3202v1.1 Computer 1: Asus A7N8X Deluxe Atlon XP 2200+ Computer 2: Asus K8N-E Deluxe Athlon 64 3000+ Computer 3: Motherboard unknown Intel P4 2.8 Ghz Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 1, 2004 Corsair Employees Share Posted November 1, 2004 Please make sure that you have the same revision of memory module in your system i.e. V1.1, V2.1, etc... if you do not have the latest BIOS please set the settings at 2.5/3/3/7 but if you do then please make sure that you have the latest BIOS for your MB and load Setup/Optimized default settings, and try the following BIOS settings; TwinX1024 or TwinX512-3200C2 (A7N8X DELUXE) CPU Freq: 133 MHz (266 FSB) System Performance: User Define Memory Frequency: 100% Resulting Frequency: 133 MHz (266 FSB) Memory Timing: User Define SDRAM CAS Latency: 2.5T SDRAM RAS to CAS Delay (tRCD): 3T SDRAM Row Precharge (tRP): 3T SDRAM Active to Precharge Delay (tRAS): 6T DDR Reference Voltage: 2.7 Volts AGP Voltage: Default *unless you have ATI 9200 or 9600 then 1.6 Volts suggested!* OR TwinX512 or TwinX1024-3200C2 (K8N-E Deluxe) Advanced Chipset: Memclock Mode: Limit Memclock Value: 2:1 (DDR400) Bank Interleaving: 4/Enabled Burst Lenght: 4 SDRAM CAS Latency: 2.5T SDRAM RAS to CAS Delay (tRCD): 3T SDRAM Active to Precharge Delay (tRAS): 6T SDRAM Row Precharge (tRP): 3T Hypertransport: 4X Jumper Free/Frequency Voltage Control: Spread Spectrum: Enabled CPU FSB Clock: 200 DDR Voltage: 2.7/2.75 Volts AGP Voltage: Default *unless you have ATI 9200 or 9600 then 1.6 Volts suggested!* All other settings are motherboards defaults Then please test them one at a time with http://www.memtest.org and let’s make sure it's not some other issue! I would run the test for at least 2-3 passes to be sure! Link to comment Share on other sites More sharing options...
Sunef Posted November 1, 2004 Author Share Posted November 1, 2004 Thank you for your reply. Both modules were bought at the same time and are both revision 1.1. I can not test any bios settings whatsoever because the screen is blank at startup regardless of the computer I am using. I never see any boot up screen, the monitor doesnt even switch on. When using the Asus motherboards I get no warning message, but on the computer with the P4 CPU I get a long beep signaling a RAM error. It has been like this on and of since I bought the modules, but I've always been able to boot after a few retries or after reseting the BIOS. Now however, I havent been able to boot at all. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 1, 2004 Corsair Employees Share Posted November 1, 2004 I have no problem replacing the memory modules for you, but I will highly recommend you to test these modules in a different system if possible or to a friend system; since I believe that the problem is not coming from the memory modules, reason being is that no manufacturer can produce two products at the same time that will be bad and especially & knowing that our company test our modules twice at it's rated speed in a MB before even shipping it out to our customers (resellers/distributors.) So if you can please do so, just to make sure it is not some other issue on your system. Link to comment Share on other sites More sharing options...
Sunef Posted November 1, 2004 Author Share Posted November 1, 2004 I am also puzzled that two modules fails at the same time. I will however test them in a fourth and maybee fifth system and report back here tomorrow. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 2, 2004 Corsair Employees Share Posted November 2, 2004 Please make sure that you test it on a known good working system, let us know how you make out. Link to comment Share on other sites More sharing options...
Sunef Posted November 4, 2004 Author Share Posted November 4, 2004 I have now tried my two Corsair modules on a fourth system. The system is as follows: Athlon 2400+ Abit NF7-S2G I tried 6 memory modules (including my Corsair modules) individually. The other 4 modules where all lower performance modules from Viking memories and TwinMOS. I tried the modules one by one, and my two Corsair modules both failed in the way described above while the other 4 worked flawlessly. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 4, 2004 Corsair Employees Share Posted November 4, 2004 Please follow the link in my signature “I think I have a bad part!” and we will be happy to replace them or it! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.