*sigh* STILL getting BSODs

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp7_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\110910-12558-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e57e50
Debug session time: Tue Nov  9 19:01:50.313 2010 (GMT-5)
System Uptime: 0 days 1:26:39.357
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80062a4a20, fffff80000b9c518, fffffa8008a88e10}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80062a4a20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8008a88e10, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa8008a88e10
DEVICE_OBJECT: fffffa8007168050
DRIVER_OBJECT: fffffa8006826a70
IMAGE_NAME:  Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4b2c98c2
MODULE_NAME: Rt64win7
FAULTING_MODULE: fffff88004200000 Rt64win7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002cf9273 to fffff80002c8a740
STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02cf9273 : 00000000`0000009f 00000000`00000003 fffffa80`062a4a20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02c9629e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`02c95dd6 : fffffa80`07326a80 fffffa80`07326a80 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02c964be : 0000000c`1b0f0f2c fffff800`00b9cc58 00000000`000515ea fffff800`02e08fc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02c95cb7 : 00000003`28ede4c2 00000003`000515ea 00000003`28ede406 00000000`000000ea : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02c92eea : fffff800`02e04e80 fffff800`02e12c40 00000000`00000000 fffff880`014b4c50 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys
BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys
Followup: MachineOwner
---------

Rt64win7.sys file description
Productname: Realtek 8136/8168/8169 PCI/PCIe Adapters
Description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
Company: Realtek ---Update driver

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command
Scan with your Anti Virus

Is this the most current?
Rt64win7.sys Sat Dec 19 04:11:30 2009

Official definition of 9F
STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE Usual causes: Device driver