sylvan_elf Posted May 14, 2009 Share Posted May 14, 2009 I build this computer with a gigabyte MA770-UD3, with other parts listen in my specs. After about 3-4 weeks it started giving me IE7, Win Explorer and random crashes, blue screens of death, and various missing/corrupt files. I ran memtest, and it would say the memory was fine, but Windows mem tester said there was a hardware conflict. I checked the Gigabyte mobo and it didn't list this RAM as compatible. So I ordered a ASUS mobo (listed in my specs), and another pack of this Corsair Dominator RAM. Built the computer with them, leaving this pack of RAM out. Booted, reformatted and reinstalled Vista, running fine. I added the original sticks of RAM back in thinking it was the mobo that was causing it. About 4 weeks later it started all over again. Running memtest, and windows memory test, one test showed good, one test showed bad. I pulled the original set of RAM out and it is now running stable again. Leads me to think that the RAM is the problem. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted May 15, 2009 Corsair Employee Share Posted May 15, 2009 Did you test those modules by them selves one at a time to be sure one was failing and with 4 modules I would suggest setting the memory frequency at DDR667 and set the memory Voltage to 2.1 Volts and set the NB/MCH/SPP Voltage to +.2 Volts as well and test the system with http://www.memtest.org. In addition, with some MB's (Mostly ASUS) you have to disable legacy USB in the bios when running any memory test. Link to comment Share on other sites More sharing options...
sylvan_elf Posted May 17, 2009 Author Share Posted May 17, 2009 I changed BIOS to the parameters you suggested, and tested the 2 sticks I had installed, and ran memtest, it came back with over 200 fails. I turned the system off, removed 1 stck and started testing each piece 1 at a time, they all passed. I installed all 4 with same parameters, and tested with memtest, and passed. It doesn't appear to be the RAM, but 2 different mobos doesn;t seem likely to be the cause either. What can cause it to start developing problems when running for long periods of time, but when turning off for 30 secs, cause it to fix it? Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted May 18, 2009 Corsair Employee Share Posted May 18, 2009 How many modules are installed and what were the settings you had set for both CPU and memory? Link to comment Share on other sites More sharing options...
sylvan_elf Posted May 31, 2009 Author Share Posted May 31, 2009 DRAm timing 5-5-5-15 with 2T, 2.1V, tested individually, and with all 4 sticks. Individually tested fine (oddly), with all 4 sticks shows errors. Ran with speed settings at 667, and 800, same results. I had updated BIOS and for about a week the blue screens had stopped, but are back. Link to comment Share on other sites More sharing options...
Wired Posted May 31, 2009 Share Posted May 31, 2009 What's the version # of each pair? How To Read the Memory Label Link to comment Share on other sites More sharing options...
sylvan_elf Posted June 2, 2009 Author Share Posted June 2, 2009 All sticks are ver 2.1. Does the lot number matter as per channel? I am not certain, but I do think I had them installed in the corresponding channel. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted June 4, 2009 Corsair Employee Share Posted June 4, 2009 Yes the set that matches would need to be installed int he right slots so that set is in D/C with its matching pair mate. With 4 modules I would suggest setting the memory frequency at DDR667 or DDR800 and set the memory Voltage to 2.1 Volts and set the NB/MCH/SPP Voltage to +.2 Volts as well and test the system with http://www.memtest.org. In addition, with some MB's (Mostly ASUS) you have to disable legacy USB in the bios when running any memory test. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.