jackanapes Posted November 3, 2004 Share Posted November 3, 2004 I am sure i have a bad module. My WINXP system was having blue screens about twice daily, as well as more frequent fatal application errors. multiple reformats didnt help. I suspected the mobo but all problems vanished when i removed one of the ram modules. i have 2 identical 512MB pc3200 cas 2.5 value select modules. with the good one in the system is stable, when i take it out and put in only the defective module, i either get a blue screen before i load windows desktop, or i will get frequent (every 2 minutes) application fatal errors followed eventually by a blue screen. replacing that module with the good one immediately cures the problem and the system works stably. i used the same RAM slot for the testing to make sure my motherboard doesn't have a faulty slot. thanks Link to comment Share on other sites More sharing options...
jackanapes Posted November 3, 2004 Author Share Posted November 3, 2004 ok corsair support you are on the clock :laughing: 24 hour countdown initiated. btw, i think messageboard posting is a great way to do tech support :): Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 3, 2004 Corsair Employees Share Posted November 3, 2004 Can you tell me the exact model# of your memory module and the make and model of MB you have along with the CPU speed and it’s FSB as well? In addition, please tell me if you have the latest BIOS installed on your system and the bios settings you have set for both CPU and memory and any performance settings that you may have set? Link to comment Share on other sites More sharing options...
jackanapes Posted November 3, 2004 Author Share Posted November 3, 2004 SHUTTLE an35n ultra 400 latest bios. umm i think its revision "s00r." corsair module VS512MB400 LOT#0437019-0 the cpu speed is 1.8 GHz, it's a mobile athlon 2400+. ram timings are at the default 8-3-3-2.5 at 200MHz. FSB/RAM is 1:1 ratio. 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 make sure that you have the latest BIOS for your MB and use this setting as a reference: VS512MB400 CPU Freq: 133 MHz Dim Voltage: 2.7 Volts DRAM Clock: 133 MHz/1:1/100% SDRAM memory timing: Manual/User Define/Expert SDRAM CAS Latency: 2.5T SDRAM RAS to CAS Delay (tRCD): 3T SDRAM Row Precharge (tRP): 3T SDRAM Active to Precharge Delay (tRAS): 8T AGP Voltage: Default *unless you have ATI (9200 or 9600) or NVIDIA (5200 or 5700) then 1.6 Volts suggested!* 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...
jackanapes Posted November 5, 2004 Author Share Posted November 5, 2004 OK I will run memtest. i disabled the quick power on self test (post) in the bios to make it run a full ram check, and the bad module fails immediately, and the mobo bios says the ram is bad. the good stick passes that test fine. ill run ram test for further confirmation. Link to comment Share on other sites More sharing options...
jackanapes Posted November 5, 2004 Author Share Posted November 5, 2004 15 minutes of memtest yielded a whopping 73,000 errors. ill run it before i go to sleep to get a summary in the morning but right now i want to use the computer (with the good ram) for games and such :) Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 5, 2004 Corsair Employees Share Posted November 5, 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...
jackanapes Posted November 5, 2004 Author Share Posted November 5, 2004 thanks. btw, memtest racked up 493,000 errors over night :laughing: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.