Bugcheck occasionally while in Connected Standby

Authorized User

New Member
Messages
4
Running Windows 8.1 on Surface Pro 3. The requested file is attached. What happens is that when in Connected Standby, the Surface will reboot. You can see the various warnings in the Event Log about unexpected shutdown, etc., but nothing that really directly implicates anything.

Thanks!
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1
Taking a look at your 0x9F it shows a driver has failed to complete a power IRP.

Code:
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: [COLOR=#0000ff]ffffe00019228060[/COLOR], Physical Device Object of the stack
Arg3: fffff802600a5960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: [COLOR=#ff0000]ffffe0001aa258e0[/COLOR], The blocked IRP

Checking the blocked IRP shows:


Code:
0: kd> !irp ffffe0001aa258e0
Irp is active with 7 stacks 5 is current (= 0xffffe0001aa25ad0)
 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
>[ 16, 2]   [COLOR=#ff0000]0 e1 ffffe000191f33d0 00000000 00000000-00000000    pending
           \Driver\ACPI
            Args: 00000000 00000001 00000001 00000000[/COLOR]
 [ 16, 2]   [COLOR=#0000ff]0 e1 ffffe0001a376060 00000000 fffff8025e7a81cc-ffffe0001aaaaf08 Success Error Cancel pending
           \Driver\USBXHCI    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000[/COLOR]
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe0001aaaaf08

Looking at the physical device:

Code:
0: kd> !devobj ffffe00019228060
Device object (ffffe00019228060) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\pci DriverObject ffffe000191063e0
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
DevExt ffffe000192281b0 DevObjExt ffffe00019228778 DevNode ffffe000191e8010 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe000191f33d0 \Driver\ACPI
Device queue is not busy.
0: kd> !devnode ffffe000191e8010
DevNode 0xffffe000191e8010 for PDO 0xffffe00019228060
  Parent 0xffffe00019226920   Sibling 0xffffe000191e85c0   Child 0xffffe0001aaabd30   
  InstancePath is "[COLOR=#ff0000]PCI\VEN_8086&DEV_9C31[/COLOR]&SUBSYS_9C311414&REV_04\3&11583659&0&A0"
  ServiceName is "USBXHCI"

That's your Intel USB 3.0 eXtensible Host Controller. Is your version of Windows completely up to date? Check here for an updated version.


Code:
0: kd> lmvm USBXHCI
start             end                 module name
fffff800`2aeef000  fffff800`2af44000   USBXHCI    (pdb symbols)           c:\symbols\usbxhci.pdb\BD65CBD3F9F84654AB0A0FE9E12DBE461\usbxhci.pdb
    Loaded symbol image file: USBXHCI.SYS
    Mapped memory image file: c:\symbols\USBXHCI.SYS\5433738855000\USBXHCI.SYS
    Image path: \SystemRoot\System32\drivers\USBXHCI.SYS
    Image name: USBXHCI.SYS
    Timestamp:        [COLOR=#ff0000]Tue Oct 07 06:00:56 2014[/COLOR] (54337388)
    CheckSum:         0005D281
    ImageSize:        00055000
    File version:     6.3.9600.17393
    Product version:  6.3.9600.17393
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbxhci.sys
    OriginalFilename: usbxhci.sys
    ProductVersion:   6.3.9600.17393
    FileVersion:      6.3.9600.17393 (winblue_r4.141006-1627)
    FileDescription:  USB XHCI Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
 

My Computer

System One

  • OS
    Win7 Pro x64 | Win8.1 Pro x64 VM | Win 10TP x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom
    CPU
    i7-4790k
    Motherboard
    ASUS Sabertooth Z87 (BIOS 2004)
    Memory
    8GB Kingston HyperX Genesis @1600MHz
    Graphics Card(s)
    EVGA GTX 980 Classified
    Sound Card
    Onboard Realtek
    Monitor(s) Displays
    Samsung S24B300
    Screen Resolution
    1920 x 1080
    Hard Drives
    Intel 520 Series 240GB SSD /
    Samsung 850 EVO 120GB SSD /
    2TB WD Caviar Black /
    2TB WD Caviar Black /
    2TB WD Caviar Green
    PSU
    Corasiar HX 850-80 Gold Modular
    Case
    Cooler Master Silencio 650
    Cooling
    Corsair H80i + 2x SP120s + 2x Noctua intakes
    Keyboard
    Microsoft Sidewinder X4
    Mouse
    Gigabyte M6900
    Internet Speed
    152Mb/s
    Browser
    Firefox
    Antivirus
    F-Secure
That's your Intel USB 3.0 eXtensible Host Controller. Is your version of Windows completely up to date? Check here for an updated version.
Thank you for the detailed analysis! Regrettably, I am fully up to date. If you follow that link and use the for dropdown to select Windows 8.1, 64-bit, you'll end up with 1 driver that is for the NUC, an itty bitty barebones desktop sold by Intel.
 

My Computer

System One

  • OS
    Windows 8.1
Just to check, there's nothing plugged into your USB 3.0 port/s at the time of the BSODs? I'm not too up on Surface Pro and am not sure what Connected Standby is.
 

My Computer

System One

  • OS
    Win7 Pro x64 | Win8.1 Pro x64 VM | Win 10TP x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom
    CPU
    i7-4790k
    Motherboard
    ASUS Sabertooth Z87 (BIOS 2004)
    Memory
    8GB Kingston HyperX Genesis @1600MHz
    Graphics Card(s)
    EVGA GTX 980 Classified
    Sound Card
    Onboard Realtek
    Monitor(s) Displays
    Samsung S24B300
    Screen Resolution
    1920 x 1080
    Hard Drives
    Intel 520 Series 240GB SSD /
    Samsung 850 EVO 120GB SSD /
    2TB WD Caviar Black /
    2TB WD Caviar Black /
    2TB WD Caviar Green
    PSU
    Corasiar HX 850-80 Gold Modular
    Case
    Cooler Master Silencio 650
    Cooling
    Corsair H80i + 2x SP120s + 2x Noctua intakes
    Keyboard
    Microsoft Sidewinder X4
    Mouse
    Gigabyte M6900
    Internet Speed
    152Mb/s
    Browser
    Firefox
    Antivirus
    F-Secure
Just to check, there's nothing plugged into your USB 3.0 port/s at the time of the BSODs? I'm not too up on Surface Pro and am not sure what Connected Standby is.
Ooooo... While nothing was plugged in to the tablet's single built in USB port, it crashed shortly after I put it in its docking station, and yes, it was in connected standby before being put in that station.

Connected standby is supported by Windows 8. It permits some things to keep running in a very low power mode when the system otherwise appears to be off. It's not like normal standby where all programs halt. More information is at https://msdn.microsoft.com/en-us/library/windows/hardware/dn481216(v=vs.85).aspx.
 

My Computer

System One

  • OS
    Windows 8.1
Just to check, there's nothing plugged into your USB 3.0 port/s at the time of the BSODs? I'm not too up on Surface Pro and am not sure what Connected Standby is.
Ooooo... While nothing was plugged in to the tablet's single built in USB port, it crashed shortly after I put it in its docking station, and yes, it was in connected standby before being put in that station.

This appears to be the problem. Could you put the Surface into its docking station while fully powered up and while powered down (then boot up) and see if the BSOD occurs under those conditions.
 

My Computer

System One

  • OS
    Win7 Pro x64 | Win8.1 Pro x64 VM | Win 10TP x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom
    CPU
    i7-4790k
    Motherboard
    ASUS Sabertooth Z87 (BIOS 2004)
    Memory
    8GB Kingston HyperX Genesis @1600MHz
    Graphics Card(s)
    EVGA GTX 980 Classified
    Sound Card
    Onboard Realtek
    Monitor(s) Displays
    Samsung S24B300
    Screen Resolution
    1920 x 1080
    Hard Drives
    Intel 520 Series 240GB SSD /
    Samsung 850 EVO 120GB SSD /
    2TB WD Caviar Black /
    2TB WD Caviar Black /
    2TB WD Caviar Green
    PSU
    Corasiar HX 850-80 Gold Modular
    Case
    Cooler Master Silencio 650
    Cooling
    Corsair H80i + 2x SP120s + 2x Noctua intakes
    Keyboard
    Microsoft Sidewinder X4
    Mouse
    Gigabyte M6900
    Internet Speed
    152Mb/s
    Browser
    Firefox
    Antivirus
    F-Secure
Just to check, there's nothing plugged into your USB 3.0 port/s at the time of the BSODs? I'm not too up on Surface Pro and am not sure what Connected Standby is.
Ooooo... While nothing was plugged in to the tablet's single built in USB port, it crashed shortly after I put it in its docking station, and yes, it was in connected standby before being put in that station.

This appears to be the problem. Could you put the Surface into its docking station while fully powered up and while powered down (then boot up) and see if the BSOD occurs under those conditions.
Thanks. I'll keep watching, but I think it rarely crashes like this in the docking station.
 

My Computer

System One

  • OS
    Windows 8.1
Back
Top