Windows 8 and 8.1 Forums


Surface Pro 3 BSOD overnight in docking station

  1. #1


    Posts : 6
    Windows 8.1

    Surface Pro 3 BSOD overnight in docking station


    Hi,
    I use Surface Pro 3 at work with a docking station and 2 external monitors. I logoff from my enterprise network when I leave work. For the past couple of weeks, I have been noticing that when I return next morning, the Surface Pro 3 has shut down. The event log shows that there was an unexpected shutdown around 2 - 3 am each day. I looked at the minidump and did does not have much information other that DRIVER__POWER_STATE_FAILURE error.
    The Surface Pro 3 uses wired network when it's in the dock. I disabled sleep a couple of days ago, so that the Surface Pro 3 is never sleeps when on power, but still there's BSOD overnight.

    Could please analyze the logs let me know which driver is failing?

    Thanks
    -Neeraj

      My System SpecsSystem Spec

  2. #2



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Upload a new zip, this one is empty.
      My System SpecsSystem Spec

  3. #3


    Posts : 6
    Windows 8.1

    File Uploaded


    Hi,
    Not sure why DM Log Collector is creating empty Zip file. So I copied the SFDebug folder into the empty zip file and here it is attached.

    Please let me know the results of the analysis.

    Thanks in advance
    -Neeraj
      My System SpecsSystem Spec

  4. #4



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Please check your manufacturer for driver updates for your network.
    Code:
    1: kd> !irp ffffe00085c13940
    Irp is active with 20 stacks 19 is current (= 0xffffe00085c13f20)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 ffffe00079bce050 00000000 fffff8005fdaa9dc-ffffe00081d2cb70 Success Error Cancel pending
    	      Unable to load image \SystemRoot\system32\DRIVERS\msu30x64w8.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for msu30x64w8.sys
    *** ERROR: Module load completed but symbols could not be loaded for msu30x64w8.sys
     \Driver\msu30x64w8	nt!PopRequestCompletion
    			Args: 00000000 00000001 00000004 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe00081d2cb70    
    
    			Args: 00000000 00000000 00000000 00000000
    
    Irp Extension present at 0xffffe00085c13fb0:
    
    	Activity ID: {00000000-0000-0000-0000-000000000000}
    1: kd> lmvm msu30x64w8
    start             end                 module name
    fffff800`9230e000 fffff800`9232d000   msu30x64w8 T (no symbols)           
        Loaded symbol image file: msu30x64w8.sys
        Image path: \SystemRoot\system32\DRIVERS\msu30x64w8.sys
        Image name: msu30x64w8.sys
        Timestamp:        Fri Jul 04 11:08:56 2014 (53B66F28)
        CheckSum:         0001C322
        ImageSize:        0001F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Is there anything on the surface that could cause the CPU to get this speed?
    Code:
    CPUID:        "Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz"
    MaxSpeed:     1900
    CurrentSpeed: 2494
      My System SpecsSystem Spec

  5. #5


    Posts : 6
    Windows 8.1


    Thanks for the detailed analysis and info axe0. This is very helpful.
    The network adapter is OEM from Microsoft. I checked the network adapter driver and it was the latest version. Regardless, I re-installed the driver. I will post most likely next week if the Surface Pro 3 rebooted overnight or not. (I am traveling over the weekend so will be carrying my Surface Pro 3 and it won't be sitting in the dock).

    Can you tell me when (date/time) did the Surface Pro3 overclock? May be I can look at the event logs to see what was going on then.

    Thanks again.
      My System SpecsSystem Spec

  6. #6



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    The overclocking is at time of the crashes, more detailed I can't be a.t.m. unfortunately
      My System SpecsSystem Spec

  7. #7


    Posts : 6
    Windows 8.1

    Overnight BSOD Again


    Hi,
    I updated the network driver per recommendation from previous email and there was no BSOD for a couple of days. But the Surface Pro 3 experienced BSOD again when left in the docking station overnight. I did an initial analysis of the minidump and the Parameter values were different than last week.

    I attaching the SFDebug from the dm_log_collector that I just ran. Could you please analyze and provide me any insights if the network driver is still the cause or there is some another driver that's failing?

    Thanks in advance
    -Neeraj
      My System SpecsSystem Spec

  8. #8



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    The same driver has been flagged
    Code:
    0: kd> !irp ffffe0009364f010
    Irp is active with 20 stacks 19 is current (= 0xffffe0009364f5f0)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 ffffe00085d1e050 00000000 fffff8011dba99dc-ffffe000884ea170 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\msu30x64w8.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for msu30x64w8.sys
    *** ERROR: Module load completed but symbols could not be loaded for msu30x64w8.sys
     \Driver\msu30x64w8    nt!PopRequestCompletion
                Args: 00000000 00000001 00000004 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe000884ea170    
    
                Args: 00000000 00000000 00000000 00000000
    
    Irp Extension present at 0xffffe0009364f680:
    but I also noticed
    Code:
    FAILURE_BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys
    The usbhub3.sys is a Windows USB driver.
    This means:
    • the USB drivers are corrupted,
    • the port is faulty
    • the connection of the attached device is faulty

    If any USB device is attached, please disconnect it while troubleshooting.
      My System SpecsSystem Spec

  9. #9


    Posts : 6
    Windows 8.1

    Changed Docking station but BSOD Happening again


    Hi Axe0,
    Thanks for the analysis from yesterday - really appreciate all your help. Based on your findings, I changed the docking station. I think the interrupts issue has been resolved - I did not see interrupts in the task manager as well as the CPU utilization was consistently at 1% - earlier it used to be at 30-35% with System Interrupts consuming most of it.
    However, the BSOD seems to have happened overnight again. So attached is the SFDebug again. I am leaning towards, bad docking station drivers (which I believe are actually USB drivers).

    I would appreciate if you can analyze the dump one more time and let me know what you find - I promise this would be the last time.

    Thanks again.

    -Neeraj
      My System SpecsSystem Spec

  10. #10



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Again a network driver have been flagged
    Code:
    0: kd> !irp ffffe000d5eeb940
    Irp is active with 20 stacks 19 is current (= 0xffffe000d5eebf20)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 ffffe000d47ee050 00000000 fffff8021b3a79dc-ffffe000d9d98590 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\msu30x64w8.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for msu30x64w8.sys
    *** ERROR: Module load completed but symbols could not be loaded for msu30x64w8.sys
     \Driver\msu30x64w8    nt!PopRequestCompletion
                Args: 00000000 00000001 00000004 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe000d9d98590    
    
                Args: 00000000 00000000 00000000 00000000
    
    Irp Extension present at 0xffffe000d5eebfb0:
    
        Activity ID: {00000000-0000-0000-0000-000000000000}
    0: kd> lmvm msu30x64w8
    start             end                 module name
    fffff800`a7f9b000 fffff800`a7fba000   msu30x64w8 T (no symbols)           
        Loaded symbol image file: msu30x64w8.sys
        Image path: \SystemRoot\system32\DRIVERS\msu30x64w8.sys
        Image name: msu30x64w8.sys
        Timestamp:        Fri Jul 04 11:08:56 2014 (53B66F28)
        CheckSum:         0001C322
        ImageSize:        0001F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code:
    Name    [00000002] Surface Ethernet Adapter
    Adapter Type    Ethernet 802.3
    Product Type    Surface Ethernet Adapter
    Installed    Yes
    PNP Device ID    USB\VID_045E&PID_07C6\000001000000
    Last Reset    12/04/2015 8:34 AM
    Index    2
    Service Name    msu30x64w8
    IP Address    10.141.83.99
    IP Subnet    255.255.255.0
    Default IP Gateway    10.141.83.1
    DHCP Enabled    Yes
    DHCP Server    10.141.150.60
    DHCP Lease Expires    12/04/2015 4:41 PM
    DHCP Lease Obtained    12/04/2015 8:41 AM
    MAC Address    ‪28:18:78:FF:7A:D1‬
    Driver    c:\windows\system32\drivers\msu30x64w8.sys (8.14.704.2014, 98.50 KB (100,864 bytes), 01/29/2015 1:47 PM)
    Then we have also again a USB driver
    Code:
    FAILURE_BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys
    
    BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_msu30x64w8_image_usbhub3.sys
    Are you using some kind of VPN or something?
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Surface Pro 3 BSOD overnight in docking station
Related Threads
Solved BSOD at boot, only when in docking station in BSOD Crashes and Debugging
Hi! We have fresh installed Surface Pro 3 that runs Windows 8.1 Enterprise 64-bit with all updates from Windows update and drivers/firmware installed. Most of the time when the computer boots and are attached to the docking station a BSOD appear. When booted without the docking station it...
BSOD Overnight in BSOD Crashes and Debugging
Not sure what killed it, my other server stayed running just this one went down. This server is used for a domain controller, DNS and eventually a WSUS server. I have attached the files required.
Hi all, I have a Thermaltake external eSATA docking Station that had no issues in Windows 7. Now with Windows 8.1, each time I power it on it will not be automatically recognized (not showing in "This PC"), I have to go to Device Manager and right click "Storage Controllers" and click "Scan for...
Hi, Just replaced my OS (Win 8.1) Drive, and was planning on using the old drive as a back up. This new (and old) drive have just the OS, all my programs and media etc are on other drives. Can I put my old OS drive, with Windows 8.1 still installed, into a USB Docking Station, and use it...
Read more at: Microsoft looks to roll out a Surface Pro docking station | ZDNet
I have installed 8.1 in a VHDX on a second SATA HDD drive in my laptop docking station. Even when not using Hyper-V (and having not started the virtual machine since rebooting into 8 which is on the laptop drive) I can see in Process Explorer that vmss.exe locks the VHDX. This prevents the drive...
Hello all, Forgive me if this is in the wrong thread but I have a problem. MY Advent Monza N2 running a 64-bit version of Windows 8 Pro is connected to a Plugable Technologies DisplayLink certified laptop docking station which in turn is connected via VGA lead to a Logik L22FED12 1080p HDTV. I...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook