jodonnell Posted December 29, 2004 Share Posted December 29, 2004 I was running a matched pair of 512MB DDR400 CAS2 at its spec speed at with relaxed timings (3-3-3-8) on my system. I bought a new case, and after installing the system into the new case (which entailed an inadvertent BIOS flash,) I had problems running the system at 200MHz FSB. 200MHz caused severe instability and MemTest86 revealed two errors in one of my modules when running at DDR400. I downclocked to 380 and once again have 100% stability. Thinking perhaps it was an error running at specifically 400MHZ (since I am running a Mobile Barton on an NF7-S) I clocked to 398 but still had problems; 380 seems to work perfect however. I am running in single channel on an Abit NF7-S v2 with a Mobile Barton 2500+ running 190x12. The timings are currently set at 3-3-3-8 running 2.9V (just in case as I've heard the NF7 undervolts slightly.) CPU Interface is set to disabled, shadowing/caching is disabled, all other options are set for stability. I think one of the modules is simply failing so I'd like to try and RMA it. Link to comment Share on other sites More sharing options...
CMC_SAVAGE Posted December 29, 2004 Share Posted December 29, 2004 Before the transfer and BIOS flash, you had no problems? Link to comment Share on other sites More sharing options...
jodonnell Posted December 29, 2004 Author Share Posted December 29, 2004 Nope, none at all. Ran 200x12, folding 24/7 with total stability. Actually I forgot to mention earlier - it actually ran fine at 200x12 after the system transfer for a day. There were some issues owing to removing the floppy drive; but that was easily remedied. It ran fine for a little while, then I turned it off and went out of town for the weekend. When I came back, it would boot at 200FSB but die within 10 minutes in Windows, and eventually it degraded to blue screens on booting Windows. After lowering the FSB to 190 it worked fine. There weren't any storms or major power surges that I'm aware of though, and I am behind a surge protector; I think it's possible the RAM died over that weekend but I'm not sure how that would have happened, since it was left off the whole time. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted December 29, 2004 Corsair Employees Share Posted December 29, 2004 That might suggest some other issue, can you test the modules on another system with http://www.memtest.org to be sure? Link to comment Share on other sites More sharing options...
jodonnell Posted December 30, 2004 Author Share Posted December 30, 2004 I don't have access to an alternate system to test on; however, I was using the Memtest referenced in your link, on my system. I was running the RAM at specification, and other BIOS settings should not have interfered, as I was using the same settings as I had before moving the system to another box. Two errors occured on test 5 (block move) on one module. I would think thhe only possible causes are a) a dying RAM module, b) a faulty BIOS setting, or c) a dying PSU; and since the problem was resolved by lowering RAM clockspeed, I would assume the error comes from the RAM module. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted December 30, 2004 Corsair Employees Share Posted December 30, 2004 Well no not always, and failures in test 5 would suggest some other component is failing, IE: CPU or Chipset or you may have noisy power. I would try and load setup defaults and set the settings listed bellow and test the modules one up. If you have a bad module it will fail no matter what settings you have set. CPU Freq: 166 MHz Memory Frequency: 100% Dim Voltage to 2.7 Volts Resulting Frequency: 166MHz SDRAM CAS Latency: 2.5T SDRAM RAS to CAS Delay (tRCD): 3T SDRAM Row Precharge (tRP): 3T SDRAM Active to Precharge Delay (tRAS): 6T Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.