BSODs when gaming (Driver Power State Failure)


  1. Posts : 4
    Windows 10 Home
       #1

    BSODs when gaming (Driver Power State Failure)


    Hi all,

    Been having this issue since I got this laptop. Computer consistently throws a BSOD when playing games or even generating plots in MATLAB. I suspect that its an issue with Windows 10 and NVIDIA since I've heard they tend to not play nice with each other, but since I have no idea how to analyze a minidump, I'm hoping someone here can give me some advice. Thanks in advance.

    Attachment 76906
      My Computer


  2. Posts : 654
    windows 10 Pro
       #2

    Because you have a laptop it is adviced to use the latest "customized" OEM driver for your specific laptop Satellite S50T-C from here http://support.toshiba.com/support/m...Text=XF143374C.
      My Computer


  3. Posts : 4
    Windows 10 Home
    Thread Starter
       #3

    lifetec said:
    Because you have a laptop it is adviced to use the latest "customized" OEM driver for your specific laptop Satellite S50T-C from here http://support.toshiba.com/support/m...Text=XF143374C.
    I have installed all the recommended drivers I could find from this page:
    http://support.toshiba.com/support/m...ext=1200010947
    as that is the model of my notebook. Still have the same problem. Anything specific from the files I posted by any chance?
      My Computer


  4. Posts : 654
    windows 10 Pro
       #4

    Could you upload a new zip with the latest BSOD.
      My Computer


  5. Posts : 4
    Windows 10 Home
    Thread Starter
       #5

    This should include the latest crash. Thanks again.

    Attachment 77308
      My Computer


  6. Posts : 654
    windows 10 Pro
       #6

    The latest dumpfile is

    Code:
     ******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, ffffe0014e33c060, ffffd000405b4890, ffffe001574fb770}
    
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0014e33c060, Physical Device Object of the stack
    Arg3: ffffd000405b4890, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001574fb770, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5632d60a
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff801b8930000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    
    DPC_STACK_BASE:  FFFFD000405BCFB0
    
    STACK_TEXT:  
    ffffd000`405b4858 fffff802`00068e42 : 00000000`0000009f 00000000`00000003 ffffe001`4e33c060 ffffd000`405b4890 : nt!KeBugCheckEx
    ffffd000`405b4860 fffff802`00068d62 : ffffe001`4c867ea8 ffffe001`4c9463d8 00000000`00000000 fffff801`fff520a6 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd000`405b48c0 fffff801`ffef62c6 : ffffe001`4c867ee0 ffffd000`405b4a10 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
    ffffd000`405b4910 fffff801`fffcd51a : ffffffff`00000000 ffffd000`40589180 ffffd000`40595cc0 ffffe001`4dcda800 : nt!KiRetireDpcList+0x5f6
    ffffd000`405b4b60 00000000`00000000 : ffffd000`405b5000 ffffd000`405ae000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_VERSION:  10.0.10586.0
    
    FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys
    
    BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_nvlddmkm_image_pci.sys
    
    FAILURE_ID_HASH:  {a47222af-fbac-bc49-47e0-2cf5d31cc673}
    The dumpfile points to your Nvdiadriver, as you have installed the latest driver from the supportpage.
    It could be that it is corrupted somehow, please uninstall the driver using DDU uninstaller ( Display Driver Uninstaller Download version 15.7.5.5 ) and reinstall the latest driver from your supportpage.

    Also do you have updated your chipset drivers and the other Intel drivers? ( because of the pci.sys mentioning)
      My Computer


  7. Posts : 4
    Windows 10 Home
    Thread Starter
       #7

    I have update chipset drivers and BIOS though I suppose there are a few drivers I haven't touched like WiFi and sound since I figured they weren't likely to be the problem.
    lifetec said:
    The latest dumpfile is

    Code:
     ******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, ffffe0014e33c060, ffffd000405b4890, ffffe001574fb770}
    
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0014e33c060, Physical Device Object of the stack
    Arg3: ffffd000405b4890, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001574fb770, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5632d60a
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff801b8930000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    
    DPC_STACK_BASE:  FFFFD000405BCFB0
    
    STACK_TEXT:  
    ffffd000`405b4858 fffff802`00068e42 : 00000000`0000009f 00000000`00000003 ffffe001`4e33c060 ffffd000`405b4890 : nt!KeBugCheckEx
    ffffd000`405b4860 fffff802`00068d62 : ffffe001`4c867ea8 ffffe001`4c9463d8 00000000`00000000 fffff801`fff520a6 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd000`405b48c0 fffff801`ffef62c6 : ffffe001`4c867ee0 ffffd000`405b4a10 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
    ffffd000`405b4910 fffff801`fffcd51a : ffffffff`00000000 ffffd000`40589180 ffffd000`40595cc0 ffffe001`4dcda800 : nt!KiRetireDpcList+0x5f6
    ffffd000`405b4b60 00000000`00000000 : ffffd000`405b5000 ffffd000`405ae000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_VERSION:  10.0.10586.0
    
    FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys
    
    BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_nvlddmkm_image_pci.sys
    
    FAILURE_ID_HASH:  {a47222af-fbac-bc49-47e0-2cf5d31cc673}
    The dumpfile points to your Nvdiadriver, as you have installed the latest driver from the supportpage.
    It could be that it is corrupted somehow, please uninstall the driver using DDU uninstaller ( Display Driver Uninstaller Download version 15.7.5.5 ) and reinstall the latest driver from your supportpage.

    Also do you have updated your chipset drivers and the other Intel drivers? ( because of the pci.sys mentioning)
      My Computer


 

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

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




Windows 10 Forums