• Question

  • i'm having blue screen DRIVER_STATE_POWER_FAILURE a few times that loads the only game  i'm playing (dota2) . Already formatted and updated all drivers and the problem continues. 


    [MODERATED: Personal file share URL redacted, 3rd party app and file links not accepted any more. Not in an open forum. If you have Microsoft Support, you can pass to them directly.]

    Wednesday, October 2, 2019 12:11 AM

All replies

  • Sorry to hear that, but if it's a particular [non-Microsoft] game, you're probably better off asking on the creator site of the game. That is a very generic driver message and you can find some great guides on for this kind of thing. Of course it could be so many things.

    Unfortunately I had to remove your private site link. The only external links we should be providing are Microsoft products.

    In this day and age, downloading someone's files from a private file share (especially someone with no points or history) is a risk. No accusations of course, just a general rule and advice. You could upload to GitHub, or simply print some of them clearly, in text form here.


    Kind regards,




    Got any nice code? If you invest time in coding an elegant, novel or impressive answer on MSDN forums, why not copy it over to TechNet Wiki, for future generations to benefit from! You'll never get archived again, and you could win weekly awards!

    Have you got what it takes to become this month's TechNet Technical Guru? Join a long list of well known community big hitters, show your knowledge and prowess in your favoured technologies!

    Wednesday, October 2, 2019 1:51 AM
  • Ok. thanks. I pasted the dump text below. I don't think the fault is exclusive to the game, because I just have it and only occurs sometimes.

    FAILURE_BUCKET_ID: 0x9F_3_ACPI_pci!PciBusInterface_GetBusData__PERF__(pci+0x0)

    Bugcheck Analysis                                    
    A driver has failed to complete a power IRP within a specific time.
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffff8907f99ef060, Physical Device Object of the stack
    Arg3: fffff80172c087b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffff890800edb520, The blocked IRP
    Debugging Details:
    Implicit thread is now ffff8907`f7ab9180
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
        Key  : Analysis.CPU.Sec
        Value: 5
        Key  : Analysis.DebugAnalysisProvider.CPP
        Value: Create: 8007007e on DESKTOP-4UNEPGP
        Key  : Analysis.DebugData
        Value: CreateObject
        Key  : Analysis.DebugModel
        Value: CreateObject
        Key  : Analysis.Elapsed.Sec
        Value: 6
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 78
        Key  : Analysis.System
        Value: CreateObject
        Key  : Dump.Attributes.InsufficientDumpfileSize
        Value: 1
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump
    BUGCHECK_P1: 3
    BUGCHECK_P2: ffff8907f99ef060
    BUGCHECK_P3: fffff80172c087b0
    BUGCHECK_P4: ffff890800edb520
    FAULTING_THREAD:  ffff8907f7ab9180
    IMAGE_NAME:  pci.sys
    MODULE_NAME: pci
    FAULTING_MODULE: fffff80170b70000 pci
    BLACKBOXACPI: 1 (!blackboxacpi)
    BLACKBOXBSD: 1 (!blackboxbsd)
    BLACKBOXNTFS: 1 (!blackboxntfs)
    BLACKBOXPNP: 1 (!blackboxpnp)
    PROCESS_NAME:  System
    fffffd87`8181d590 fffff801`6e43c77d : fffff801`6a3e4180 ffff8908`fffffffe fffff801`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76
    fffffd87`8181d6d0 fffff801`6e43b604 : ffff8907`f7ab9180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xbfd
    fffffd87`8181d770 fffff801`6e43ada5 : 00000000`00000000 00000000`00000000 ffff9a88`711cb300 00000000`00000000 : nt!KiCommitThreadWait+0x144
    fffffd87`8181d810 fffff801`70a82a9a : fffffd87`8181d958 00000000`00000000 00000000`00000000 ffff8907`fb287400 : nt!KeWaitForSingleObject+0x255
    fffffd87`8181d8f0 fffff801`70a91797 : fffffd87`00000000 ffff8907`fb2874b8 00000000`00000004 00000000`00000028 : ACPI!SyncEvalObject+0x29a
    fffffd87`8181d9a0 fffff801`70a9135a : 00000000`00000000 ffffa00f`e359e510 00000000`00000000 ffffa00f`e06a45e0 : ACPI!AMLIEvalNameSpaceObject+0xab
    fffffd87`8181da00 fffff801`70a81586 : ffff8908`0abd8340 fffff801`00000004 ffffa00f`e359e510 ffff8907`fb287530 : ACPI!ACPIIoctlEvalControlMethod+0xa6
    fffffd87`8181da90 fffff801`70a810d8 : ffff8907`f7bc8bc0 00000000`00000007 ffff8908`0abd84a0 ffff8908`00000004 : ACPI!ACPIIrpDispatchDeviceControl+0x186
    fffffd87`8181dad0 fffff801`6e431f39 : 00000000`00000007 00000000`c00000bb fffffd87`8181dc90 00000000`00000000 : ACPI!ACPIDispatchIrp+0xc8
    fffffd87`8181db50 fffff801`86ca2966 : ffff8908`05384000 fffff801`6e431f39 00000000`00000007 00000000`c00000bb : nt!IofCallDriver+0x59
    fffffd87`8181db90 fffff801`86b42aea : ffff8908`0abd8340 ffff8908`00195030 00000000`00000000 ffff8908`00195030 : dxgkrnl!DpiFdoDispatchIoctl+0x6f6
    fffffd87`8181e6b0 fffff801`8e019567 : ffff8908`0abd8340 ffff8908`0abd84a0 ffff8908`0abd8340 ffff8908`00195030 : dxgkrnl!DpiDispatchIoctl+0xda
    fffffd87`8181e7d0 ffff8908`0abd8340 : ffff8908`0abd84a0 ffff8908`0abd8340 ffff8908`00195030 00000000`00000054 : nvlddmkm+0xd9567
    fffffd87`8181e7d8 ffff8908`0abd84a0 : ffff8908`0abd8340 ffff8908`00195030 00000000`00000054 ffff8908`00195030 : 0xffff8908`0abd8340
    fffffd87`8181e7e0 ffff8908`0abd8340 : ffff8908`00195030 00000000`00000054 ffff8908`00195030 ffff8908`0abd8340 : 0xffff8908`0abd84a0
    fffffd87`8181e7e8 ffff8908`00195030 : 00000000`00000054 ffff8908`00195030 ffff8908`0abd8340 fffff801`8e019366 : 0xffff8908`0abd8340
    fffffd87`8181e7f0 00000000`00000054 : ffff8908`00195030 ffff8908`0abd8340 fffff801`8e019366 00000000`c0000002 : 0xffff8908`00195030
    fffffd87`8181e7f8 ffff8908`00195030 : ffff8908`0abd8340 fffff801`8e019366 00000000`c0000002 ffff8908`00172000 : 0x54
    fffffd87`8181e800 ffff8908`0abd8340 : fffff801`8e019366 00000000`c0000002 ffff8908`00172000 ffff8908`0abd84a0 : 0xffff8908`00195030
    fffffd87`8181e808 fffff801`8e019366 : 00000000`c0000002 ffff8908`00172000 ffff8908`0abd84a0 ffff8908`0abd8340 : 0xffff8908`0abd8340
    fffffd87`8181e810 00000000`c0000002 : ffff8908`00172000 ffff8908`0abd84a0 ffff8908`0abd8340 00000000`0032c004 : nvlddmkm+0xd9366
    fffffd87`8181e818 ffff8908`00172000 : ffff8908`0abd84a0 ffff8908`0abd8340 00000000`0032c004 fffff801`6e431f39 : 0xc0000002
    fffffd87`8181e820 ffff8908`0abd84a0 : ffff8908`0abd8340 00000000`0032c004 fffff801`6e431f39 ffff8908`08074650 : 0xffff8908`00172000
    fffffd87`8181e828 ffff8908`0abd8340 : 00000000`0032c004 fffff801`6e431f39 ffff8908`08074650 ffff8908`00172000 : 0xffff8908`0abd84a0
    fffffd87`8181e830 00000000`0032c004 : fffff801`6e431f39 ffff8908`08074650 ffff8908`00172000 ffff8908`00195030 : 0xffff8908`0abd8340
    fffffd87`8181e838 fffff801`6e431f39 : ffff8908`08074650 ffff8908`00172000 ffff8908`00195030 fffffd87`8181e8e0 : 0x32c004
    fffffd87`8181e840 fffff801`8dfb2153 : 00000000`00000000 00000000`00000000 ffff8908`08074dc0 ffff8908`00172000 : nt!IofCallDriver+0x59
    fffffd87`8181e880 00000000`00000000 : 00000000`00000000 ffff8908`08074dc0 ffff8908`00172000 ffff8908`068b2000 : nvlddmkm+0x72153
    STACK_COMMAND:  .thread 0xffff8907f7ab9180 ; kb
    IMAGE_VERSION:  10.0.18362.387
    SYMBOL_NAME:  pci!PciBusInterface_GetBusData <PERF> (pci+0x0)+0
    FAILURE_BUCKET_ID:  0x9F_3_ACPI_pci!PciBusInterface_GetBusData__PERF__(pci+0x0)
    OSNAME:  Windows 10
    FAILURE_ID_HASH:  {3768e0cb-c0c4-138e-4d0b-a325e2d0952b}
    Followup:     MachineOwner

    • Edited by nunes99 Wednesday, October 2, 2019 1:24 PM
    Wednesday, October 2, 2019 1:23 PM
  • use "!devstack ffff8907f99ef060" to look which driver is blocking

    Wednesday, October 2, 2019 2:17 PM
  • ServiceName is "nvlddmkm"

    I was using the latest version available on the nvidia site for the mx 150, I went to the lenovo site and downloaded the driver with the old version, I will test to see if the problem still appears, because it did not always happen.


    EDIT: With this old driver I can hear the fan of the notebook, before I could not, thought he was in trouble, was very weak. Weird. What will be the reason?
    • Edited by nunes99 Wednesday, October 2, 2019 6:00 PM
    Wednesday, October 2, 2019 5:44 PM
  • ServiceName is "nvlddmkm"

    I was using the latest version available on the nvidia site for the mx 150, I went to the lenovo site and downloaded the driver with the old version, I will test to see if the problem still appears, because it did not always happen.


    EDIT: With this old driver I can hear the fan of the notebook, before I could not, thought he was in trouble, was very weak. Weird. What will be the reason?

    Maybe the new driver provided some optimization to the fans' usage.
    If the video driver is responsible for those faults, you should report the problem to Lenovo and ask for support.


    Luigi Bruno

    Wednesday, October 2, 2019 7:30 PM