Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
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.
Information
Errors are sometimes found after 8 passes.
Tip
Do this test overnight, before going to bed.
[CODE
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\USER\Downloads\SF_29-01-2014\SF_29-01-2014\012914-29625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c92e90
Debug session time: Wed Jan 29 15:21:49.775 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:04.119
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 6db2a001, 0, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000006db2a001
Arg3: 0000000000000000
Arg4: fffff70001080000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41284
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002b24767 to fffff80002acd640
STACK_TEXT:
fffff880`07846938 fffff800`02b24767 : 00000000`0000001a 00000000`00041284 00000000`6db2a001 00000000`00000000 : nt!KeBugCheckEx
fffff880`07846940 fffff800`02b0256a : 38c00001`9890d025 fffffa80`09cb55f0 00000000`00000011 fffff8a0`030eac08 : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`07846980 fffff800`02a99141 : 00000000`00000001 fffffa80`0b2db550 00000000`00000000 38c00001`9890d025 : nt!MiGetPageProtection+0xaa
fffff880`078469c0 fffff800`02a98dda : fffffa80`09cb55f0 fffffa80`0b2d1960 fffffa80`0b2d1960 00000000`6db2a000 : nt!MiQueryAddressState+0x2b1
fffff880`07846a10 fffff800`02da7cb4 : 00000000`00000020 00000000`6db2b000 fffffa80`09cb55f0 fffff780`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`07846a80 fffff800`02acc8d3 : ffffffff`ffffffff fffffa80`0b2db550 00000000`0042e9b8 00000000`001be128 : nt!NtQueryVirtualMemory+0x382
fffff880`07846b70 00000000`770e154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001be108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770e154a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`02b24767 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ac3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
Followup: MachineOwner
---------
][/CODE]
