BSOD ntoskrnl.exe

[cyclone3211]

This has happened several times on Win7 Pro. Notice that I am running two machines and the other ntoskrnl.exe file is dated in May while the machine in trouble is dated in March. I have attached several files.

 

[Arc]

Hello cyclone3211.

A stop 0x9F caused by the realtek network driver is rare. Please let me understand one thing? Your onboard connection is Marvell Yukon, and you are using Realtek? Is it a card?

Anyway, the driver is kinda backdated.

fffff880`0547e000 fffff880`05545000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
[COLOR=Red]    Image name: Rt64win7.sys
    Timestamp:        Wed Dec 26 22:47:50 2012[/COLOR] (50DB313E)
    CheckSum:         000CDEEE
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek

Also, uninstall SeriousBit NetBalancer Internet traffic control (nbdrv.sys) and Networx, at least as a try.

Moreover, it appears to be a desktop computer. So you can disable Sleep and hibernate. It will also help you to get rid of your issue.

Let us know the results.
_________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ae4a10, fffff80000b9c518, fffffa800ccebcf0}

*** 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 has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ae4a10, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800ccebcf0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa800869b050

DRIVER_OBJECT: fffffa800869f800

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50db313e

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff8800547e000 Rt64win7

IRP_ADDRESS:  fffffa800ccebcf0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0494d8c2 : 00000000`0000009f 00000000`00000003 fffffa80`07ae4a10 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`048e884c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`048e86e6 : fffff800`04a8df20 00000000`000683b2 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`048e85ce : 0000000f`88187094 fffff800`00b9cc58 00000000`000683b2 fffff800`04a5c8c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`048e83b7 : 00000004`ddd28fc1 00000004`000683b2 00000004`ddd28f17 00000000`000000b2 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`048d590a : fffff800`04a58e80 fffff800`04a66cc0 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_3_POWER_DOWN_IMAGE_Rt64win7.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_Rt64win7.sys

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

0: kd> lmvm Rt64win7
start             end                 module name
fffff880`0547e000 fffff880`05545000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Wed Dec 26 22:47:50 2012 (50DB313E)
    CheckSum:         000CDEEE
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa800ccebcf0

 

[cyclone3211]

Thank you for the replay and instructions which I did the following:

1. Uninstall SeriousBit NetBalancer Internet traffic control (nbdrv.sys) and Networx

2. Did a Restore backup and installed the updated Realtek driver

3. Yes, it is a desktop and I do not remember if after getting this unit if I installed a separate sound card. The unit came with " 3D Premium Surround Sound Onboard" if you think it is important to find out I will open the machine and see.

4. Hibernate caused various problems in the past and disabled it but it did come back but I do not use it. Sleep on the other hand I do use often, even multiple times during the day. I seldom turn my computer off but leave it in Sleep. Nightly, I do turn off the monitor. The box is loaded with drives and I have always left the unit on rather than turning it on and off. Liked using Hibernation when it worked well but it started to lock my machine and then turned to Sleep as an alternative.

If you have another suggestion, please advise on this.

5 Hope this works and again many thanks.

 

[Arc]

Now it is the time to wait and observe the situation

 

[cyclone3211]

Thank you again for your help on this......hope this is the fix.