Since Jan 1st, I have been having random crashes, BSOD, and tuner failures for no apparent reason. This only has happened since Jan 1st. I have also completely replaced every piece of hardware in my system. CPU, motherboard, hard drives, DVD drive, CPU, RAM, cables, power supply, case, every has been replaced except for the 2 ATI CableCARD tuners and the 2 Avermedia Duets. But I also have crashes when trying to use the system with one unplugged at a time.

Some days I may not have any crashes, but most days I have 1 or even 5 crashes. What happens is BSOD, or the media center app crashes and or tuner failures happen where I need to reboot in order to watch TV again.

Tonight, I had another BSOD and earlier media center crashed 3 times and another time tuners were failing and I could not watch TV until a reboot.

Here is a dump from my system after the latest BSOD. Any ideas?

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

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

Symbol search path is: D:\Symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
Debug session time: Sun Feb 14 22:56:36.596 2010 (GMT-8)
System Uptime: 0 days 3:36:53.141
Loading Kernel Symbols
............................................................... ................................................................ ...........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8002ede750, 2, 0, fffff80002a815a4}

PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+c4 )

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

0: 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: fffffa8002ede750, 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: fffff80002a815a4, address which referenced memory

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

PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details

READ_ADDRESS: fffffa8002ede750

CURRENT_IRQL: 2

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

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

TRAP_FRAME: fffff880090fc1a0 -- (.trap 0xfffff880090fc1a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002c36e80 rbx=0000000000000000 rcx=fffffa8002ede750
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a815a4 rsp=fffff880090fc330 rbp=0000000000000001
r8=0000000000000001 r9=00000000048c6001 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`02a815a4 488b09 mov rcx,qword ptr [rcx] ds:0400:e750=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002abd469 to fffff80002abdf00

STACK_TEXT:
fffff880`090fc058 fffff800`02abd469 : 00000000`0000000a fffffa80`02ede750 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`090fc060 fffff800`02abc0e0 : 00000000`00134300 fffffa80`007d0760 00000000`00000000 fffff800`02ae84dd : nt!KiBugCheckDispatch+0x69
fffff880`090fc1a0 fffff800`02a815a4 : fffffa80`007d0760 f8a008cc`00000000 00000000`00000000 fffff800`02c735d0 : nt!KiPageFault+0x260
fffff880`090fc330 fffff800`02b7d23d : fffffa80`007d0760 fffff880`090fc480 00000000`00000080 00000000`00074612 : nt!MiRestoreTransitionPte+0xc4
fffff880`090fc390 fffff800`02a713fe : 00000000`00000000 fffff880`090fc480 ffffffff`ffffffff 00000000`000001c0 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`090fc410 fffff800`02ae9e8e : fffff980`05166000 00000000`048c6040 fffff880`00000000 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0x44fc3
fffff880`090fc600 fffff800`02ae9bf4 : fffffa80`0454a320 00000000`048c6040 fffff880`090fc740 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`090fc6f0 fffff880`012e6fb8 : 00000000`59a30000 fffffa80`04b86700 fffff880`090fc7e0 fffffa80`00010000 : nt!CcCopyWrite+0x194
fffff880`090fc780 fffff880`0101a132 : fffffa80`04b86730 fffff880`0101d732 fffff900`00010000 00000000`00010001 : Ntfs!NtfsCopyWriteA+0x208
fffff880`090fc970 fffff880`0101dc2a : fffff880`090fca40 fffffa80`063900d8 00000000`048c0000 00000000`00010000 : fltmgr!FltpPerformFastIoCall+0xf2 fffff880`090fc9d0 fffff880`0103b7fe : 00000000`00010000 00000000`00000000 fffffa80`04b86730 fffff880`090fcb40 : fltmgr!FltpPassThroughFastIo+0xda fffff880`090fca10 fffff800`02dd248e : fffffa80`04b867a4 fffffa80`00000002 fffffa80`03b5f570 fffffa80`04b867a4 : fltmgr!FltpFastIoWrite+0x1ce
fffff880`090fcab0 fffff800`02abd153 : fffffa80`05af3b01 00000000`00001440 00000000`00000000 00000000`09488678 : nt!NtWriteFile+0x5ad
fffff880`090fcbb0 00000000`776aff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0ee1d928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776aff3a

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRestoreTransitionPte+c4
fffff800`02a815a4 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: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRestoreTransitionPte+c4

BUCKET_ID: X64_0xA_nt!MiRestoreTransitionPte+c4

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

And like I said, I have replaced every piece of hardware except the tuners but I have tried the system with each tuner unplugged and removed from the system but it would still crash. I am also only installing updates from Windows Update including all my driver but sometimes if I just installed Windows, it would just crash with a BSOD. Nothing had even been install, it would just have rebooted from the final reboot of installing Windows and I have not done anything yet.

Today I did a fresh install again but this time I turned off all Windows Update and only allowed the Duets to install. Haven't hard a single issue yet. To me it looks like there is an issue coming from Windows Update. Looking around online and other have this exact problem but no one seems to know why. The only fix seems to do a restore before Jan. 1st. From the various testings I have done it looks like what may be causing an issue is when the ATI cards update their firmware from Windows Update, which it shouldn't be since they already have the latest. But it seems like once I do that, things start crashing.