2 sets of identical RAM seem to not work together?

[Joshyy]

So I've had 8GB (2x 4GB) of G.Skill Ripjaws RAM in my system for about a year now and I got another 8GB of the exact same RAM in December and ever since then I've been getting BSOD's every couple of hours with all 4 DIMMs installed - However if I use just use either the 2 old sticks or the 2 new sticks it runs fine, I don't think it's a compatability issue as all the memory is identical (Naming - Sticker information - AMD overdrive gives the same name), I'm sort of leaning towards an issue with the motherboard maybe? It's all really confusing and none of the DIMMs give errors in Memtest86+

Any help would be really appreciated.

 

[Golden]

Hi,

There are two possibilities:

1. Defective RAM chips
2. Defective RAM slots on the motherboard

How long did you run MemTest86+ for? We recommend a minimum of 7 passes, which is usually an overnight job of several hours.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Upload your BSOD dmp files here, and we'll take a look:

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Regards,
Golden

 

[kbrady1979]

RAM is probably the most fickle piece of hardware in your PC. That is the reason why we always recommend buying a full kit, instead of buying a set and then later on buying another set...less chance of this happening. It's not your fault, I'm not saying that, but it does throw an extra variable in when the RAM isn't a matched set. Anyway, to get to the root of your problem, run Memtest86+ on the original two sticks for 7 passes like Golden said, then swap that out and replace it with the new kit in the same slots, rinse repeat. If NONE of the testing throws an error, you need to test each stick individually, in EACH slot. Goal is to isolate either a bad RAM stick or a bad slot. I've seen cases of all the RAM testing fine through individual/dual setups but when you put all 4 sticks in they throw an error. Let us know what you find.

 

[Joshyy]

I did a disk cleanup a couple of hours ago so there's only 2 BSOD's but it's all attached below, If the BSOD's done give any info I'll try you're approach Kbrady

 

[Golden]

How long did you run MemTest for?

 

[Joshyy]

I ran Memtest on the 4 DIMMs over night (Just let it run overnight) no errors

 

[Golden]

1. Download and save this tool to your desktop:
http://go.microsoft.com/fwlink/?linkid=52012

2. Run the tool, and then click 'Copy' - ignore any errors if they appear

3. Use CTRL+V to paste the unedited results of the validation tool here in your next reply

 

[Joshyy]

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: Censored as this is un-needed
Windows Product Key Hash: Censored as this is un-needed
Windows Product ID: Censored as this is un-needed
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {42AA1FE1-416D-4981-BE42-277EB1E32BE6}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\Josh\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{42AA1FE1-416D-4981-BE42-277EB1E32BE6}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-33KXK</PKey><PID>00359-892-0893951-85040</PID><PIDType>5</PIDType><SID>S-1-5-21-286029009-3228617082-3475973654</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1701 </Version><SMBIOSVersion major="2" minor="5"/><Date>20121114000000.000000+000</Date></BIOS><HWID>23C10500018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: 2e7d060d-4714-40f2-9896-1e4f15b612ad
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00170-892-089395-00-2057-7601.0000-2122012
Installation ID: 156649300010922959973050456748116135435900439124811350
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: 33KXK
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 27/01/2013 00:16:08

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 11:8:2012 22:35
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OgAAAAAABAABAAEAAAAEAAAABAABAAEAln3elVT59JZIxPTjgA4MN2I9PpOYVD2InqL05rI/QA2OLg==

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC 111412 APIC1033
FACP 111412 FACP1033
HPET 111412 OEMHPET
MCFG 111412 OEMMCFG
OEMB 111412 OEMB1033
SSDT A M I POWERNOW

 

[Golden]

I don't see any issues with the validation, but in future when requested don't assume we don't need that information, and then censor/edit it out. The report does not contain any information that can be stolen and used.

I'll have a look at the dmp files shortly.

 

[Golden]

******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff90041f3d578, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600015cb41, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f9100
 fffff90041f3d578 

FAULTING_IP: 
win32k!ValidateHwnd+f1
fffff960`0015cb41 498b9058010000  mov     rdx,qword ptr [r8+158h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

[B][COLOR="Red"]BUGCHECK_STR:  0x50[/COLOR][/B]

PROCESS_NAME:  ts3client_win6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!ValidateHwnd+f1
fffff960`0015cb41 498b9058010000  mov     rdx,qword ptr [r8+158h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!ValidateHwnd+f1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6

FAILURE_BUCKET_ID:  X64_0x50_win32k!ValidateHwnd+f1

BUCKET_ID:  X64_0x50_win32k!ValidateHwnd+f1

Followup: MachineOwner

Bugcheck 0x50 - this is most definitely memory-related.

Questions:

1. What anti-virus software is currently installed?

2. Are you overclocking any RAM, or using the stock settings?

3. Have you had any disk errors recently?

 

[Joshyy]

Hi there Golden

I use Avast! Free antivirus

I don't overclock anything in my system and I also have not had any disk errors


I ran some testing last night using Memtest86+ and these were the results I got


All 4 DIMMs installed - 88 errors test 5

2 new DIMMs installed in slot 2 and 4 - 0 errors

I'm going to be testing those 2 DIMMs in slot 1 and 3 tonight too see what happens.

 

[Joshyy]

I've just had a look in the BIOS at the timings and it's running the memory at 11-11-11-28, However the memory's rated at 9-9-9-24, Would having the CAS latencys higher cause instability? Should I manually set the memory to 9-9-9-24?