C
CStendall22
Hi all,
We have a virtual server running on VMWare running Server 2016 Desktop Experience. This server is not in an RDS farm, and therefore contains multiple components of the RDS setup by itself.
Recently (In the last few days) it has started crashing and rebooting itself. I have analysed the crash dump and it seems to point to a driver problem? VMWare tools were removed and the latest version of them reinstalled on the server, and the server then rebooted, but this has not solved the problem.
Please find the crash dump below, can anyone offer any advice or possible solutions?:
Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Development\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810
Machine Name:
Kernel base = 0xfffff801`2b401000 PsLoadedModuleList = 0xfffff801`2b703200
Debug session time: Wed Aug 15 05:49:20.739 2018 (UTC + 1:00)
System Uptime: 0 days 7:09:43.641
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffc60b1e2648d0, ffff9e81cc15c2a0, ffffc60b1d9b0bc0}
Implicit thread is now ffffc60b`16358040
Probably caused by : HIDCLASS.SYS ( HIDCLASS!CancelAllPingPongIrps+122 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffc60b1e2648d0, Physical Device Object of the stack
Arg3: ffff9e81cc15c2a0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc60b1d9b0bc0, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffc60b`16358040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 402
BUILD_VERSION_STRING: 14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810
SYSTEM_MANUFACTURER: VMware, Inc.
VIRTUAL_MACHINE: VMware
SYSTEM_PRODUCT_NAME: VMware Virtual Platform
SYSTEM_VERSION: None
BIOS_VENDOR: Phoenix Technologies LTD
BIOS_VERSION: 6.00
BIOS_DATE: 04/05/2016
BASEBOARD_MANUFACTURER: Intel Corporation
BASEBOARD_PRODUCT: 440BX Desktop Reference Platform
BASEBOARD_VERSION: None
DUMP_TYPE: 0
BUGCHECK_P1: 3
BUGCHECK_P2: ffffc60b1e2648d0
BUGCHECK_P3: ffff9e81cc15c2a0
BUGCHECK_P4: ffffc60b1d9b0bc0
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: 16358040
CPU_COUNT: 4
CPU_MHZ: d40
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 55
CPU_STEPPING: 4
CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 2000043'00000000 (cache) 2000043'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: SERVER NAME REMOVED
ANALYSIS_SESSION_TIME: 08-15-2018 11:38:47.0364
ANALYSIS_VERSION: 10.0.17134.12 amd64fre
LAST_CONTROL_TRANSFER: from fffff8012b4d109d to fffff8012b5644d6
STACK_TEXT:
ffff9e81`cbffc010 fffff801`2b4d109d : 00000000`00000000 00000000`00000001 00000000`00000000 fffff80a`fc9a62f8 : nt!KiSwapContext+0x76
ffff9e81`cbffc150 fffff801`2b4d0b3f : 00000000`00000000 00000000`00000005 00000000`00000000 fffff80a`fc9a62f8 : nt!KiSwapThread+0x17d
ffff9e81`cbffc200 fffff801`2b4d2917 : 00000000`00000000 fffff801`2b4d10d8 ffffc60b`1dec3798 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffff9e81`cbffc2a0 fffff80a`fc994b16 : ffffc60b`1d956128 ffffc60b`00000000 00000000`00000000 ffffc60b`00000000 : nt!KeWaitForSingleObject+0x377
ffff9e81`cbffc350 fffff80a`fc994953 : ffffc60b`1e03b800 ffffc60b`1d9b0e88 00000000`80000000 ffffc60b`1d9b0bc0 : HIDCLASS!CancelAllPingPongIrps+0x122
ffff9e81`cbffc3b0 fffff80a`fc9927ba : ffffc60b`1e03b7e0 00000000`00000000 ffffc60b`1d9b0bc0 00000000`00000016 : HIDCLASS!HidpFdoPower+0x1f3
ffff9e81`cbffc420 fffff801`2b52bdf2 : ffff9e81`cbffc530 fffff801`2b6fe700 ffffc60b`1e03b690 fffff801`2b6fe700 : HIDCLASS!HidpMajorHandler+0x30a
ffff9e81`cbffc4b0 fffff801`2b4a8aa9 : ffffc60b`16358040 fffff801`2b52bc14 00000000`00000000 00000000`00002436 : nt!PopIrpWorker+0x1de
ffff9e81`cbffc550 fffff801`2b564bc6 : ffff9e81`cc096180 ffffc60b`16358040 fffff801`2b4a8a68 52880fc0`85d08bff : nt!PspSystemThreadStartup+0x41
ffff9e81`cbffc5a0 00000000`00000000 : ffff9e81`cbffd000 ffff9e81`cbff6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .thread 0xffffc60b16358040 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 2e316f3144981f1aa4235d5bba636dec6a927049
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2e40588ec41e4653b000ad7ed1999dbce6a7f3e5
THREAD_SHA1_HASH_MOD: a51dc7364fc2e2c5568bbf67ced0f32adac695c0
FOLLOWUP_IP:
HIDCLASS!CancelAllPingPongIrps+122
fffff80a`fc994b16 f0ff4d18 lock dec dword ptr [rbp+18h]
FAULT_INSTR_CODE: 184dfff0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: HIDCLASS!CancelAllPingPongIrps+122
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HIDCLASS
IMAGE_NAME: HIDCLASS.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 5b1a1821
IMAGE_VERSION: 10.0.14393.2312
BUCKET_ID_FUNC_OFFSET: 122
FAILURE_BUCKET_ID: 0x9F_3_HIDCLASS!CancelAllPingPongIrps
BUCKET_ID: 0x9F_3_HIDCLASS!CancelAllPingPongIrps
PRIMARY_PROBLEM_CLASS: 0x9F_3_HIDCLASS!CancelAllPingPongIrps
TARGET_TIME: 2018-08-15T04:49:20.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 16
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 Server TerminalServer
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-08-07 05:05:51
BUILDDATESTAMP_STR: 180806-1810
BUILDLAB_STR: rs1_release_inmarket_aim
BUILDOSVER_STR: 10.0.14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810
ANALYSIS_SESSION_ELAPSED_TIME: 711
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_hidclass!cancelallpingpongirps
FAILURE_ID_HASH: {4f75e063-21d8-788d-807c-6f8cb2bfd785}
Followup: MachineOwner
---------
Thanks,
Chris
Continue reading...
We have a virtual server running on VMWare running Server 2016 Desktop Experience. This server is not in an RDS farm, and therefore contains multiple components of the RDS setup by itself.
Recently (In the last few days) it has started crashing and rebooting itself. I have analysed the crash dump and it seems to point to a driver problem? VMWare tools were removed and the latest version of them reinstalled on the server, and the server then rebooted, but this has not solved the problem.
Please find the crash dump below, can anyone offer any advice or possible solutions?:
Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Development\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810
Machine Name:
Kernel base = 0xfffff801`2b401000 PsLoadedModuleList = 0xfffff801`2b703200
Debug session time: Wed Aug 15 05:49:20.739 2018 (UTC + 1:00)
System Uptime: 0 days 7:09:43.641
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffc60b1e2648d0, ffff9e81cc15c2a0, ffffc60b1d9b0bc0}
Implicit thread is now ffffc60b`16358040
Probably caused by : HIDCLASS.SYS ( HIDCLASS!CancelAllPingPongIrps+122 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffc60b1e2648d0, Physical Device Object of the stack
Arg3: ffff9e81cc15c2a0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc60b1d9b0bc0, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffc60b`16358040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 402
BUILD_VERSION_STRING: 14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810
SYSTEM_MANUFACTURER: VMware, Inc.
VIRTUAL_MACHINE: VMware
SYSTEM_PRODUCT_NAME: VMware Virtual Platform
SYSTEM_VERSION: None
BIOS_VENDOR: Phoenix Technologies LTD
BIOS_VERSION: 6.00
BIOS_DATE: 04/05/2016
BASEBOARD_MANUFACTURER: Intel Corporation
BASEBOARD_PRODUCT: 440BX Desktop Reference Platform
BASEBOARD_VERSION: None
DUMP_TYPE: 0
BUGCHECK_P1: 3
BUGCHECK_P2: ffffc60b1e2648d0
BUGCHECK_P3: ffff9e81cc15c2a0
BUGCHECK_P4: ffffc60b1d9b0bc0
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: 16358040
CPU_COUNT: 4
CPU_MHZ: d40
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 55
CPU_STEPPING: 4
CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 2000043'00000000 (cache) 2000043'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: SERVER NAME REMOVED
ANALYSIS_SESSION_TIME: 08-15-2018 11:38:47.0364
ANALYSIS_VERSION: 10.0.17134.12 amd64fre
LAST_CONTROL_TRANSFER: from fffff8012b4d109d to fffff8012b5644d6
STACK_TEXT:
ffff9e81`cbffc010 fffff801`2b4d109d : 00000000`00000000 00000000`00000001 00000000`00000000 fffff80a`fc9a62f8 : nt!KiSwapContext+0x76
ffff9e81`cbffc150 fffff801`2b4d0b3f : 00000000`00000000 00000000`00000005 00000000`00000000 fffff80a`fc9a62f8 : nt!KiSwapThread+0x17d
ffff9e81`cbffc200 fffff801`2b4d2917 : 00000000`00000000 fffff801`2b4d10d8 ffffc60b`1dec3798 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffff9e81`cbffc2a0 fffff80a`fc994b16 : ffffc60b`1d956128 ffffc60b`00000000 00000000`00000000 ffffc60b`00000000 : nt!KeWaitForSingleObject+0x377
ffff9e81`cbffc350 fffff80a`fc994953 : ffffc60b`1e03b800 ffffc60b`1d9b0e88 00000000`80000000 ffffc60b`1d9b0bc0 : HIDCLASS!CancelAllPingPongIrps+0x122
ffff9e81`cbffc3b0 fffff80a`fc9927ba : ffffc60b`1e03b7e0 00000000`00000000 ffffc60b`1d9b0bc0 00000000`00000016 : HIDCLASS!HidpFdoPower+0x1f3
ffff9e81`cbffc420 fffff801`2b52bdf2 : ffff9e81`cbffc530 fffff801`2b6fe700 ffffc60b`1e03b690 fffff801`2b6fe700 : HIDCLASS!HidpMajorHandler+0x30a
ffff9e81`cbffc4b0 fffff801`2b4a8aa9 : ffffc60b`16358040 fffff801`2b52bc14 00000000`00000000 00000000`00002436 : nt!PopIrpWorker+0x1de
ffff9e81`cbffc550 fffff801`2b564bc6 : ffff9e81`cc096180 ffffc60b`16358040 fffff801`2b4a8a68 52880fc0`85d08bff : nt!PspSystemThreadStartup+0x41
ffff9e81`cbffc5a0 00000000`00000000 : ffff9e81`cbffd000 ffff9e81`cbff6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .thread 0xffffc60b16358040 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 2e316f3144981f1aa4235d5bba636dec6a927049
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2e40588ec41e4653b000ad7ed1999dbce6a7f3e5
THREAD_SHA1_HASH_MOD: a51dc7364fc2e2c5568bbf67ced0f32adac695c0
FOLLOWUP_IP:
HIDCLASS!CancelAllPingPongIrps+122
fffff80a`fc994b16 f0ff4d18 lock dec dword ptr [rbp+18h]
FAULT_INSTR_CODE: 184dfff0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: HIDCLASS!CancelAllPingPongIrps+122
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HIDCLASS
IMAGE_NAME: HIDCLASS.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 5b1a1821
IMAGE_VERSION: 10.0.14393.2312
BUCKET_ID_FUNC_OFFSET: 122
FAILURE_BUCKET_ID: 0x9F_3_HIDCLASS!CancelAllPingPongIrps
BUCKET_ID: 0x9F_3_HIDCLASS!CancelAllPingPongIrps
PRIMARY_PROBLEM_CLASS: 0x9F_3_HIDCLASS!CancelAllPingPongIrps
TARGET_TIME: 2018-08-15T04:49:20.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 16
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 Server TerminalServer
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-08-07 05:05:51
BUILDDATESTAMP_STR: 180806-1810
BUILDLAB_STR: rs1_release_inmarket_aim
BUILDOSVER_STR: 10.0.14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810
ANALYSIS_SESSION_ELAPSED_TIME: 711
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_hidclass!cancelallpingpongirps
FAILURE_ID_HASH: {4f75e063-21d8-788d-807c-6f8cb2bfd785}
Followup: MachineOwner
---------
Thanks,
Chris
Continue reading...