Dear All,
I couln't find anything regarding this bsod. Sometimes an rds server crashes with a blue screen ( always Driver_Power_State_Failure 9F ). My engineers told me this happens when they connect with rdp but not always.The server has the poweroption high perfomance.
This server has last been patched on 10 march 2016.
When I analyze the minidmp it's always the same faulting module: usbccgp
Minidmp !analyze -v
==========================begin minidmp===========================================
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: ffffe00076e2b300, Physical Device Object of the stack
Arg3: ffffd000e7f9b960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe8005912c490, The blocked IRP
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 9600.17936.amd64fre.winblue_ltsb.150715-0840
SYSTEM_MANUFACTURER: Microsoft Corporation
VIRTUAL_MACHINE: HyperV
SYSTEM_PRODUCT_NAME: Virtual Machine
SYSTEM_VERSION: 7.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 090006
BIOS_DATE: 05/23/2012
BASEBOARD_MANUFACTURER: Microsoft Corporation
BASEBOARD_PRODUCT: Virtual Machine
BASEBOARD_VERSION: 7.0
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffe00076e2b300
BUGCHECK_P3: ffffd000e7f9b960
BUGCHECK_P4: ffffe8005912c490
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1b3
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff801f651f000 usbccgp
CPU_COUNT: 8
CPU_MHZ: 898
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 2d
CPU_STEPPING: 7
CPU_MICROCODE: 6,2d,7,0 (F,M,S,R) SIG: FFFFFFFF'00000000 (cache) FFFFFFFF'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: PC8MIL
ANALYSIS_SESSION_TIME: 03-25-2016 09:39:48.0962
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
ffffd000`e7f9b928 fffff802`ae2801ce : 00000000`0000009f 00000000`00000003 ffffe000`76e2b300 ffffd000`e7f9b960 : nt!KeBugCheckEx
ffffd000`e7f9b930 fffff802`ae2800ee : ffffe000`71729c90 fffff802`ae027fae ffffe800`580e02a0 ffffd000`e7f4e180 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`e7f9b990 fffff802`ae0fc948 : 00000000`00000014 00000000`00989680 ffffd000`e7f9bae0 ffffd000`e7f4e180 : nt!PopIrpWatchdog+0x32
ffffd000`e7f9b9e0 fffff802`ae1ce4ea : ffffd000`e7f4e180 ffffd000`e7f4e180 ffffd000`e7f5a3c0 ffffe000`7b48b2c0 : nt!KiRetireDpcList+0x4f8
ffffd000`e7f9bc60 00000000`00000000 : ffffd000`e7f9c000 ffffd000`e7f96000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b4ad1c5ace16e5a03331b4856dbd5b1986faa70f
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_usbvideo_IMAGE_usbccgp.sys
BUCKET_ID: 0x9F_3_usbvideo_IMAGE_usbccgp.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_usbvideo_IMAGE_usbccgp.sys
TARGET_TIME: 2015-09-03T14:40:56.000Z
OSBUILD: 9600
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 16
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
OSEDITION: Windows 8.1 Server TerminalServer
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2015-07-15 18:37:58
BUILDDATESTAMP_STR: 150715-0840
BUILDLAB_STR: winblue_ltsb
BUILDOSVER_STR: 6.3.9600.17936.amd64fre.winblue_ltsb.150715-0840
ANALYSIS_SESSION_ELAPSED_TIME: 4bd
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_usbvideo_image_usbccgp.sys
FAILURE_ID_HASH: {5a143f89-5f5a-24ab-53c4-ca74dfa032ac}
Followup: MachineOwner
---------
======================== end minidmp ===============================================
You see the blocked irp
Arg4: ffffe8005912c490, The blocked IRP
if I do !irp ffffe8005912c490
I also get this:
=============================Blocked IRP begin======================================
1: kd> !irp ffffe8005912c490
Irp is active with 8 stacks 6 is current (= 0xffffe8005912c6c8)
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
[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_SET_POWER(2)]
0 0 ffffe8005c097540 00000000 00000000-00000000
\Driver\usbvideo
Args: 00000000 00000001 00000004 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe0007aba6b60 00000000 fffff802ae19980c-ffffe00071729c90 Success Error Cancel pending
\Driver\ksthunknt!PopRequestCompletion
Args: 00000000 00000001 00000004 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffe00071729c90
Args: 00000000 00000000 00000000 00000000
===========================end blocked irp =========================================
usbvideo and ksthunk are at fault here.
Does someone has a clue what the failure might be I'm a bit stumped. Can it be a physical problem? The hyper-v host has 4 vms
and this vm is the only one with this problem although it uses the most ram of all.
Thanks in advance.
