Hi, I have been having problems with the G.SKILL Ripjaws Series 4GB (2 x 2GB) DDR3 2000 (PC3 16000).
First, here are my specs.
Windows 7 64-bit (Nothing overclocked)
Motherboard: XFX nForce 790I Ultra SLI http://www.newegg.com/Product/Produc...-009-_-Product
RAM: Crucial Ballistix 2GB (2 x 1GB) DDR3 1800 (PC3 14400) http://www.newegg.com/Product/Produc...82E16820148223
Video Card: NVIDIA 8800GTS 512MB http://www.newegg.com/Product/Produc...82E16814133215
Processor: Intel Quad Core Q6600 http://www.newegg.com/product/produc...82e16819115017
So, it all started when I replaced my old RAM with my new RAM. I didn't change anything in the bios, so it was being under clocked at 1333mhz. Everything was fine until I started playing MW2. I turned up all the graphics, and thats when everything started glitching out. It froze and crashed, saying that my Display Kernel Driver 195 has stopped responding but has successfully recovered. Then the desktop was glitchy. First, let me tell you that it isn't the drivers fault, i tried newer and earlier versions, and the problem persisted. Then I went into the bios, and changed it from 1333mhz to 2000mhz, and set the timings right (9-9-9-27 2T), the voltage (1.65V), and the problem was still there. When I put my old RAM back in, the problem went away. It does say on my motherboard that it can support 2000mhz with EPP 2 memory. It also says "DDR3 2000(OC)/1800(OC)/1333", so do I need to overclock it somehow? No matter how I set up the ram, the issue still shows. I have updated my video card driver. Also, in the beginning one of the 2 sticks were bad, so I had to RMA it and get a new pack, which is this pack. I have memtested the new RAM separately and the RAM DOES work. No errors. I had to run it in 1333 mode in order to memtest it, 2000 freezes for me. My old ram does have EPP 2.0, so all I have to do is select Auto under EPP 2.0, and it does it all for me.
Here is a CPUZ pic of the new RAM installed when I changed the timings.
The glitch usually happens when most of the RAM is being used. It freezes and glitches the game until it bsod's, the game crashes, I minimize it and the video driver recovers and everything is back to normal, or I minimize it and the video driver says it recovers but doesn't causing graphical issues on my desktop until i restart. I have tried this on multiple games and if the graphics are intense enough, the error will occur. Also screws up on Mark3D, videos, and web browsing.
The last thing I have done is update my BIOS driver to P09 (Latest Driver). The new RAM was installed at the time. When I tried loading windows 7 after that, it failed to, just leaving me at the Loading Windows screen, the animation moving still. I under clocked the RAM and no matter what i did, I couldn't launch Windows 7. I put my old RAM in and the new RAM out, EPP 2.0 Auto, and Windows 7 loaded. After memtesting the new RAM again, this time separately and at the speed 1333, it passed, and windows 7 did load after that with the RAM.
Does my motherboard fully support this RAM? If so, what exactly do I do that I haven't done that will fix it!
Thanks,
JWH
First, here are my specs.
Windows 7 64-bit (Nothing overclocked)
Motherboard: XFX nForce 790I Ultra SLI http://www.newegg.com/Product/Produc...-009-_-Product
RAM: Crucial Ballistix 2GB (2 x 1GB) DDR3 1800 (PC3 14400) http://www.newegg.com/Product/Produc...82E16820148223
Video Card: NVIDIA 8800GTS 512MB http://www.newegg.com/Product/Produc...82E16814133215
Processor: Intel Quad Core Q6600 http://www.newegg.com/product/produc...82e16819115017
So, it all started when I replaced my old RAM with my new RAM. I didn't change anything in the bios, so it was being under clocked at 1333mhz. Everything was fine until I started playing MW2. I turned up all the graphics, and thats when everything started glitching out. It froze and crashed, saying that my Display Kernel Driver 195 has stopped responding but has successfully recovered. Then the desktop was glitchy. First, let me tell you that it isn't the drivers fault, i tried newer and earlier versions, and the problem persisted. Then I went into the bios, and changed it from 1333mhz to 2000mhz, and set the timings right (9-9-9-27 2T), the voltage (1.65V), and the problem was still there. When I put my old RAM back in, the problem went away. It does say on my motherboard that it can support 2000mhz with EPP 2 memory. It also says "DDR3 2000(OC)/1800(OC)/1333", so do I need to overclock it somehow? No matter how I set up the ram, the issue still shows. I have updated my video card driver. Also, in the beginning one of the 2 sticks were bad, so I had to RMA it and get a new pack, which is this pack. I have memtested the new RAM separately and the RAM DOES work. No errors. I had to run it in 1333 mode in order to memtest it, 2000 freezes for me. My old ram does have EPP 2.0, so all I have to do is select Auto under EPP 2.0, and it does it all for me.
Here is a CPUZ pic of the new RAM installed when I changed the timings.
The glitch usually happens when most of the RAM is being used. It freezes and glitches the game until it bsod's, the game crashes, I minimize it and the video driver recovers and everything is back to normal, or I minimize it and the video driver says it recovers but doesn't causing graphical issues on my desktop until i restart. I have tried this on multiple games and if the graphics are intense enough, the error will occur. Also screws up on Mark3D, videos, and web browsing.
The last thing I have done is update my BIOS driver to P09 (Latest Driver). The new RAM was installed at the time. When I tried loading windows 7 after that, it failed to, just leaving me at the Loading Windows screen, the animation moving still. I under clocked the RAM and no matter what i did, I couldn't launch Windows 7. I put my old RAM in and the new RAM out, EPP 2.0 Auto, and Windows 7 loaded. After memtesting the new RAM again, this time separately and at the speed 1333, it passed, and windows 7 did load after that with the RAM.
Does my motherboard fully support this RAM? If so, what exactly do I do that I haven't done that will fix it!
Thanks,
JWH
Comment