New RAM causing system instability

[burning_phoneix]

I just recently upgraded my PC with a new GPU (HD7870) new RAM (2x4GB 1600mhz DDR3) and a new Hard Disk (1TB WD Blue) and have been having some trouble.

The system was VERY wonky when I first got it and would repeatedly crash and eventually fail to boot up. I found that the problem was the RAM. The motherboard does not support 1600Mhz so it automatically sets it to 1333 but does not readjust the voltage or the RAM timings so I manually adjusted them (1.65v and 9-9-9-27 respectively).

While the system is now stable, whenever I play any videogame for about 10 minutes, the game will crash to desktop. (I have tried this on multiple games).

I've already wiped all my drivers using Driver sweeper and reinstalled the latest AMD drivers so I don't think it's the GPU but I can't seem to stop the problem and even Firefox crashes now from time to time.

Oh and my mobo is a Gigabyte GA-880GM-UD2H AM3 AMD 880G HDMI Micro ATX

 

[mauller07]

try using just one stick of the ram at a time, it could be that one if faulty or they do not like playing together.

 

[Tradesman1]

Try raising the CPU/NB voltage + 0.07, it's the MC (memory controller) voltage

 

[burning_phoneix]

My BIOS had the option to move up the CPU/NB VID voltage so I assumed that was it. I can only move it up in increments so I did +0.075v and it's kinda gotten worse. Instead of a crash to desktop, I get a Blue screen and the system restarts.

Whocrashed puts up this crash report which is new to me:

On Thu 11/07/2013 11:44:11 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\071213-20701-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CF7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005759CF7, 0xFFFFF88005DEF6A8, 0xFFFFF88005DEEF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Tradesman1]

What CPU are you running?

 

[burning_phoneix]

It's an AMD Athlon II X4 640

 

[Tradesman1]

try the sticks at 1333 8-8-8-24, 2T - very few 640s can can carry 1600 sticks especially 2x4GB, generally want at least a 965 3C for 1600

 

[burning_phoneix]

Do I leave the CPU/NB voltage at +0.075v

 

[Tradesman1]

drop it to auto and see how 1333 does

 

[burning_phoneix]

I dropped the CPU/NB to Normal setting and tried the 8-8-8-24 2T settings but no dice. It caused a system crash.

Should I just drop these RAM sticks and buy new ones more compatible with my mobo+cpu? If so, what are some good 8GB ones?

 

[Tradesman1]

Try each stick by itself if each works by it's lonesome, then try together with the increased CPU/NB, let me know and I'll take a look at sticks for your combo , off hand would think Snipers in 1333 had good luck with them paired with your CPU

 

[burning_phoneix]

I'll try each stick by itself but it wouldn't hurt for any suggestions because if it fails, I'm going to get some new RAM straight away and it would help if I had a list already on hand.

 

[Tradesman1]

With your CPU I'd look at 1333 prob 9-9-9-24-27, would suggest the GSKill Snipers as they work extremely well with AMD

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231417

if not them then one of the Ripjaws line, same freq/timings

 

[burning_phoneix]

Okay I tested them out. With normal CPU/NB voltage, each one ALONE works excellently! But put them together and they start getting wonkey. If set the CPU/NB voltage to auto I get a whole system crash. If I set the CPU voltage to +0.075v the program crashes but not the system.

I guess I'll give up at this point and pick up some other RAM. Thanks for all your help Tradesman! I'll report how it goes with the GSkill

 

[mauller07]

sounds like the ram is faulty in the end if lone sticks work, sounds like they are not matched pairs.