BSOD - Intermittently - ntoskrnl.exe+df273

Hi there, I have made and given a PC to some relatives and it's bluescreening. I've got the Dump collection and Perfmon results zipped up, I also added the SIW.exe quick html scan, so all the hardware bases are covered. The html file with the hardware info is in the zip file.

If you could have a look that'd be great.
This PC also has a Logitech MX5500 mouse keyboard combo. iPods are connected time to time, but that's about it in the way of peripheral devices.
No extra PCI cards or anything either.

Espio said:

Hi there, I have made and given a PC to some relatives and it's bluescreening. I've got the Dump collection and Perfmon results zipped up, I also added the SIW.exe quick html scan, so all the hardware bases are covered. The html file with the hardware info is in the zip file.

If you could have a look that'd be great.
This PC also has a Logitech MX5500 mouse keyboard combo. iPods are connected time to time, but that's about it in the way of peripheral devices.
No extra PCI cards or anything either.

All of these were caused by yout network driver Rt64win7.sys


Probably caused by : Rt64win7.sys


I would re-install it.

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111810-13478-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;srv*e:\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`03010000 PsLoadedModuleList = 0xfffff800`0324de50
Debug session time: Wed Nov 17 13:45:04.696 2010 (GMT-5)
System Uptime: 1 days 0:07:06.726
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80040eaa20, fffff80000b9c518, fffffa8004bad580}

*** 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: fffffa80040eaa20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8004bad580, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8004bad580

DEVICE_OBJECT: fffffa80049d8050

DRIVER_OBJECT: fffffa80049dc930

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c970f61

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88003d88000 Rt64win7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030ef273 to fffff80003080740

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`030ef273 : 00000000`0000009f 00000000`00000003 fffffa80`040eaa20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0308c29e : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`0308bdd6 : fffffa80`060d5168 fffffa80`060d5168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0308c4be : 000000ca`28c30c4e fffff800`00b9cc58 00000000`0054ed54 fffff800`031fdd08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0308bcb7 : 0000003a`1ace5ac3 0000003a`0054ed54 0000003a`1ace5adf 00000000`00000054 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03088eea : fffff800`031fae80 fffff800`03208c40 00000000`00000002 fffff880`00000000 : 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
---------

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: fffffa80040eaa20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8004bad580, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8004bad580

DEVICE_OBJECT: fffffa80049d8050

DRIVER_OBJECT: fffffa80049dc930

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c970f61

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88003d88000 Rt64win7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030ef273 to fffff80003080740

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`030ef273 : 00000000`0000009f 00000000`00000003 fffffa80`040eaa20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0308c29e : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`0308bdd6 : fffffa80`060d5168 fffffa80`060d5168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0308c4be : 000000ca`28c30c4e fffff800`00b9cc58 00000000`0054ed54 fffff800`031fdd08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0308bcb7 : 0000003a`1ace5ac3 0000003a`0054ed54 0000003a`1ace5adf 00000000`00000054 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03088eea : fffff800`031fae80 fffff800`03208c40 00000000`00000002 fffff880`00000000 : 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
---------

Hello again. So I've just got back on to this computer, and I've reinstalled the network driver(Realtek RTL8112L LAN Driver V7.6.820.2009 for 32/64bit Windows 7.(WHQL) Off the Asus website). I will post back to confirm what the outcome is.
And thanks ZigZag, your prompt reply was uber excellent.

So far so good, the internet seemed to be quite intermittent prior to the driver. Everything has been good in the last 4hours.

Well, it seems it blue screened this morning. Unfortunatly im not near the computer to send you the new bluescreen logs.
I will get back to you after the break