New BSOD I Haven't Seen Before, Need Help Diagnosing

Just got a BSOD that I haven't seen before. The minidump file is attached. Thanks for any help in diagnosing the issue.

Windows 7 Home Premium x86 64-bit installed on built desktop setup
Full retail purchased from retailer, says OEM System Builder Pack on the box
System is brand new built just a month ago, OS installation is fresh and is my third one trying to fix BSOD issues

josh99ta said:

Just got a BSOD that I haven't seen before. The minidump file is attached. Thanks for any help in diagnosing the issue.

Windows 7 Home Premium x86 64-bit installed on built desktop setup
Full retail purchased from retailer, says OEM System Builder Pack on the box
System is brand new built just a month ago, OS installation is fresh and is my third one trying to fix BSOD issues

This crash was caused by memory corruption I would

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Good luck

Ken J




Analysis

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\091310-22666-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Mon Sep 13 20:10:21.875 2010 (GMT-4)
System Uptime: 0 days 8:47:20.435
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

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

1: 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: fffff80002afab7f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02afab7f f00fba6b1000    lock bts dword ptr [rbx+10h],0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0d0e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  lightroom.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88008b75708 -- (.exr 0xfffff88008b75708)
ExceptionAddress: fffff80002afab7f (nt!MiReplenishPageSlist+0x0000000000000100)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88008b757b0 -- (.trap 0xfffff88008b757b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=4bd049c154774f3f rbx=0000000000000000 rcx=fdffffffffffffff
rdx=0000000000000050 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002afab7f rsp=fffff88008b75940 rbp=fffffa8006600578
 r8=fffff80002d0f400  r9=fffffa8006600000 r10=fffffa8006600598
r11=fffff88008b75998 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0x100:
fffff800`02afab7f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:8f39:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0fa39 to fffff80002ad5740

STACK_TEXT:  
fffff880`08b74f38 fffff800`02b0fa39 : 00000000`0000001e ffffffff`c0000005 fffff800`02afab7f 00000000`00000000 : nt!KeBugCheckEx
fffff880`08b74f40 fffff800`02ad4d82 : fffff880`08b75708 370dcebf`d65edbd0 fffff880`08b757b0 00000000`0000000f : nt!KiDispatchException+0x1b9
fffff880`08b755d0 fffff800`02ad368a : 00000000`00000000 fffffa80`088a4000 00000000`00041000 fffff880`03d4a44c : nt!KiExceptionDispatch+0xc2
fffff880`08b757b0 fffff800`02afab7f : 00000000`00000000 fffffa80`093c3b30 00000000`0000000f 00000000`003fff1c : nt!KiGeneralProtectionFault+0x10a
fffff880`08b75940 fffff800`02afb0af : fffff800`02d0f400 00000000`00000023 fffffa80`00bd7290 fffffa80`023e5690 : nt!MiReplenishPageSlist+0x100
fffff880`08b759a0 fffff800`02af0a9a : fffff683`fff1cca0 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`08b75ac0 fffff800`02ad382e : 00000000`00000001 000007ff`e3990000 000007ff`f09f6301 000007ff`f09f53c0 : nt!MmAccessFault+0x169a
fffff880`08b75c20 00000000`7409c04d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`1519eed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7409c04d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+100
fffff800`02afab7f f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiReplenishPageSlist+100

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100

BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100

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

Hey zig, I've ran the memtest stuff already. The first time through it showed 28416 errors, then I started pulling sticks and rerunning it. At the end of testing I ended up with all sticks back in the mobo and showing 0 errors. I let all tests make 7 full passes and run for 10 hours each. No errors showing yet I'm still getting crashes.

For now I pulled two sticks of RAM and am just working on 4GB. Hoping the system will be stable for a while and then I can contact Corsair to replace these two whether they're bad or good, because I'm obviously getting crashes.

I also did some searching in relation to my motherboard to see what RAM Gigabyte recommends, and they say 2x2GB DDR2 PC2-6400 1.8V. Since the Corsair I have is PC2-8500 2.1V and Gigabyte recommends PC2-6400 1.8V, would that make any differences or cause any problems?