PCI.sys Driver Powerstate blue screens

Page 1 of 3 123 LastLast

  1. Posts : 3
    Windows 7 x64 Professional
       #1

    PCI.sys Driver Powerstate blue screens


    Getting a bluescreen about 1-2 a day.
    all analysis of the minidump files point to a driver power state issue with PCI.sys

    installed Windows 7 x64 professional running under bootcamp (not virtualized)
    Latest version of bootcamp (3.1) and drivers are installed


    heres the analysis:
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Windows\Minidump\040510-13291-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 (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e40e50
    Debug session time: Mon Apr  5 11:45:38.923 2010 (UTC - 4:00)
    System Uptime: 0 days 21:05:39.017
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, fffffa80021e9060, fffff80000b9c518, fffffa8003bda2f0}
    Probably caused by : pci.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: fffffa80021e9060, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa8003bda2f0, The blocked IRP
    Debugging Details:
    ------------------
     
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  pci.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117
    MODULE_NAME: pci
    FAULTING_MODULE: fffff88000e00000 pci
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`02ce3e23 : 00000000`0000009f 00000000`00000003 fffffa80`021e9060 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02c80fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
    fffff800`00b9c570 fffff800`02c80326 : fffffa80`03b10c68 fffffa80`03b10c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02c80e7e : 000000b0`cf2e8183 fffff800`00b9cc58 00000000`004a470e fffff800`02df0448 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02c80697 : 0000001b`de2e9dc3 0000001b`004a470e 0000001b`de2e9dc2 00000000`0000000e : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02c7d6fa : fffff800`02dede80 fffff800`02dfbc40 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_bcmwl664_IMAGE_pci.sys
    BUCKET_ID:  X64_0x9F_3_bcmwl664_IMAGE_pci.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: fffffa80021e9060, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa8003bda2f0, The blocked IRP
    Debugging Details:
    ------------------
     
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  pci.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117
    MODULE_NAME: pci
    FAULTING_MODULE: fffff88000e00000 pci
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`02ce3e23 : 00000000`0000009f 00000000`00000003 fffffa80`021e9060 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02c80fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
    fffff800`00b9c570 fffff800`02c80326 : fffffa80`03b10c68 fffffa80`03b10c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02c80e7e : 000000b0`cf2e8183 fffff800`00b9cc58 00000000`004a470e fffff800`02df0448 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02c80697 : 0000001b`de2e9dc3 0000001b`004a470e 0000001b`de2e9dc2 00000000`0000000e : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02c7d6fa : fffff800`02dede80 fffff800`02dfbc40 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_bcmwl664_IMAGE_pci.sys
    BUCKET_ID:  X64_0x9F_3_bcmwl664_IMAGE_pci.sys
    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello Welcome to SF !!

    PCI.sys was a common issue with XP. Did your Upgrade form XP to Windows 7 ?? Or was it a clean install ?? If its an upgrade it might wanna consider clean install. Anyway post us the Dump files !!

    Hope this helps,
    Captain
      My Computer


  3. Posts : 3
    Windows 7 x64 Professional
    Thread Starter
       #3

    Capt.Jack Sparrow said:
    Hello Welcome to SF !!

    PCI.sys was a common issue with XP. Did your Upgrade form XP to Windows 7 ?? Or was it a clean install ?? If its an upgrade it might wanna consider clean install. Anyway post us the Dump files !!

    Hope this helps,
    Captain
    It was a clean install. running into permissions issues trying to post the dump files. let me see if I can figure out a workaround
      My Computer


  4. Posts : 1
    Windows Vista, 7
       #4

    I too am running a clean install of Windows 7 on bootcamp and I frequently experience crashes, either when the computer puts itself into sleep mode or when I close the lid of the laptop (the latter seems to cause the problem more frequently which has made me afraid to close the list while it's running).

    I just saw a new BSOD a few minutes ago and it was indeed a DRIVER_POWER_STATE_FAILURE error.

    I'm guessing this is a problem with the bootcamp drivers and that it might be more effective to inquire at an Apple support forum?
      My Computer


  5. Posts : 14
    Windows 7 Pro x64
       #5

    I am having the same issue. Here's my dump file. Hope it helps. I'd like to fix it, if possible. I use sleep mode quite often.

    Additional info: This is a custom built PC nothing to do with mac. I've also run memory diagnostics provided by this OS, and it was clean. I thought maybe it was saving files to a faulty stick. It doesn't seem to be the case.

    I upgraded from XP Pro 32 bit. I'm using windows 7 pro 64 bit clean install on a completely different HDD.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: symsrv*symsrv.dll*e:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02807000 PsLoadedModuleList = 0xfffff800`02a44e50
    Debug session time: Fri Jun 25 20:57:58.554 2010 (UTC - 5:00)
    System Uptime: 0 days 16:46:09.348
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8004650060, fffff80003d59518, fffffa80066d1830}
    
    Probably caused by : pci.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: fffffa8004650060, Physical Device Object of the stack
    Arg3: fffff80003d59518, Functional Device Object of the stack
    Arg4: fffffa80066d1830, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000f5c000 pci
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`03d594c8 fffff800`028e61b3 : 00000000`0000009f 00000000`00000003 fffffa80`04650060 fffff800`03d59518 : nt!KeBugCheckEx
    fffff800`03d594d0 fffff800`028836a6 : fffff800`03d59600 fffff800`03d59600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
    fffff800`03d59570 fffff800`02882a26 : fffffa80`043d87d8 fffffa80`043d87d8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`03d595e0 fffff800`0288357e : 0000008c`8eef9780 fffff800`03d59c58 00000000`003b0c6d fffff800`029f5028 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`03d59c30 fffff800`02882d97 : 00000024`99bc99ca 00000024`003b0c6d 00000024`99bc9970 00000000`0000006d : nt!KiTimerExpiration+0x1be
    fffff800`03d59cd0 fffff800`0287fdfa : fffff800`029f1e80 fffff800`029ffc40 00000000`00000000 fffff880`01667c50 : nt!KiRetireDpcList+0x277
    fffff800`03d59d80 00000000`00000000 : fffff800`03d5a000 fffff800`03d54000 fffff800`03d59d40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_nvmf6264_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_nvmf6264_IMAGE_pci.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #6

    Bugcheck code 9F is usually correspond to driver issues. Can you please upload your minidump so that I can take a look at the loaded drivers
    Thanks
    ~Tuan
      My Computer


  7. Posts : 14
    Windows 7 Pro x64
       #7

    The dump file is 102 mbs zipped I can upload it to a file hosting service if that is allowed.
      My Computer


  8. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #8

    c0ke543 said:
    The dump file is 102 mbs zipped I can upload it to a file hosting service if that is allowed.
    Go to C:\Windows\Minidumps, and copy all of them to a folder on the desktop. Then zip those up and upload them here.

    ~Lordbob
      My Computer


  9. Posts : 14
    Windows 7 Pro x64
       #9

    haha my bad. I was looking at the memory.dmp file in just the windows folder. I just did a couple tests. I recreated the conditions it crashed on. I open a media player and firefox, then let it sleep tried to wake it after a minute. The computer woke, but the screen stayed black. However if I unpaused the video with the keyboard hotkey. I could hear the video playing, but the monitor was still in standby.

    Also it woke from sleep fine, when I had all programs closed. Another thing I noticed is I didn't hear the HDD make it's spin down noise, when it sleeps with the media player and firefox open. I never heard the spin down despite waiting 2 mins.

    Here's the dump file.
      My Computer


  10. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #10

    Ok, the 9F stop code can indicate a power problem, but it is usually drivers.

    The dump indicated that the problem was caused by the system driver for the PCI slots.\
    To fix this file, start an elevated command prompt (hit start, cmd, right click, run as admin) and type sfc /scannow. What happens?

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp1_062510-40107-01.zip\062510-40107-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`03d59500?
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02807000 PsLoadedModuleList = 0xfffff800`02a44e50
    Debug session time: Fri Jun 25 18:57:58.554 2010 (UTC - 7:00)
    System Uptime: 0 days 16:46:09.348
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8004650060, fffff80003d59518, fffffa80066d1830}
    
    Probably caused by : pci.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: fffffa8004650060, Physical Device Object of the stack
    Arg3: fffff80003d59518, Functional Device Object of the stack
    Arg4: fffffa80066d1830, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000f5c000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`03d594c8 fffff800`028e61b3 : 00000000`0000009f 00000000`00000003 fffffa80`04650060 fffff800`03d59518 : nt!KeBugCheckEx
    fffff800`03d594d0 fffff800`028836a6 : fffff800`03d59600 fffff800`03d59600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
    fffff800`03d59570 fffff800`02882a26 : fffffa80`043d87d8 fffffa80`043d87d8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`03d595e0 fffff800`0288357e : 0000008c`8eef9780 fffff800`03d59c58 00000000`003b0c6d fffff800`029f5028 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`03d59c30 fffff800`02882d97 : 00000024`99bc99ca 00000024`003b0c6d 00000024`99bc9970 00000000`0000006d : nt!KiTimerExpiration+0x1be
    fffff800`03d59cd0 fffff800`0287fdfa : fffff800`029f1e80 fffff800`029ffc40 00000000`00000000 fffff880`01667c50 : nt!KiRetireDpcList+0x277
    fffff800`03d59d80 00000000`00000000 : fffff800`03d5a000 fffff800`03d54000 fffff800`03d59d40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_nvmf6264_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_nvmf6264_IMAGE_pci.sys
    
    Followup: MachineOwner
    ---------
    ~Lordbob
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:42.
Find Us