Random BSODs when using 2 sticks of RAM.

Stokie1996 · 25 Nov 2012

For the past few weeks I've been having problems running my PC with two sticks of RAM, which came with the PC that I purchased back in September, they're both identical sticks of 4gb. I can run on a single stick, but never on both at once, otherwise I'll get a random BSOD, the type of BSOD varies and the only one I've noted is 'APC_INDEX_MISMATCH', which occured on the BSOD before last. I've use MemTest with both sticks in and individually and get no errors.

One thing to note is that in the SystemInfo file it says that I have a total physical memory of 4gb, that's because I'm running on 4gb now in order to create this thread, I only have problems on 8gb as previously stated.

I'm don't know a lot when it comes to these type of errors, and I don't know a lot about this site, so I apologize if I've made a mistake in my post or haven't included enough information, but I'll do my best to help you understand my problem.

Specifications:
AMD Phenom II x4 965 (@3.40GHz)
AMD Radeon HD 7770 (1gb)
2 x 4gb Mushkin Essentials (Running on 1 stick to prevent BSOD)
500gb SATA II HDD

koolkat77 · 26 Nov 2012

Welcome to SevenForums.

RECOMMENDATIONS:

System Optimisers

Please remove the following software

Code:

Start Menu\Programs\Advanced SystemCare 6	Public:Start Menu\Programs\Advanced SystemCare 6	Public

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner but make sure you back up the registry before making letting ccleaner delete anything.

Uninstall AVG, it contributes in BSOD-s:

Code:

Start Menu\Programs\AVG	Public:Start Menu\Programs\AVG	Public

AVG | Download tools and utilities

Recommended antivirus program for Windows 7 based on stability compared to others:-

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

Disk Check

REINSTALL VIDEO DRIVERS:
Click on the Start

► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATI and restart the computer if required. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper.

Use this link to get latest drivers:

AMD Driver Autodetect

Let us know if that helps.

Summary:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03053670
Debug session time: Mon Nov 26 04:18:08.995 2012 (UTC + 6:00)
System Uptime: 0 days 0:03:32.556
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002e85ec5, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002e85ec5, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bd100
GetUlongFromAddress: unable to read from fffff800030bd1c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e85ec5 498b08          mov     rcx,qword ptr [r8]

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ed8a88 to fffff80002e8dfc0

STACK_TEXT:  
fffff880`09394fa8 fffff800`02ed8a88 : 00000000`0000001e ffffffff`c0000005 fffff800`02e85ec5 00000000`00000000 : nt!KeBugCheckEx
fffff880`09394fb0 fffff800`02e8d642 : fffff880`09395788 00000000`00000002 fffff880`09395830 fffffa80`08f6e9b8 : nt! ?? ::FNODOBFM::`string'+0x487ad
fffff880`09395650 fffff800`02e8bf4a : fffffa80`01a37240 fffff800`02eb35b0 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`09395830 fffff800`02e85ec5 : 00000000`00000002 fffff800`02e9da6d 80000001`478d6867 fffff880`09395a40 : nt!KiGeneralProtectionFault+0x10a
fffff880`093959c0 fffff800`02e9da6d : 80000001`478d6867 fffff880`09395a40 fffff700`01080000 fffffa80`08f6e9b8 : nt!ExpInterlockedPopEntrySListFault16
fffff880`093959d0 fffff800`02e9a7ce : 00000000`00000001 00000000`0be6f000 fffff880`09395c20 fffff680`0005f378 : nt!MiResolveDemandZeroFault+0x14d
fffff880`09395ac0 fffff800`02e8c0ee : 00000000`00000001 00000000`0be6f000 fffff880`09395b01 00000000`011d0000 : nt!MmAccessFault+0x5de
fffff880`09395c20 00000000`77ccdf85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`004ae61c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ccdf85


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e85ec5 498b08          mov     rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16+0

Followup: MachineOwner
---------

Stokie1996 · 26 Nov 2012

Sorry for the slow reply, some of these things took hours to complete, for some reason I couldn't find anything AMD/ATI related to uninstall, I'm just installing MSE and then I'll install the other stick of RAM and then reboot. Is MSE the best software available? Because I've always trusted names that I know more, such as AVG. I'll post back with results in an hour or so, thanks.

Stokie1996 · 26 Nov 2012

I got another BSOD after about 5 minutes of running on 8gb RAM again, so I've attached the updated diagnostics file to this. Thanks in advance!

koolkat77 · 26 Nov 2012

MSE and MBAM work great, but you can use Avast! Antivirus (Free) instead of MSE.

The bug check is same, does not give a probable cause. You should proceed with memtest.

Stokie1996 · 27 Nov 2012

koolkat77 said:

MSE and MBAM work great, but you can use Avast! Antivirus (Free) instead of MSE.

The bug check is same, does not give a probable cause. You should proceed with memtest.

I've already done so, I tried last week and got no errors, I'll try again later tonight.

koolkat77 · 27 Nov 2012

Follow the way mentioned earlier. Sometimes memtest may find no errors at all, that time you should test them yourself in different slots of the motherboard and see how the computer works. (Not memtest, just manually by moving sticks here & there and see if the computer crashes/blue screens)

Stokie1996 · 27 Nov 2012

Alright thanks, but I only have 2 slots. If it's one of the slots then I assume the motherboard is having problems?

koolkat77 · 27 Nov 2012

Stokie1996 said:

Alright thanks, but I only have 2 slots. If it's one of the slots then I assume the motherboard is having problems?

Probably this will help?
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.

Do this test overnight, before going to bed.