Driver Power State Failure??

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80076cb060, fffff80000b9c3d8, fffffa800b860010}

Probably caused by : pci.sys

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

0: kd> !irp fffffa800b860010
Irp is active with 4 stacks 3 is current (= 0xfffffa800b860170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 3]   0 e1 fffffa800a7af050 00000000 fffff80003926210-fffffa800a4c1b30 Success Error Cancel pending
	      Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 \Driver\RTL8167	nt!PopSystemIrpCompletion
			Args: 00016600 00000000 00000006 00000006
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800a4c1b30    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm Rt64win7
start             end                 module name
fffff880`04e00000 fffff880`04e6a000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Wed Feb 16 19:33:57 2011 (4D5B92FD)
    CheckSum:         000754A7
    ImageSize:        0006A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

OK, the issue appears to be caused by the outdated Realtek ethernet driver. Update the driver by downloading a newer one from this site:

Realtek

No worries. Let us know how it goes.