F3-12800CL9D-4GBNQ+Asus M4A79XTD Evo BSOD

[Aveamantium]

Well I've been running the replacement ram since June at DDR-1333 8-8-8-24 and started getting BSODs again over the last week (switched to 9-9-9-24 and still getting bsods). Can't be without the computer for the RMA process so I've ordered a set of F3-12800CL9D-4GBRL. Once I get these I'll probably send in my other sticks for RMA. Funny thing is I never get BSODs under load (games, Prime95, memtest86+) and I'm running verifier.exe w/o issue. However, these BSODs seem to come out of the BLUE (pun intended) usually during a cold boot, after coming out of sleep. The last Memory.dmp analysis resulted in the following (if you believe this is not ram related please let me know, TIA):

WARNING: Whitespace at end of path element

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/s...wnload/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e92e50
Debug session time: Sun Nov 28 01:43:08.048 2010 (UTC - 7:00)
System Uptime: 0 days 12:16:25.033
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.................................................. ..........
Loading User Symbols

Loading unloaded module list
.........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {58, 2, 0, fffff80002d83a70}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+40 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000058, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d83a70, address which referenced memory

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


READ_ADDRESS: 0000000000000058

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`02d83a70 4c8b6e58 mov r13,qword ptr [rsi+58h]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880031fc900 -- (.trap 0xfffff880031fc900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880031fcb08 rbx=0000000000000000 rcx=0000000000000006
rdx=fffff880031fcac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d83a70 rsp=fffff880031fca90 rbp=00000000fa800cc1
r8=0000000000000110 r9=00000000000c92d2 r10=0000000000008c30
r11=0000000000000110 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x40:
fffff800`02d83a70 4c8b6e58 mov r13,qword ptr [rsi+58h] ds:00000000`00000058=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cc4ca9 to fffff80002cc5740

STACK_TEXT:
fffff880`031fc7b8 fffff800`02cc4ca9 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031fc7c0 fffff800`02cc3920 : 00000000`00000000 fffffa80`07113930 fffff8a0`102a0700 fffff800`02ccb652 : nt!KiBugCheckDispatch+0x69
fffff880`031fc900 fffff800`02d83a70 : 00000980`00000000 0000007f`fffffff8 00000000`00000010 fa800711`393004c0 : nt!KiPageFault+0x260
fffff880`031fca90 fffff800`02caf9da : fa800cc1`0000000c fa800711`393004c0 fffffa80`07113930 fa800cc1`0000000c : nt!MiReleaseConfirmedPageFileSpace+0x40
fffff880`031fcb10 fffff800`02fb660f : fffffa80`071138b0 00000000`00000000 00000000`00088081 fffffa80`00088081 : nt!MiDeleteSegmentPages+0x316
fffff880`031fcbc0 fffff800`02ded08b : fffffa80`071138b8 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`031fcc00 fffff800`02ded6fd : 00000000`00000000 00000000`00000080 fffffa80`039d6840 00000000`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`031fccc0 fffff800`02f69c06 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`02ca3c26 : fffff880`02f63180 fffffa80`039f6040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc680 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`02d83a70 4c8b6e58 mov r13,qword ptr [rsi+58h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40

BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40

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

[GSKILL TECH]

Did you ever test each module individually? After the cold boot and you restart the computer, does it blue screen again? Or is it perfectly stable?

Thank you
GSKILL TECH

[Aveamantium]

It is very sporadic and hard to reproduce... Funny thing is I put the new ram in (8GB now) and have yet to have an issue. Of course I'm jinxing myself now...

Edit: The speeds are still DDR-3 1333 at 8-8-8-24