Random Windows 7 BSOD

Caused by memory corruption. Carry on with the GFX card plan.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\071510-13260-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50
Debug session time: Thu Jul 15 15:00:01.928 2010 (UTC - 4:00)
System Uptime: 0 days 13:00:28.958
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa000886da50, 2, 0, fffff80002c81c74}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+c4 )

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

6: 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: fffffa000886da50, 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: fffff80002c81c74, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef60e0
 fffffa000886da50 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRestoreTransitionPte+c4
fffff800`02c81c74 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033466a0 -- (.trap 0xfffff880033466a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880030f9180 rbx=0000000000000000 rcx=fffffa000886da50
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c81c74 rsp=fffff88003346830 rbp=0000000000000001
 r8=0000000000000001  r9=fffff80002e4ad01 r10=0000000000000002
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiRestoreTransitionPte+0xc4:
fffff800`02c81c74 488b09          mov     rcx,qword ptr [rcx] ds:04c0:fffffa00`0886da50=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cbdb69 to fffff80002cbe600

STACK_TEXT:  
fffff880`03346558 fffff800`02cbdb69 : 00000000`0000000a fffffa00`0886da50 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03346560 fffff800`02cbc7e0 : 00000000`0001acf2 fffffa80`03322860 00000001`585f6921 fffff6fc`c0077578 : nt!KiBugCheckDispatch+0x69
fffff880`033466a0 fffff800`02c81c74 : fffffa80`03322860 ffffffff`00000000 fffffa80`008e2030 fffff800`02e635b8 : nt!KiPageFault+0x260
fffff880`03346830 fffff800`02d7f1dd : fffffa80`03322860 fffff880`03346980 00000000`00000080 00000000`000925a6 : nt!MiRestoreTransitionPte+0xc4
fffff880`03346890 fffff800`02c639d5 : fa800907`14b004c0 fffff880`03346980 00000000`000006d0 00000000`00000000 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`03346910 fffff800`02f5f89a : fffffa80`07cf7b30 fffffa80`00000001 fffffa80`07cf7b30 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x2d928
fffff880`03346a80 fffff800`02c70a57 : fffffa80`07cf7b30 00000000`024cd000 00000000`024cd000 fffff800`02e635a0 : nt!MmPrefetchForCacheManager+0x96
fffff880`03346ad0 fffff800`02cb2472 : fffffa80`060208d0 fffffa80`00000000 fffff880`00000000 fffff880`04109701 : nt!CcPerformReadAhead+0x2f3
fffff880`03346c00 fffff800`02ccb861 : fffffa80`05511550 fffff800`02cb2254 fffff800`02ec5150 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`03346cb0 fffff800`02f63a86 : 00000000`00000000 fffffa80`0551d680 00000000`00000080 fffffa80`054ed040 : nt!ExpWorkerThread+0x111
fffff880`03346d40 fffff800`02c9cb06 : fffff880`0316a180 fffffa80`0551d680 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03346d80 00000000`00000000 : fffff880`03347000 fffff880`03341000 fffff880`033469f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRestoreTransitionPte+c4
fffff800`02c81c74 488b09          mov     rcx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiRestoreTransitionPte+c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiRestoreTransitionPte+c4

BUCKET_ID:  X64_0xA_nt!MiRestoreTransitionPte+c4

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

Again, graphic card issue, have you check this article about stop code 116:
https://www.sevenforums.com/crash-loc...eshooting.html

Download and install fresh copy of directx please:
Download details: DirectX End-User Runtime

Code:

BugCheck A, {0, 2, 0, fffff80002ea7183}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiReadPnpRegistryValue+107 )

Followup: MachineOwner
---------
BugCheck A, {fffff800031065f8, 2, 8, fffff800031065f8}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+4fce7 )

Followup: MachineOwner
---------
BugCheck 116, {fffffa80086dc4e0, fffff8801053fc88, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+704c88 )

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

DirectX found nothing to update. I will now run Furmark and Prime95 at the same time and then post my results.

*edit*
Here are the results: my CPU failed Prime95. So what now?

*edit2*
Here are my CPU and voltage settings.
No Overclock.
Do you guys know of any program where I could look for voltage spikes/drops in a graph?

I recommend that you have your computer checked by a competent technician. Perhaps it is time to replace the CPU.

I am glad you have a warranty on the CPU; that helps. It may be time to RMA; but I sure don't blame you for trying everything else first.

By all means RMA your CPU. If the mobo is under warranty, exchange that too.