Preacher_Man Posted October 25, 2007 Share Posted October 25, 2007 When I build my rig six months ago I put in 2 GB of TWIN2X2048-6400C4. The system was completely stable. About two weeks ago I bought two more GB of TWIN2X2048-6400C4 and the issues started. I initially though I had fixed them when I realized that 64 bit Vista needed to be patched to actually run 4 GB of memory properly. But it turns out that wasn't actually the end of my problems. OK here goes: before I added the 2 GB of new memory I could play Company of Heroes relatively problem free (it would crash once in a while). As soon as I added the new memory I started getting crashes in the game with the message: "Display driver nvlddmkm stopped responding, but has successfully recovered". Then my system would immediately blue screen and restart. I checked various support forums to see what it meant, and many said it was possibly due to faulty memory, but I also read that it is caused by using DX10 and turning it off will fix the problem. I wanted to eliminate the bad memory possibility, so I used Vista's memory testing programs to see if it would report a problem, and sure enough there was one. I managed to narrow it down to one 1 GB module (I made sure it wasn't just the slot the module was running in causing the problem by switching it around). The funny (or not so funny) thing is that it was one of my 6 month-old sticks, not one of my new ones. At this point I wanted to do some more testing, and here is where I get lost in what is going on. I had been running my memory at 5-5-5-18-2T (1.8v) when my windows memory test reported the problem. I bumped everything to 4-4-4-12-2T (2.1v) and the windows memory test no longer found any problems with the memory! :thinking: Now doing this did not solve my problem with COH :greencry:, the nvlddmkm problem still occurs, just now it doesn't make my system blue screen the game just crashes to the desktop and the screen flickers every few seconds, repeating the same message "Display driver nvlddmkm stopped responding, but has successfully recovered" :brick:. This all leads me to think it is actually just the game (or NVIDIA's drivers) causing the problem. But it makes me nervous that when I try to run my memory at 5-5-5-18-2T (1.8v) Windows Memory Diagnostic tool reports a problem with the same stick every time and the system blue screen when the nvlddmkm error occurs. Now I haven't yet had this problem playing any other games, but then again I haven't really been playing anything but COH since the problems started. So what should I do? RMA or keep playing for now until I can reproduce the issue in another game? Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted October 25, 2007 Corsair Employees Share Posted October 25, 2007 These modules are tested to run at 2.1 volts, and although they may seem stable at 1.8 volts, it is not uncommon that they would cause errors in memtest at 1.8 volts. Although NVXXXXX errors could be caused by faulty memory, since your memory is passing memtest, the error probably has to do with your chipset or video drivers. Link to comment Share on other sites More sharing options...
Preacher_Man Posted October 25, 2007 Author Share Posted October 25, 2007 These modules are tested to run at 2.1 volts, and although they may seem stable at 1.8 volts, it is not uncommon that they would cause errors in memtest at 1.8 volts. Although NVXXXXX errors could be caused by faulty memory, since your memory is passing memtest, the error probably has to do with your chipset or video drivers. Thanks! I appreciate your help! I will just leave the memory at 2.1v. :sunglasse Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted October 25, 2007 Corsair Employees Share Posted October 25, 2007 NP Please let us know if you have any more questions! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.