Page 1 of 2 12 LastLast

  1. Joined : Oct 2015
    Posts : 52
    Windows 10
       05 Jan 2016 #1

    Constant crashes&BSODs on MS Surface Pro 3: DRIVER_POWER_STATE_FAILURE


    Since about 2 weeks I have constant (i.e. 5-10 times per day) "black crashes" and BSODs on my MS Surface Pro 3 - roughly in 50%/50% mixture.

    "Black crash" means: the screen suddenly goes dark followed by the appearance of the "Surface" Boot logo. But these "self-reboots" always hang, i.e. there is never any further progress, no circling dots appear, nothing. I then always first have to power down the system (i.e. do a hard-reset by pressing the power button for 15-20 seconds until the system switches fully off) and then I can power on and reboot again.
    In the other maybe 50% I get a BSOD which states that this is due to a DRIVER_POWER_STATE_FAILURE. In these cases the system creates a minidump and then reboots properly.

    Both, crashes and BSODs, always happen while the system is idle, i.e. typically a few minutes after leaving the system idling (e.g. just putting it on the table without any further interaction, no activity, no download, no mouse movements, just idling). Then it takes typically 3-5 minutes and I get either a "black crash" or a BSOD. Of course any unsaved work is then lost... :-(

    I scanned the minidumps using the WhoCrashed utility, but the results all state the same.:
    -------
    On Tue 05.01.2016 20:59:32 GMT your computer crashed
    crash dump file:
    C:\WINDOWS\Minidump\010516-8359-01.dmp
    This was probably caused by the following module:
    ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code:
    0x9F (0x3, 0xFFFFE000B19B6060, 0xFFFFD000DD674990, 0xFFFFE000B4CDAAB0)
    Error:
    DRIVER_POWER_STATE_FAILURE
    Bug check description:
    This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel.
    Possibly this problem is caused by another driver that cannot be identified at this time.

    -------

    I also searched extensively on the net but haven't found any useful explanation or advice what one could do to fix such a recurring DRIVER_POWER_STATE_FAILURE (other than re-installing the system from scratch which will clearly be my very last resort only, since I have many apps installed).

    I upgraded from Win8.1 to Windows 10 about 4 weeks ago without any problem. The first 2 weeks everything seemed to be running smoothly. But since then these crashes suddenly started (I don't know whether they were started by some Windows update, since once doesn't see anymore, if and when the system auto-updates due to Windows 10 new update approach). Unfortunately I didn't set any restore point yet after the system upgrade.

    Another observation - not sure whether it has to do with the above but I strongly suspect so: I noticed that the system cannot restart any more. If I trigger a restart the system first behaves normal as if it were restarting up to the point where the screen goes black. But then the screen remains black (i.e. no boot logo appears, nothing happens) but the system also does not switch fully off (e.g. the fan keeps running and one can sense the vibrator reacting to presses of the windows button).
    Also here, I then always first have to hard-reset the device and only then I can power on again and reboot.

    Any ideas or advice?

    BTW: I just located the update history.
    There are 3 entries - see below. I suspect it was the bottom-most which causes these issues. Can one unroll that one? Is it possible to uninstall an update that is NOT the last one? I have never done that before...


    Update history:

    Update for Internet Explorer Flash Player for Windows 10 Version 1511 for x64-based Systems (KB3133431)
    Successfully installed on 05.01.2016 (i.e. today)

    Security Update for Internet Explorer Flash Player for Windows 10 Version 1511 for x64-based Systems (KB3132372)
    Successfully installed on 30.12.2015

    Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3124200)
    Successfully installed on 18.12.2015
      My System SpecsSystem Spec


  2. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       07 Jan 2016 #2
      My System SpecsSystem Spec


  3. Joined : Oct 2015
    Posts : 52
    Windows 10
       14 Jan 2016 #3

    Unfortunately the dmcollector does not work!
    It first collects maybe 25 .dmp files, then generates misc. reports etc. (see the screenshots) and eventually reports that it has now created a .zip on the desktop (which it has), but that .zip file (attached) has a length of mere 22 Bytes (!), i.e. it is empty!
    Attachment 58749
    Attachment 58750
    Attachment 58751

    What am I missing? Why is this tool not working?
    BTW: I *am* administrator on this box!

    Any further suggestion?
      My System SpecsSystem Spec


  4. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       14 Jan 2016 #4

    Please try to move the minidumps to a different location and zip them up, you might need to use a 3rd party uploader to upload them.
    After the minidumps have moved and the minidump folder is empty, try to run the dm log collector again.
      My System SpecsSystem Spec


  5. Joined : Oct 2015
    Posts : 52
    Windows 10
       14 Jan 2016 #5

    Did as instructed and now the .zip looks MUCH better!
    Attachment 58798
    and here the .dmp files zipped up separately:
    Attachment 58799

    BTW: I meanwhile observed, that the crashes seem to happen ONLY, when the device is on battery (i.e. as long as it runs from the power supply everything seem to work fine) and it must have been switched off at least once before. I never witnessed a crash right after rebooting.
    So, it could be, that some driver is not properly re-initialized when the device wakes up from being "off" (or actually from: "connected standby"). Just in case this helps...
      My System SpecsSystem Spec


  6. Joined : Jan 2016
    Posts : 516
    windows 10 Pro
       14 Jan 2016 #6

    The dumpfiles flag
    Code:
     *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, ffffe000a0af3060, ffffd001521f8990, ffffe000af93a8e0}
    Probably caused by : mshidkmdf.sys
    Unable to load image \SystemRoot\System32\drivers\SurfacePenDriver.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SurfacePenDriver.sys
    *** ERROR: Module load completed but symbols could not be loaded for SurfacePenDriver.sys
     \Driver\SurfacePenDriver nt!PopRequestCompletion
       Args: 00000000 00000001 00000004 00000000
    The Bsod are probably caused by SurfacePendriver
    SurfacePenDriver Thu Oct 22 19:13:44 2015

    Maybe your driver is corrupted.
    The driverpackage for surfacepro 3 and install info here https://www.microsoft.com/en-us/down....aspx?id=38826
      My System SpecsSystem Spec


  7. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       14 Jan 2016 #7

    lifetec said: View Post
    The dumpfiles flag
    Code:
     *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, ffffe000a0af3060, ffffd001521f8990, ffffe000af93a8e0}
    Probably caused by : mshidkmdf.sys
    Unable to load image \SystemRoot\System32\drivers\SurfacePenDriver.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SurfacePenDriver.sys
    *** ERROR: Module load completed but symbols could not be loaded for SurfacePenDriver.sys
     \Driver\SurfacePenDriver nt!PopRequestCompletion
       Args: 00000000 00000001 00000004 00000000
    The Bsod are probably caused by SurfacePendriver
    SurfacePenDriver Thu Oct 22 19:13:44 2015

    Maybe your driver is corrupted.
    The driverpackage for surfacepro 3 and install info here https://www.microsoft.com/en-us/down....aspx?id=38826
    That is the analyse and correct, but what I'm worried about is that there are so many outdated drivers.
    Below is a list of the drivers, all of them are outdated, some may not be possible to update.
    My guess is that most drivers are used by software.
    Code:
    tifsfilt.sys Wed Aug 29 14:37:29 2007 (46D56889) 
    timntr.sys Wed Aug 29 14:38:23 2007 (46D568BF) 
    vcd10bus.sys Mon Jun 16 09:36:31 2008 (485617FF) 
    azvusb.sys Thu Aug 13 13:29:32 2009 (4A83F91C) 
    jnprvamgr.sys Wed Nov 18 18:39:04 2009 (4B043138) 
    virtualnet.sys Sun Mar 14 22:23:13 2010 (4B9D53C1) 
    vfilter.sys Fri Dec 17 06:42:25 2010 (4D0AF841) 
    TSKNFA00.SYS Sun Jan 29 17:17:09 2012 (4F257105) 
    uimx64.sys Thu Nov 22 13:07:52 2012 (50AE1598) 
    UimFIO.SYS Thu Nov 22 13:07:54 2012 (50AE159A) 
    Uim_IMx64.sys Thu Nov 22 13:07:58 2012 (50AE159E) 
    uim_vimx64.sys Thu Nov 22 13:08:04 2012 (50AE15A4) 
    vdrv1000.sys Thu Dec 6 11:09:22 2012 (50C06ED2) 
    npf.sys Fri Mar 1 02:31:24 2013 (513004EC) 
    TeeDriverx64.sys Wed Nov 27 18:56:32 2013 (52963250) 
    SurfaceDisplayCalibration.sys Fri May 2 21:16:48 2014 (5363EF20) 
    SurfaceAccessoryDevice.sys Fri May 23 06:54:43 2014 (537ED493) 
    TrueColor.sys Tue Jun 17 07:57:42 2014 (539FD8D6) 
    VMNET.SYS Sun Jul 27 15:30:27 2014 (53D4FEF3) 
    vmnetadapter.sys Sun Jul 27 15:30:30 2014 (53D4FEF6) 
    vmnetbridge.sys Sun Jul 27 15:30:32 2014 (53D4FEF8) 
    file_tracker.sys Thu Sep 4 14:49:39 2014 (54085FE3) 
    vmci.sys Fri Sep 5 04:11:32 2014 (54091BD4) 
    vsock.sys Fri Sep 5 04:12:05 2014 (54091BF5) 
    SurfacePciController.sys Sat Sep 27 12:32:23 2014 (54269237) 
    jnprns.sys Thu Oct 30 19:38:20 2014 (5452859C) 
    fltsrv.sys Tue Nov 11 13:01:53 2014 (5461FAB1) 
    snapman.sys Wed Nov 12 11:54:05 2014 (54633C4D) 
    SurfaceCapacitiveHomeButton.sys Tue Nov 25 20:47:32 2014 (5474DCD4) 
    SurfaceIntegrationDriver.sys Tue Dec 2 06:03:51 2014 (547D4837) 
    
    http://www.carrona.org/drivers/driver.php?id=tifsfilt.sys 
    http://www.carrona.org/drivers/driver.php?id=timntr.sys 
    http://www.carrona.org/drivers/driver.php?id=vcd10bus.sys 
    http://www.carrona.org/drivers/driver.php?id=azvusb.sys 
    jnprvamgr.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    http://www.carrona.org/drivers/driver.php?id=virtualnet.sys 
    http://www.carrona.org/drivers/driver.php?id=vfilter.sys 
    http://www.carrona.org/drivers/driver.php?id=TSKNFA00.SYS 
    http://www.carrona.org/drivers/driver.php?id=uimx64.sys 
    http://www.carrona.org/drivers/driver.php?id=UimFIO.SYS 
    http://www.carrona.org/drivers/driver.php?id=Uim_IMx64.sys 
    http://www.carrona.org/drivers/driver.php?id=uim_vimx64.sys 
    http://www.carrona.org/drivers/driver.php?id=vdrv1000.sys 
    http://www.carrona.org/drivers/driver.php?id=npf.sys 
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys 
    SurfaceDisplayCalibration.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    SurfaceAccessoryDevice.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    TrueColor.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS 
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys 
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys 
    http://www.carrona.org/drivers/driver.php?id=file_tracker.sys 
    http://www.carrona.org/drivers/driver.php?id=vmci.sys 
    http://www.carrona.org/drivers/driver.php?id=vsock.sys 
    SurfacePciController.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    jnprns.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    http://www.carrona.org/drivers/driver.php?id=fltsrv.sys 
    http://www.carrona.org/drivers/driver.php?id=snapman.sys 
    SurfaceCapacitiveHomeButton.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. 
    SurfaceIntegrationDriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
      My System SpecsSystem Spec


  8. Joined : Oct 2015
    Posts : 52
    Windows 10
       14 Jan 2016 #8

    Thanks for the analysis! I highly appreciate it!
    I already had a suspicion re. the PenDriver but then didn't follow up on that.
    I had indeed downloaded and installed the latest driver version from the Surface Pro 3 download page shortly before Christmas (at about the same time when these BSODs started) since I had hoped that the latest pen driver would enable the lower part of the dialog of the "Surface" app where one can configure the pen button assignment (something I badly want to change but can not with the current Surface pen config app). Since the screenshot of the app in the MS Store suggests that the app allows to do that I thought that maybe my pen driver is outdated, so I went and downloaded the latest version and (re-)installed that.

    But that did not seem to have any effect at all. So my suspicion thus went more to the 1511 update that happend around the same time. But maybe the driver install indeed *did* have an effect! :-(

    I'll try to de-install and re-install that driver. I'll let you know whether that helped...
    Thanks!
      My System SpecsSystem Spec


  9. Joined : Oct 2015
    Posts : 52
    Windows 10
       16 Jan 2016 #9

    I re-installed the Surface Pro 3 pen drivers ("Surface Pen" and "SrufacePenSettingsDriver") - no change, still BSODs.
    I then did a full re-install of ALL Surface Pro 3 drivers using SurfacePro3_Win10_151026_2.msi - still the same: less than 10 minutes after detaching the device from power I get a BSOD! %$#@!

    I then tried to first REALLY get rid of those (presumably corrupt) pen drivers with the intention to re-install them afterwards: the drive "Surface Pen" was easy to uninstall: Right-click --> uninstall --> OK - gone.B
    But uninstalling the driver "Surface Pen Settings" seems impossible: it shows "uninstalling devices..." forever and never reaches an end.
    I assume that's why also re-installing the driver didn't change anything...

    How can I uninstall this darn driver? Is there some "force uninstall" option or method anywhere?
    How does one uninstall a driver anyway, when it's uninstall-option doesn't work?
    Last edited by mmo; 17 Jan 2016 at 15:55.
      My System SpecsSystem Spec


  10. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       17 Jan 2016 #10

    By uninstalling the software that comes with it usually.
      My System SpecsSystem Spec


 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Solved New Win 10 Install: Constant BSODs
Hi all, I installed windows 10 on a brand new system I just built, and I'm getting constant BSODs. Initially I'll get a "PAGE_FAULT_IN_NONPAGED_AREA" or RQL_NOT_LESS_OR_EQUAL". The system will reboot and give me a "MEMORY_MANAGEMENT"error on...
BSOD Crashes and Debugging
Constant BSODs with a variety of error messages
Hi everyone, I built my computer a couple of months ago and everything was fine, however AMD released this Crimson software and after that everything went to garbage. My computer would start BSODing with a variety of errors. I've seen: ...
BSOD Crashes and Debugging
Just replaced AMD 6870 with AMD R9 390 getting constant BSODs
When I start some games, I get BSOD "CRITICAL_PROCESS_DIED" and have to manually restart. Usually happens within 2 minutes of starting the game, often sooner. I've got all the recent drivers, Windows 10 home, X58 Pro-E (MS-7522) motherboard, AMD...
BSOD Crashes and Debugging
Random and constant BSODs, nearly all KERNEL_SECURITY_CHECK_FAILURE
Alright, so I'm at a loss here. I just put together this PC last week, and everything was working great until I decided to upgrade to Windows 10. I started having issues yesterday, when my PC randomly crashed with the error message...
BSOD Crashes and Debugging
Solved Constant BSODS After getting new parts.
So here is my story. I had an old PC with a first Gen i5 and some other parts and-... Well long story short I replaced my mobo, Processor and video card. Didnt get bluescreens till I replaced the parts. I did memcheck and the mem comes up clear, I...
BSOD Crashes and Debugging
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 00:11.
Find Us
Twitter Facebook Google+



Windows 10 Forums