none
A driver has failed to complete a power IRP within a specific time (usually 10 minutes) : Rt630x64

    Question

  • Hello,

    Sometimes when I shut down my computer, the central unit takes several minutes to power off.

    WinDbg gives the following on the minidump file:

    ------------------

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\082413-29577-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    Machine Name:
    Kernel base = 0xfffff802`78887000 PsLoadedModuleList = 0xfffff802`78b53a20
    Debug session time: Sat Aug 24 18:12:55.727 2013 (UTC + 2:00)
    System Uptime: 0 days 19:05:45.937
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................................
    Loading User Symbols
    Loading unloaded module list
    ........................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa800c00e880, fffff802785da930, fffffa800d808880}

    Probably caused by : pci.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: fffffa800c00e880, Physical Device Object of the stack
    Arg3: fffff802785da930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800d808880, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  pci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5010ab1f

    MODULE_NAME: pci

    FAULTING_MODULE: fffff8800100a000 pci

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    TAG_NOT_DEFINED_c000000f:  FFFFF802785E0FB0

    STACK_TEXT: 
    fffff802`785da8f8 fffff802`78a1d722 : 00000000`0000009f 00000000`00000003 fffffa80`0c00e880 fffff802`785da930 : nt!KeBugCheckEx
    fffff802`785da900 fffff802`78a1d755 : fffffa80`0b9a1680 fffffa80`0dca2c70 fffff802`785daa79 fffff802`78909ef6 : nt!PopIrpWatchdogBugcheck+0xe2
    fffff802`785da960 fffff802`7890a1ea : fffffa80`0dca2c70 00000000`00000000 fffff802`785dac58 00000000`00000000 : nt!PopIrpWatchdog+0x32
    fffff802`785da9b0 fffff802`78908655 : fffff802`785dabf0 fffff802`78909cff fffff802`78b81f00 fffff802`78b822a0 : nt!KiProcessExpiredTimerList+0x22a
    fffff802`785daae0 fffff802`7890a668 : fffff802`78b7f180 fffff802`78b81f80 00000000`00000003 00000000`002803f1 : nt!KiExpireTimerTable+0xa9
    fffff802`785dab80 fffff802`78909a06 : fffffa80`0d833630 fffff802`78b7f180 00000032`2612f440 fffff802`785dac8c : nt!KiTimerExpiration+0xc8
    fffff802`785dac30 fffff802`7890a9ba : fffff802`78b7f180 fffff802`78b7f180 00000000`00183de0 fffff802`78bd9880 : nt!KiRetireDpcList+0x1f6
    fffff802`785dada0 00000000`00000000 : fffff802`785db000 fffff802`785d5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  0x9F_3_Rt630x64_IMAGE_pci.sys

    BUCKET_ID:  0x9F_3_Rt630x64_IMAGE_pci.sys

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

    0: kd> lmvm pci
    start             end                 module name
    fffff880`0100a000 fffff880`01047000   pci        (private pdb symbols)  c:\symbols\pci.pdb\429548BF135649C9A87C6617D1481B962\pci.pdb
        Loaded symbol image file: pci.sys
        Mapped memory image file: c:\symbols\pci.sys\5010AB1F3d000\pci.sys
        Image path: \SystemRoot\System32\drivers\pci.sys
        Image name: pci.sys
        Timestamp:        Thu Jul 26 04:27:43 2012 (5010AB1F)
        CheckSum:         00044B6F
        ImageSize:        0003D000
        File version:     6.2.9200.16384
        Product version:  6.2.9200.16384
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     pci.sys
        OriginalFilename: pci.sys
        ProductVersion:   6.2.9200.16384
        FileVersion:      6.2.9200.16384 (win8_rtm.120725-1247)
        FileDescription:  NT Plug and Play PCI Enumerator
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    ---------------

    Apparently it deals with the Rt630x64.sys driver, which is for the Realtek network adapter. First I had the problem with a driver dated 2011. I downloaded the Windows 8 file to update it from Realtek (impossible to put the link here):

    Win8 and Win8.1 Auto Installation Program (SID:1594877), version 8.018 (2013/8/1),

    believing it would solve the issue. I also installed the diagnosis tool from Realtek for a checkup, everything ok.

    Unfortunately at the third shut down of my PC after Rt630x64.sys driver update, again the problem (WinDbg diagnosis of this message) !

    Please help, don't know what to do anymore...

    Best regards,
    phi phi

    Saturday, August 24, 2013 9:12 PM

Answers

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)
    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    You can read more about BSODS here
    You can learn how to test your memory here



    Wanikiya & Dyami--Team Zigzag

    Saturday, August 24, 2013 10:58 PM
  • Hi,

    I would like to confirm what security software you are using?

    Sometimes third party software will cause this kind of issue. I suggest you uninstall your security software temporarily for a test.


    Niki Han
    TechNet Community Support

    Tuesday, August 27, 2013 2:56 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)
    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    You can read more about BSODS here
    You can learn how to test your memory here



    Wanikiya & Dyami--Team Zigzag

    Saturday, August 24, 2013 10:58 PM
  • Thank you for your reply.

    I cannot send you anything, it says "body text cannot include links or images until we are able to check your account"...

    Kind regards,

    phi phi

    Sunday, August 25, 2013 4:05 PM
  • If you are being told you cant post a link, or embed a picture (or any other restriction) you just need to post to one of these threads saying your account has not been validated

    Wanikiya & Dyami--Team Zigzag

    Sunday, August 25, 2013 9:59 PM
  • Ok I did it, waiting for answer.

    I have impression the problem comes from VirtualBox: the host-only ethernet adapter, from what I read in forums, other people had BSoD apparently linked to this driver... For instance see 'Windows 8 won't shutdown after install virtualbox' on Stack Overflow website.

    Yet I have last version installed (NAT enabled in VirtualBox config).

    In the list of network cards there is also TAP-Windows Adapter V9.

    Would you have a clue about this possible link with VirualBox and an idea what I can do ?

    Last shut down of my PC, it stayed switched on (I waited more than ten minutes), didn't end up switching off automatically as usual, had to do it manually.

    Thx

    Monday, August 26, 2013 11:27 AM
  • Hi,

    I would like to confirm what security software you are using?

    Sometimes third party software will cause this kind of issue. I suggest you uninstall your security software temporarily for a test.


    Niki Han
    TechNet Community Support

    Tuesday, August 27, 2013 2:56 AM
  • Hello, thanks for your reply.

    I use Kaspersky Pure 3.0, I don't think it's this...

    Nevertheless when I was on Vista, after upgrading from Kaspersky 2.0 to 3.0, I had a BSoD at boot up, which was impossible to solve. Thanks Kaspersky because there, you acted as a pure virus.

    Tuesday, August 27, 2013 3:18 PM