Windows 7: Realtek win7 x64 Tried it all will not install Get BSOD

icrosoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Windows\Minidump\010911-26769-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 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`03203000 PsLoadedModuleList = 0xfffff800`03440e50
Debug session time: Sun Jan  9 19:00:58.769 2011 (UTC - 8:00)
System Uptime: 0 days 0:02:14.845
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {60, 2, 1, fffff8000327cc9c}
Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+2878dc )
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: 0000000000000060, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8000327cc9c, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ab0e0
 0000000000000060 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`0327cc9c f00fba2e07      lock bts dword ptr [rsi],7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  fffff880031bd810 -- (.trap 0xfffff880031bd810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000021c3 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000327cc9c rsp=fffff880031bd9a0 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff88002f63180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x13c:
fffff800`0327cc9c f00fba2e07      lock bts dword ptr [rsi],7 ds:da10:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80003272ca9 to fffff80003273740
STACK_TEXT:  
fffff880`031bd6c8 fffff800`03272ca9 : 00000000`0000000a 00000000`00000060 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`031bd6d0 fffff800`03271920 : ffff0800`00000011 00000000`00000000 fffff880`031bd8e0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031bd810 fffff800`0327cc9c : 00000000`00000000 00000000`00000000 fffff880`086e38ac 80000000`00000000 : nt!KiPageFault+0x260
fffff880`031bd9a0 fffff880`086e38dc : 00000000`00000000 fffff880`00000000 00000000`00000000 00000000`00010200 : nt!KeWaitForSingleObject+0x13c
fffff880`031bda40 00000000`00000000 : fffff880`00000000 00000000`00000000 00000000`00010200 00000000`00000000 : RTKVHD64+0x2878dc
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
RTKVHD64+2878dc
fffff880`086e38dc ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  RTKVHD64+2878dc
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: RTKVHD64
IMAGE_NAME:  RTKVHD64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d1c020a
FAILURE_BUCKET_ID:  X64_0xA_RTKVHD64+2878dc
BUCKET_ID:  X64_0xA_RTKVHD64+2878dc
Followup: MachineOwner
---------