ProGeek Posted February 14, 2021 Share Posted February 14, 2021 I have a recent build where I used the 1000D case with the built in Commander. I have the Corsair water cooling, Corsair keyboard, Corsair mouse, Corsair RGB RAM, and additionally I have added 2 more lighting nodes to handle additional lights including custom back plates. MB is the Asus Zenith II Extreme with 24 core Threadripper. Daily, I was getting the BSOD: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffb48642154cf0, 0xffff8406c1645850, 0xffffb486469eb010). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 2f70bcbb-22e2-4c1d-a1bc-8699b23b62df. Being a software engineer myself, I broke out the kernel debugger and looked into the dump file. What I found was the offending driver/device was VID_1B1C and PID_1D00. 1B1C is Corsair. I was not able to pinpoint online which device is 1D00. Maybe someone can help me here with that. I suspect it is one of the lighting controllers because another issue that I see is that the lighting works great for a while after booting my system, but after awhile, many of the lights slip back to the hardware light configuration. ICUE also typically becomes unresponsive. For now, I have uninstalled ICUE and the BSODs seem to have gone away. So I am left wondering - is ICUE software and driver unreliable or do I have faulty light controllers? I would hate to spend more money replacing Corsair light controllers if I am just going to have the same problems again. Have others been able to run ICUE and have it work for more than a few hours? Does anyone know what device 1D00 is? Thanks Link to comment Share on other sites More sharing options...
Corsair Employees Corsair Notepad Posted February 16, 2021 Corsair Employees Share Posted February 16, 2021 Would be really helpful if you provided your actual system specs and what devices you have connected. Link to comment Share on other sites More sharing options...
ProGeek Posted February 16, 2021 Author Share Posted February 16, 2021 (edited) Operating System Windows 10 Pro 64-bit CPU AMD Ryzen Threadripper 3960X 38 °C Castle Peak 7nm Technology RAM 128GB Corsair @ 1058MHz (15-15-15-36) Motherboard ASUSTeK COMPUTER INC. ROG ZENITH II EXTREME (sTRX4) 42 °C Graphics 416 (1920x1200@59Hz) 416 (1920x1200@59Hz) 4095MB NVIDIA GeForce RTX 2080 (ASUStek Computer Inc) 33 °C 4095MB NVIDIA GeForce RTX 2080 (ASUStek Computer Inc) 33 °C SLI Enabled Storage 3726GB Samsung SSD 860 EVO 4TB (SATA (SSD)) 36 °C 1863GB Corsair Force MP600 2TB Optical Drives No optical disk drives detected Audio Sennheiser Main Audio The case is a Corsair 1000D with the built in Corsair Commander. I have Hydro X cooling: - XD5 RGB Pump - 2 XG7 RGB 20-series GPU water blocks - QL140 and QL120 RGB fans - Hydro X XC9 RGB CPU Water Block Memory is 8 sticks - Corsair Vengeance RGB Pro 64GB (4x16GB) DDR4 3200 Power - CORSAIR AXi Series, AX1600i, 1600 Watt, 80+ Titanium Certified USB lighting devices - Corsair integrated Commander Pro - 2x Corsair Lighting Node COREs Mouse is Corsair Scimitar Pro RGB Keyboard: Corsair K95 RGB Platinum Mechanical Edited February 16, 2021 by ProGeek Add more devices Link to comment Share on other sites More sharing options...
ProGeek Posted February 16, 2021 Author Share Posted February 16, 2021 Initial dump file analysis. For analysis of this file, run !analyze -v 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: ffffb48642154cf0, Physical Device Object of the stack Arg3: ffff8406c1645850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffb486469eb010, The blocked IRP Debugging Details: ------------------ Implicit thread is now ffffb486`299b4080 KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on MONOLITH Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 4 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffb48642154cf0 BUGCHECK_P3: ffff8406c1645850 BUGCHECK_P4: ffffb486469eb010 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffb486299b4080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffff8406`c161b680 fffff804`07265850 : 00000000`00000009 ffff8406`ffffffff 00000000`00000000 ffffb486`55bf8158 : nt!KiSwapContext+0x76 ffff8406`c161b7c0 fffff804`07264d7f : 00000000`00000000 00000000`00000000 ffff8406`c161b980 00000000`00000000 : nt!KiSwapThread+0x500 ffff8406`c161b870 fffff804`07264623 : ffffb486`00000000 ffffb486`00000000 ffffb486`5058db00 ffffb486`299b41c0 : nt!KiCommitThreadWait+0x14f ffff8406`c161b910 fffff804`52294ece : ffffb486`467e32a8 00000000`00000000 00000000`00000000 ffff8406`c161ba00 : nt!KeWaitForSingleObject+0x233 ffff8406`c161ba00 fffff804`522941d7 : ffffb486`46ae61d0 00000000`00000002 ffffb486`469eb710 ffffb486`469eb010 : HIDCLASS!CancelAllPingPongIrps+0x1fe ffff8406`c161ba60 fffff804`522926d6 : ffffb486`46ae61b0 00000000`00000000 00000000`00000016 fffff804`0739ccc6 : HIDCLASS!HidpFdoPower+0x247 ffff8406`c161bae0 fffff804`0739ca99 : ffff8406`c161bbf0 ffffb486`299b4080 ffffb486`469eb010 ffffb486`00000000 : HIDCLASS!HidpMajorHandler+0x206 ffff8406`c161bb70 fffff804`07317e25 : 00000000`00000000 fffff804`0739c8c0 00000000`00000000 00000000`000000be : nt!PopIrpWorker+0x1d9 ffff8406`c161bc10 fffff804`073fd0d8 : ffffe000`cf880180 ffffb486`299b4080 fffff804`07317dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff8406`c161bc60 00000000`00000000 : ffff8406`c161c000 ffff8406`c1616000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 STACK_COMMAND: .thread 0xffffb486299b4080 ; kb SYMBOL_NAME: HIDCLASS!CancelAllPingPongIrps+1fe MODULE_NAME: HIDCLASS IMAGE_NAME: HIDCLASS.SYS IMAGE_VERSION: 10.0.19041.1 BUCKET_ID_FUNC_OFFSET: 1fe FAILURE_BUCKET_ID: 0x9F_3_HIDCLASS!CancelAllPingPongIrps OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4f75e063-21d8-788d-807c-6f8cb2bfd785} Link to comment Share on other sites More sharing options...
Recommended Posts