BSOD "Attempt to reset display driver and recover from time out failed

[yupper]

I'll see about getting a multimeter. In the mean time, this the latest crash dump. Seems to be a different error than all others I've experienced. Almost all of the BSOD's are preceded by artifactiing (XFX support is pretty useless at the moment...). Any ideas?

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


Loading Dump File [C:\Windows\Minidump\022413-24866-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 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`03051670
Debug session time: Sun Feb 24 18:21:04.487 2013 (UTC - 5:00)
System Uptime: 0 days 2:52:45.173
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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

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: fffff80002ea8240, 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+c0
fffff800`02ea8240 f00fba6b1000    lock bts dword ptr [rbx+10h],0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bb100
 ffffffffffffffff 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TESV.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ecd7e8 to fffff80002e82c40

STACK_TEXT:  
fffff880`08d4bed8 fffff800`02ecd7e8 : 00000000`0000001e ffffffff`c0000005 fffff800`02ea8240 00000000`00000000 : nt!KeBugCheckEx
fffff880`08d4bee0 fffff800`02e822c2 : fffff880`08d4c6b8 e14fc978`23f9a0b0 fffff880`08d4c760 00000000`0000000a : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`08d4c580 fffff800`02e80bca : 00000000`00000000 00000000`00000000 fffffa80`073b3730 fffff880`04fb0962 : nt!KiExceptionDispatch+0xc2
fffff880`08d4c760 fffff800`02ea8240 : ffffffff`ffffffff fffffa80`04546b50 00000000`58550000 fffff800`02ea250c : nt!KiGeneralProtectionFault+0x10a
fffff880`08d4c8f0 fffff800`02ea69ff : fffffa80`03c00960 00000000`0000003c fffffa80`02366f40 00000000`0000003c : nt!MiReplenishPageSlist+0xc0
fffff880`08d4c960 fffff800`02e90134 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`08d4ca80 fffff800`02e80d6e : 00000000`00000001 00000000`585b9000 fffff880`08d4cb01 00000000`00001a40 : nt!MmAccessFault+0x1224
fffff880`08d4cbe0 00000000`042a1574 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018f894 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x42a1574


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+c0

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