Windows error 0x0000009F, 159

Detailed Error Information

BAD_THREADID_ADDR[1]

MessageThe address for the thread ID is not correct.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x8007009F.

DRIVER_POWER_STATE_FAILURE[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code159 (0x009f)

Possible solutions

3

Windows 10 - DRIVER_POWER_STATE_FAILURE BSOD

memory
drivers
windows-10
crash
bsod

By analyzing the dump I see that the crash is caused by the nVIDIA GPU driver nvlddmkm.sys:

*******************************************************************************
*                                                                             *
*                        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: ffffe001e655f060, Physical Device Object of the stack
Arg3: ffffd000345aace0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001e724c730, The blocked IRP

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

Implicit thread is now ffffe001`e44ab040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  G551JW

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  G551JW.202

BIOS_DATE:  01/16/2015

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  G551JW

BASEBOARD_VERSION:  1.0       

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  e44ab040

CPU_COUNT: 8

CPU_MHZ: a22

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  SearchUI.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

DPC_STACK_BASE:  FFFFD000345AAFB0

LAST_CONTROL_TRANSFER:  from fffff8032a0c7dca to fffff8032a1bd1f6

STACK_TEXT:  
00 nt!KiSwapContext
01 nt!KiSwapThread
02 nt!KiCommitThreadWait
03 nt!KeWaitForSingleObject
04 dxgkrnl!DpiFdoHandleDevicePower
05 dxgkrnl!DpiDispatchPower
06 nvlddmkm
07 0x0
08 0x0
09 0x0
0a 0x0

5: kd> !podev ffffe001e655f060
Device object is for:
  DriverObject e6561720
Current Irp 00000000 RefCount 0 Type 00000023 AttachedDev ffffe001e6560210 DevFlags 00001040
Device queue is not busy.
Device Object Extension: ffffe001e655f7b0:
PowerFlags: 00000040 =>SystemState=0 DeviceState=4
Dope: 00000000:
5: kd> !devstack ffffe001e6560210
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001e4448140  \Driver\nvlddmkm   ffffe001e4448290  InfoMask field not found for _OBJECT_HEADER at ffffe001e4448110

> ffffe001e6560210  \Driver\ACPI       ffffe001e6498470  InfoMask field not found for _OBJECT_HEADER at ffffe001e65601e0

  ffffe001e655f060  \Driver\pci        ffffe001e655f1b0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe001e655e010 :
  DeviceInst is "PCI\VEN_10DE&DEV_139B&SUBSYS_185D1043&REV_A2\4&819bc9d&0&0008"
  ServiceName is "nvlddmkm"

Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp:        Sat Nov 14 06:44:20 2015 

This is the driver for your NVIDIA GeForce GTX 960M (PCI\VEN_10DE&DEV_139B). Disable the PCIe power savings in the Windows power saving options. Also try the latest nVIDIA driver. Maybe the driver also fixes your 960M crashes. Because I see SearchUI.exe as process, open the nVIDIA control panel and select that SearchUI.exe runs on the Intel HD graphic and not on the nvidia card.

answered on Super User Dec 5, 2015 by magicandre1981 • edited Jun 26, 2017 by magicandre1981
3

Unable to wake computer from sleep/hibernate

windows
windows-8.1
sleep
hibernate
hybrid-sleep

ok, the dumps shows that the tunnel.sys causes it:

*******************************************************************************
*                                                                             *
*                        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: ffffe000b9f6f9c0, Physical Device Object of the stack
Arg3: ffffd0014dcfacb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000c1f23e10, The blocked IRP


6: kd> !irp ffffe000c1f23e10
Irp is active with 3 stacks 2 is current (= 0xffffe000c1f23f28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe000bc345050 00000000 fffff802df7edb3c-ffffe000afb149c0 Success Error Cancel pending
           \Driver\tunnel   nt!PopSystemIrpCompletion
            Args: 00014400 00000000 00000004 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe000afb149c0    

            Args: 00000000 00000000 00000000 00000000

This is a known issue in Windows 8.1, that Microsoft already tried to fix. But I can see that you have the fix already installed. Your tunnel.sys has the version 6.3.9600.18048. You should contact the Microsoft support and tell them that the update doesn't fix it.

answered on Super User Jan 25, 2016 by magicandre1981
3

Windows 7 BSOD on hybernate

windows
bsod

0x9f is DRIVER_POWER_STATE_FAILURE.

0x3 as the first parameter means "A device object has been blocking an IRP for too long a time."

It looks like one of your drivers is buggy.

answered on Super User Feb 7, 2010 by (unknown user)
3

How to find out what causes crashes in Windows 10 during sleep or hibernation (DRIVER_POWER_STATE_FAILURE, ntoskrnl.exe+14d220)?

windows
drivers
sleep
windows-10
windows-10-upgrade

the crash seams to be caused by the driver btfilter.sys (Atheros Bluetooth driver):

*******************************************************************************
*                                                                             *
*                        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: ffffe0012795a060, Physical Device Object of the stack
    Arg3: ffffd001024ab990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00133776980, The blocked IRP

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


    SYSTEM_SKU:  PSKK6E

    SYSTEM_VERSION:  PSKK6E-02H05KCZ

    BIOS_DATE:  09/19/2014

    BASEBOARD_PRODUCT:  VG10S

    BASEBOARD_VERSION:  To be filled by O.E.M.

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    STACK_TEXT:  
    00 nt!KeBugCheckEx
    01 nt!PopIrpWatchdogBugcheck
    02 nt!PopIrpWatchdog
    03 nt!KiRetireDpcList
    04 nt!KiIdleLoop


    IMAGE_VERSION:  10.0.10240.16401

    FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_btfilter_IMAGE_usbhub.sys

    5: kd> !irp ffffe00133776980
    Irp is active with 15 stacks 14 is current (= 0xffffe00133776df8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context

     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    

                Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffffe0012792b030 00000000 fffff800907ecd40-ffffe0012ec4f7d0 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\btfilter.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for btfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
     \Driver\BtFilter   nt!PopSystemIrpCompletion
                Args: 00014400 00000000 00000004 00000002
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-ffffe0012ec4f7d0    

                Args: 00000000 00000000 00000000 00000000

        Loaded symbol image file: btfilter.sys
        Image path: \SystemRoot\system32\DRIVERS\btfilter.sys
        Image name: btfilter.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Aug 09 11:41:27 2013 

the driver is 2 years old. Look for a driver update or remove it and look if the generic Windows driver works.

answered on Super User Aug 11, 2015 by magicandre1981
2

Find device in Windows based on Physical Device Object (PDO) identifiers

windows-7
drivers

Yes. You can trace this bugcheck.

1. What you need is to first download Windows debugging tools from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8279

2. Next you need the appropriate Windows 7 Debugging Symbols (You want the 'retail' version. Not the 'checked' version: http://msdn.microsoft.com/en-us/windows/hardware/gg463028

3. Install the Debugging tools normally. Install the Debugging symbols to a new folder named c:\Symbols. When done with both, open up Debugging Tools for Windows, go to the File Menu and select "Symbol File Path". Replace whatever is in the box with this string (replacing drive letter and symbols path, if you choose to install the symbols to somewhere else):

srv*c:\symbols*http://msdl.microsoft.com/download/symbols

4. Next, with Windows Explorer go to c:\Windows\Minidump (assuming C: is where you installed windows). Inside you'll find the so called minidump files. These contain the information on your BSODS. One file per BSOD named after the date of the BSOD.

5. Drag the last one to your Debugging Tools for Windows empty grey area (or open it through the file menu). The Debugger will start analyzing it, after which you can see a !analyze -v link you can click.

6. Click it and you'll get the bugcheck report. Update your question with the results from this analize -v and many of us in here will be able to hint you into what might be the problem.


An example of what you may want to paste into your question above is given below (from one of my own minidump files from early this year when I found out I had faulty RAM:

BugCheck 1000008E, {c0000005, 940c23de, abb34b0c, 0}

Probably caused by : Npfs.SYS ( Npfs!NpRemoveAllAttributesFromList+14 )

Followup: MachineOwner

[..]

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
[...]
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 940c23de, The address that the exception occurred at
Arg3: abb34b0c, Trap Frame
Arg4: 00000000

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Npfs!NpRemoveAllAttributesFromList+14
940c23de 897004          mov     dword ptr [eax+4],esi
answered on Super User Jul 7, 2011 by A Dwarf
2

Windows 7 BSOD on hibernate

windows
bsod
minidumps

Some general advice:

  1. Make sure nothing else is connected to the laptop at all, no USB, no VGA, no nothing. Just making sure...
  2. See if your laptop has the latest BIOS, and if it does not, flash it to the latest BIOS version.

As far as troubleshooting minidumps, the official Microsoft reference seems to be:

http://support.microsoft.com/kb/315271

debugging tools must be downloaded from:

http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx

I also found a reference to WhoCrashed which, given the minidump as input, will supposedly tell you which driver is most likely responsible for it. I have not used this myself but it looks reputable. Might be easier..

answered on Super User Feb 9, 2010 by Jeff Atwood
1

Failure with booting of qemu_x86_defconfig in buildroot-2011.11?

linux-kernel
qemu
i386
buildroot

Back in late 2011, we had problems with the IA32 CodeSourcery toolchain, but they should now be fixed.

answered on Stack Overflow May 11, 2012 by Thomas Petazzoni
1

Annoying bugcheck - prevents laptop from going to sleep

windows-8
macbook-pro
bsod

Your Windows crashes because of the DRIVER_POWER_STATE_FAILURE (9f) bugcheck. WinDbg tells me that the MS PPP Framing Driver (ndiswan.sys) causes the issue.

Which Wide Area Network do you use?

answered on Super User Apr 28, 2013 by magicandre1981
1

BSOD error on Windows 7 ultimate

windows-7
bsod

I've seen this a dozen times and it always was due to outdated or incompatibile drivers. It never had ANYTHING to do with power, sleep mode, etc.

1). Use Microsoft Windows Update, check all critical and look in Optional for driver updates. Reboot.

2). Go to the manufacturer's website and see if they provide Windows 7 drivers. Update everything unless you specifically remember updating that driver with the Windows Update program.

3). If your manufacturer does not offer Windows 7 drivers, there are a couple tricks. You can either google the name of the computer and look for people who have released Windows 7 drivers; visit each component manufacturer's website (nvidia, intel, broadcom etc.) individually and download the drivers for your device; or use your manufacturer's windows vista drivers and pray for the best.

answered on Super User Apr 18, 2010 by James Watt
0

Failure with booting of qemu_x86_defconfig in buildroot-2011.11?

linux-kernel
qemu
i386
buildroot

Try to use:

root=/dev/sda1

in boot script as sda1 corresponds to the first partition of the sda.

answered on Stack Overflow Apr 23, 2012 by Abhisheietk • edited Oct 29, 2012 by Luksprog
0

Failure with booting of qemu_x86_defconfig in buildroot-2011.11?

linux-kernel
qemu
i386
buildroot

Have you tried to disable SELinux as mentioned in this thread?? Perhaps it might fix it.

answered on Stack Overflow Nov 3, 2014 by HighOnMeat • edited May 23, 2017 by Community
0

Lenovo X220T bluescreen with problems shutting down

windows-8
bsod

After examining the memory dump, it was determined that the Lenovo OEM Broadcom Bluetooth driver (btwampfl.sys) was taking the PnP lock and never releasing it. Updating the Bluetooth adapter to the latest Windows Update drivers resolved the issue. Full stack trace below:

Call Site
-----------------------------------
nt!KiSwapContext+0x76
nt!KiCommitThreadWait+0x23c
nt!KeDelayExecutionThread+0x1d3
btwampfl+0xa5c6
btwampfl+0xa1f7
bthport!BthHandleRemoveDevice+0xdf
bthport!BthHandlePnp+0xea
bthport!BthDispatchPnp+0x68
nt!IopSynchronousCall+0xc7
nt!IopRemoveDevice+0x100
nt!PnpRemoveLockedDeviceNode+0x22d
nt!PnpDeleteLockedDeviceNode+0x78
nt!PnpDeleteLockedDeviceNodes+0xa1
nt!PnpDelayedRemoveWorker+0x80
nt!ExpWorkerThread+0x142
nt!PspSystemThreadStartup+0x59
nt!KiStartSystemThread+0x16
answered on Server Fault Feb 6, 2013 by Mitch
0

Projection matrix causing inaccuracy in clip-space depth calculation?

c#
directx
direct3d
hlsl
slimdx

Your depth buffer always has the same value written into it because you have your projection matrix wrong. The value that actually gets written is the w-value so you need to juggle your matrix around a bit.

The DirectX documentation gives a good explanation of the perspective transform.

Basically your matrix should be as follows

W, 0, 0, 0
0, H, 0, 0
0, 0, Q, 1
0, 0, P, 0

Where

W = 1.0f / tanf( fovHoriz / 2 );
H = 1.0f / tanf( fovVert  / 2 );
Q = zFar / (zFar - zNear);
P = -Q * zNear;
answered on Stack Overflow May 20, 2013 by Goz • edited May 23, 2017 by Community
0

Bluescreen after sleep caused by asmthub3

windows-10
drivers
bsod
usb-3

Since Windows 8, Microsoft includes a generic USB 3.0 driver, so there is no need to install 3rd party drivers (only if the generic driver doesn't support the chip like old Fresco Logic 1000 chips). So go to device manager

enter image description here

and uninstall the ASmedia devices

enter image description here

and install the default Windows drivers (shows up as (Microsoft) at the end)

enter image description here

answered on Super User Apr 19, 2016 by magicandre1981
0

Bluescreen when i restart windows 10

windows-10
bsod

ok, the drivers ewusbwwan.sys (Huawei driver) and NetBalancer driver nbdrv.sys seem to cause it.

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe00178ea7800, The thread currently holding on to the Pnp lock.
Arg4: ffffd0007df3f9b0, nt!TRIAGE_9F_PNP on Win7 and higher

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

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
00 nt!KiSwapContext
01 nt!KiSwapThread
02 nt!KiCommitThreadWait
03 nt!KeDelayExecutionThread
04 nbdrv
05 0x0
06 0x0


BUCKET_ID:  0x9F_4_ewusbwwan_IMAGE_usbccgp.sys

PRIMARY_PROBLEM_CLASS:  0x9F_4_ewusbwwan_IMAGE_usbccgp.sys

BUILDDATESTAMP_STR:  150709-1700

BUILDLAB_STR:  th1

BUILDOSVER_STR:  10.0.10240.16384.amd64fre.th1.150709-1700

FAILURE_ID_HASH_STRING:  km:0x9f_4_ewusbwwan_image_usbccgp.sys


    Image path: \SystemRoot\system32\DRIVERS\nbdrv.sys
    Image name: nbdrv.sys
    Timestamp:        Fri Apr 19 21:13:24 2013 (51719754)

    Image path: \SystemRoot\System32\drivers\ewusbwwan.sys
    Image name: ewusbwwan.sys
    Timestamp:        Thu Mar 21 02:57:34 2013 (514A690E)

So the crash is network related. remove all 3rd party tools which install network drivers (Netbalancer, AV suite, firewall, Virtual Machine tools like Vmware or VirtualBox), update the Huawei driver and try again.

The TH1 means you try to install the July 2015 version. Get the 1511 ISO, mount it in Win7, run setup.exe and select "upgrade" to go to the November 2015 version of Windows 10.

answered on Super User Dec 1, 2015 by magicandre1981
0

BSOD Asus G750JM Win8.1

windows
windows-8
drivers
windows-8.1
bsod

Removing the bloatware and enabling the verifier is what fixed it for me. Closing question.

answered on Super User Aug 30, 2014 by beardedeagle
0

Is a STOP 0x0000009F (DRIVER_POWER_STATE_FAILURE) BSOD a sign of hardware trouble?

windows-7
windows-vista
bsod

Such a problem can be explained in 2 ways: hardware or software.

However, in your particular case I understand that you never had these problems in Vista, that you didn't touch Vista since, but that the same problem is now occurring in Vista.

It is very important that there were no driver updates to Vista, but that it's now BSODing. As Vista and Win7 have the same driver base, if Windows Update was set to auto-update, then this pollutes my above logic. (please confirm that there weren't.)

For me, this is proof enough that the problem is hardware, enough to activate the warranty.

Just to make sure, you may have a look at the Event Log, run memtest86+, and install some monitoring tools:

GPU-Z will tell you the temperature of the video card
SpeedFan for the CPU
Active@ Hard Disk Monitor for the hard disk.

answered on Super User Dec 24, 2009 by harrymc
0

Find device in Windows based on Physical Device Object (PDO) identifiers

windows-7
drivers

When you loaded the dmp in Windbg and loaded the symbols, run !podev 0xfffffa800a21f060 (address from argument 2: Arg2: fffffa800a21f060, Physical Device Object of the stack).

This dumps the Physical Device Object (PDO).

This

X64_0x9F_3_AiCharger_IMAGE_usbhub.sys

tells me that the ASUS Ai Charger driver caused it.

answered on Super User Dec 14, 2016 by magicandre1981 • edited May 23, 2017 by Community
0

BSOD error on Windows 7 ultimate

windows-7
bsod

I have the same issue on my pc, but doubt its the power supply.

My guess is its related to sleep mode, as I never have issues when working, only when I leave computer - I come back and most of the time I have crash problem.

I am going to try to keep power onto various things and see if that fixes it.

answered on Super User Dec 31, 2009 by (unknown user) • edited Feb 4, 2010 by Jared Harley
0

Windows 7 BSOD on hibernate

windows
bsod
minidumps

That is exactly what happens to me. When I try to come out of hibernation, it will bluescreen. It so far has happened only when I have let it hibernate into the next day.

answered on Super User Feb 11, 2010 by (unknown user)
0

Is there Linux kernel version limitation for virtual machines to run on GCE?

migration
google-cloud-platform
google-compute-engine

I've found this three links that can be usefull for you regarding your concerns:

  1. Google Cloud Platform Compute Engine Limitations
  2. Building Custom Operating Systems
  3. Best practises when migrating
answered on Stack Overflow Feb 7, 2018 by Thrahir
0

Is there Linux kernel version limitation for virtual machines to run on GCE?

migration
google-cloud-platform
google-compute-engine

It appears that you're running a 2.6.32-71 kernel.

Unfortunately, this kernel is too old and isn't supported by GCP. For 2.6.32 RHEL/CentOS kernels, GCP only supports 2.6.32-279 or higher.

answered on Stack Overflow Feb 7, 2018 by Leonid Feinberg
0

Google compute engine boot fails after hardware upgrade to Hashwell

centos
google-compute-engine

I suggest at first to follow standard troubleshooting steps to validate the disk's filesystem as documented.

Then you can try to snapshot the disk and create a new instance with boot disk from snapshot to avoid exclude a disk UUID conflict.

Finally you can try to attach the disk to recover the files to a brand new instance as I suggested in my previous comment.

If you can not validate the filesystem as per troubleshooting guide the data is most probably lost and nothing more can be done to recover it.

Please note as a good practice to take care of either periodic snapshot, GCS differentiual backup or other replication method.

Thank you.
Sincerely,
P.

answered on Stack Overflow Apr 30, 2015 by Paolo P.
0

BSOD - DRIVER_POWER_STATE_ERROR 0x0000009f ntoskrnl.exe - Windows 10

windows-10
bsod
ntoskrnl.exe

Looking at the dump (!irp command with value from parameter 4 (ffffe001dbbf8c10)) shows that the Synaptic Touchpad driver causes the crash:

7: kd> !irp ffffe001dbbf8c10
Irp is active with 9 stacks 6 is current (= 0xffffe001dbbf8e48)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffffe001d63a4640 00000000 fffff801a3d41ec0-00000000    
           \Driver\ACPI i8042prt!I8xPowerUpToD0Complete
            Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe001d87de9f0 00000000 00000000-00000000    pending
           \Driver\i8042prt
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe001d76b2e20 00000000 fffff801a3e11060-00000000 Success Error Cancel pending
          *** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
 \Driver\SynTP  kbdclass!KeyboardClassPowerComplete
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe001d8619cc0 00000000 fffff8023a51d418-ffffe001d5af5940 Success Error Cancel pending
           \Driver\kbdclass nt!PopRequestCompletion
            Args: 00051100 00000001 00000001 00000002
 [N/A(0), N/A(0)]

Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
Image name: SynTP.sys
Timestamp:        Fri Apr 15 03:46:43 2016 

The driver is relatively new April 2016), try to find a newer driver or install older drivers and disable the automatic driver update.

answered on Super User Jul 31, 2016 by magicandre1981 • edited Mar 20, 2017 by Community

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0