flyingtm Posted January 19, 2007 Share Posted January 19, 2007 Hello, I've been having a problem lately. I've been having a problem more recently that has been causing my computer to reset itself or give me the blue screen of death with a corresponding error of PFN_LIST_CORRUPT. When I first started having the problems I went through and flashed the Bios on my Asus P5B-E to the current version that is out now. Still my problems only got worse. I was suspicious of the RAM being bad, but didn't really pay attention because the RAM was from corsair. Further testing proved that one of the two sticks of RAM was bad. I have a total of 4 sticks of XMS2 ram from you guys, three of them do not pull any errors in the Microsoft Memory diagnostic but the fourth one did pull errors in the program. Ram that I have: (that doesn't pull an error) Corsair 2x(CM2x512-5400C4) Corsair 1x(CM2x1024-5400C4) (faulty stick) Corsair 1x(CM2x1024-5400C4) The system Asus P5B-E Mobo Intel E6600 Western Digital and Seagate Baracude set to Raid0 Western Digital 250gb XFX 7900GT Enermax 480W PSU Two DVD Burners Note: All drivers are up to date, firmware on both DVD burners is up to date also. I have taken all steps toward finding a solution, all that I see now is a replacement. Thanks, Tim Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted January 19, 2007 Corsair Employees Share Posted January 19, 2007 Please make sure that you have the latest bios and then load setup defaults and set the Dim Voltage to 2.1 volts and then set the timings manually to the tested settings for the specific module you have, and then test the module/modules one at a time with http://www.memtest.org! If you still get errors, please follow the link in my signature “I think I have a bad part!” and we will be happy to replace them or it! However, if you get errors with both modules that would suggest some other problem and I would test them in another system or MB to be sure. In addition, with this MB you have to disable legacy USB in the bios when running any memory test. If you have done this and just that one module is failing I would suggest we get that set replaced. Link to comment Share on other sites More sharing options...
flyingtm Posted January 20, 2007 Author Share Posted January 20, 2007 The Bios in my computer is fully up to date. Every driver in my system is up to date. The only downside to this motherboard is that you cannot tweak the settings for RAM. I guess it does it already for you, because I've picked through all parts of the bios settings and haven't found anything. Since running the Microsoft memory tester I have had a few errors come up in Memtest, once with the faulty stick and then tested the other with it and received the same errors. I will try and find someone with a computer that I can put this ram into and test. Note: Since I have taken out the two gig (with the one being bad) I haven't had any errors in the games I play, a windows crash, or a reboot. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted January 22, 2007 Corsair Employees Share Posted January 22, 2007 Let's get them replaced, please use the On Line RMA Request Form and we will be happy to replace them or it. Link to comment Share on other sites More sharing options...
flyingtm Posted January 27, 2007 Author Share Posted January 27, 2007 I'm having a problem RMAing the ram. I have not heard a response from anyone. I have sent two RMA request (one being two days ago and the other 4). It says it should take 24 hours at the max. Why no email back to me with a RMA number? Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted January 27, 2007 Corsair Employees Share Posted January 27, 2007 Please either call our customer service at 888-222-4346 and dial "0" or follow the link in my signature "If you have submitted the RMA using the on line form and have not got a reply!" Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.