Jump to content
Corsair Community

H115i not detected in latest iCUE (3.6.109)


prenetic

Recommended Posts

This has actually been going on for two or three releases now. The H115i AIO cooler is not detected by iCUE despite the drivers loaded, and service running. Originally it was hit or miss, after booting it would *sometimes* be detected, however with the latest versions it is never detected.

 

In an attempt to further isolate the issue and rule out conflicting software, a laptop with a clean installation of Windows 10 x64 and iCUE 3.6.109 was placed alongside the machine with the H115i. A different USB cable was used, and plugged into the H115i and the laptop. The cooler was never detected by iCUE on the laptop after validating OS-level detection, either.

 

Digging into service logs on the desktop, we see issues interacting with the device with several retries. At this point, even after a complete uninstall (removing ProgramData and AppData configurations, device drivers), I am unable to control the H115i AIO cooler.

 

shqshsvty3g11.png

 

k6we9c5ly3g11.png

 

ifxknq7hy3g11.png

 

Logs:

2018-08-14 12:26:32.2142 | 20 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:26:32.2142 | 20 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3150 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3150 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3150 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3150 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3150 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3150 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3290 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.3290 | 14 | NYX | 3.6.0.19 | DisableHardware | Trying to restart devices(USB\VID_1B1C&PID_0C0A\7289_2.0). Attempt #1 of 5

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Device #1 of 1

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling...

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling...

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Trying to restart devices(USB\VID_1B1C&PID_0C0A\7289_2.0). Attempt #2 of 5

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Device #1 of 1

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling...

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling...

2018-08-14 12:30:59.3450 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Trying to restart devices(USB\VID_1B1C&PID_0C0A\7289_2.0). Attempt #3 of 5

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Device #1 of 1

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling...

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling...

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Trying to restart devices(USB\VID_1B1C&PID_0C0A\7289_2.0). Attempt #4 of 5

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Device #1 of 1

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling...

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling...

2018-08-14 12:30:59.3600 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | Trying to restart devices(USB\VID_1B1C&PID_0C0A\7289_2.0). Attempt #5 of 5

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Device #1 of 1

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling...

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Disabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling...

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | Restart of device(USB\VID_1B1C&PID_0C0A\7289_2.0). Enabling error: SetupDiChangeStateError

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | DisableHardware | TOTAL COUNT OF RESTARTS OF DEVICES(USB\VID_1B1C&PID_0C0A\7289_2.0) IS 1

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Set timeout for 1 hour

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Read was failed 5 time(s). Need to restart devices

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Next restart of device will be after 59 minute(s)

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3920 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Read was failed 5 time(s). Need to restart devices

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Read was failed 5 time(s). Need to restart devices

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4070 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Read was failed 5 time(s). Need to restart devices

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4230 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Open was failed 3 time(s). Need to restart devices

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 12:30:59.4380 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 14:58:56.6381 | 55 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

2018-08-14 14:58:56.6381 | 55 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

Link to comment
Share on other sites

Check Device Manager. Do you see Corsair USBXp Driver in there? Can you manually reset the driver?

 

Are you running any other monitoring tools? EVGA Precision XOC? (Note: Precision XOC is known to cause issues; see the Cooler FAQ).

 

I read the FAQ before posting, and I'll take a moment here to reiterate: the screenshot included in the original post shows the Corsair USBXp driver installed and running. I've reset the driver, reinstalled the driver, and as stated above, even went as far as to plug the device into a different machine altogether.

 

I don't have any conflicting/monitoring software installed, and sought to rule this out pretty quickly. When testing the device while plugged into a laptop with a fresh installation of Windows and only iCUE installed, the behavior was the same as the desktop the device is installed in.

Link to comment
Share on other sites

First, the cooler would need to be properly powered; it won't be detected just from the power on the USB header. So unless you had it properly powered when you plugged it into the laptop, that's not a valid test.

 

And do you have Precision XOC running? Your logs look like the driver is crashing. Precision XOC has been known to cause this and you have an EVGA card.

Link to comment
Share on other sites

First, the cooler would need to be properly powered; it won't be detected just from the power on the USB header. So unless you had it properly powered when you plugged it into the laptop, that's not a valid test.

 

And do you have Precision XOC running? Your logs look like the driver is crashing. Precision XOC has been known to cause this and you have an EVGA card.

 

I appreciate the assistance, but it would appear there is some trouble understanding what I'm saying given the claim this testing methodology was flawed. I haven't tested whether USB or the SATA powers the USB device within the H115i itself, but that's beside the point. Additionally, it's important to realize both the possibility and validity of powering devices from a standalone SATA power supply for testing.

 

In this scenario, the desktop was fully powered on and the only change from normal operation was the USB cable itself and which machine it was connected to. The H115i was receiving power as it always has been through the SATA plug on the desktop -- fans spinning, pump running, and LEDs illuminated. The laptop was used to validate whether or not the USB component itself would be detected by the operating system, the driver would load, and iCUE would detect it. On both machines, there was successful detection by the operating system and the driver was loaded, however iCUE did not detect the device.

 

With respect to Precision XOC, I do not have this installed. I do not have this installed on my desktop, nor do I have it installed on the freshly rebuilt laptop. This has never been installed on either machine. With respect to the logs, I don't see any corresponding driver crash events in the event log on the machine. From the Corsair service log, it looks like there's a reoccurring access issue (on reads/writes) which increments a retry counter until a threshold is met and the device is requested to gracefully restart. In some cases the device is restarted successfully (according to the Corsair logs), other times it maxes out at 5 retries and gives up. Either way we wind up with the following two lines mixed in with access operation failures:

 

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

Link to comment
Share on other sites

I appreciate the assistance, but it would appear there is some trouble understanding what I'm saying given the claim this testing methodology was flawed. I haven't tested whether USB or the SATA powers the USB device within the H115i itself, but that's beside the point. Additionally, it's important to realize both the possibility and validity of powering devices from a standalone SATA power supply for testing.

 

In this scenario, the desktop was fully powered on and the only change from normal operation was the USB cable itself and which machine it was connected to. The H115i was receiving power as it always has been through the SATA plug on the desktop -- fans spinning, pump running, and LEDs illuminated. The laptop was used to validate whether or not the USB component itself would be detected by the operating system, the driver would load, and iCUE would detect it. On both machines, there was successful detection by the operating system and the driver was loaded, however iCUE did not detect the device.

 

With respect to Precision XOC, I do not have this installed. I do not have this installed on my desktop, nor do I have it installed on the freshly rebuilt laptop. This has never been installed on either machine. With respect to the logs, I don't see any corresponding driver crash events in the event log on the machine. From the Corsair service log, it looks like there's a reoccurring access issue (on reads/writes) which increments a retry counter until a threshold is met and the device is requested to gracefully restart. In some cases the device is restarted successfully (according to the Corsair logs), other times it maxes out at 5 retries and gives up. Either way we wind up with the following two lines mixed in with access operation failures:

 

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Exception while writing and reading: Exception of type 'SIUSBXpWrapper.USBDeviceReadException' was thrown.

2018-08-14 12:30:59.3790 | 14 | NYX | 3.6.0.19 | AsetekCoolerV2Device | Device can't be open. USBCommandHandler.SI_Open returns false

 

Thanks for the additional information. I do not assume details - far too often this leads to mistaken assumptions. You had no details regarding powering the cooler in your post so I am not going to read your mind and infer that it was setup correctly. Again, experience on the forum has frequently shown that this leads down mistaken paths. The more information that you provide to us, the better we can help you. Details are important.

 

Now ... again ... this logs are indicative of the driver crashing. That's what appears in the logs when the driver crashes.

 

When you say that the driver is loaded on the laptop ... do you see the Corsair USBXp Driver in Device Manager as well?

 

Again, this is typically the result of software conflict ... like 90% of the time. These drivers only support single access from a single software application ("Highlander Mode") and more than one application connecting to the drivers will almost always cause these issues. Barring that, if you are absolutely certain that no other software is accessing the device (and, at this point, that does seem to be the case but I need to make sure that it's qualified) then it's possible that something has gone awry with the MCU in the device. From there, the only option left is to open a support ticket - you can't reflash the firmware.

Link to comment
Share on other sites

Thanks for the additional information. I do not assume details - far too often this leads to mistaken assumptions. You had no details regarding powering the cooler in your post so I am not going to read your mind and infer that it was setup correctly. Again, experience on the forum has frequently shown that this leads down mistaken paths. The more information that you provide to us, the better we can help you. Details are important.

 

Now ... again ... this logs are indicative of the driver crashing. That's what appears in the logs when the driver crashes.

 

When you say that the driver is loaded on the laptop ... do you see the Corsair USBXp Driver in Device Manager as well?

 

Again, this is typically the result of software conflict ... like 90% of the time. These drivers only support single access from a single software application ("Highlander Mode") and more than one application connecting to the drivers will almost always cause these issues. Barring that, if you are absolutely certain that no other software is accessing the device (and, at this point, that does seem to be the case but I need to make sure that it's qualified) then it's possible that something has gone awry with the MCU in the device. From there, the only option left is to open a support ticket - you can't reflash the firmware.

 

Well the logs certainly don't make that clear. And yes, the device shows up in Device Manager on the laptop as well, and indicates the device is working properly when checking via properties.

 

I'm absolutely certain I've got no conflicting software installed on the laptop since iCUE is literally the only thing installed following a rebuild, though on the desktop it's hard to say with absolute certainty what could be conflicting. This is why I wanted to perform some testing on a completely fresh machine.

 

The only other possibility I've come up with is ASUS Aura Sync, but I haven't seen posts indicating a conflict there. HWiNFO is occasionally used on the desktop, but is not installed (portable binary only) and is not running when the machine starts up. I tend to steer away from running unnecessary software from device manufacturers for this exact reason, it's far too common.

 

Sounds like I might as well try a new unit at this point and see how far that gets me.

Link to comment
Share on other sites

Well the logs certainly don't make that clear. And yes, the device shows up in Device Manager on the laptop as well, and indicates the device is working properly when checking via properties.

 

It's always a matter of interpreting the logs. We have seen log entries like this when there is a conflict.

 

I'm absolutely certain I've got no conflicting software installed on the laptop since iCUE is literally the only thing installed following a rebuild, though on the desktop it's hard to say with absolute certainty what could be conflicting. This is why I wanted to perform some testing on a completely fresh machine.

 

The only other possibility I've come up with is ASUS Aura Sync, but I haven't seen posts indicating a conflict there. HWiNFO is occasionally used on the desktop, but is not installed (portable binary only) and is not running when the machine starts up. I tend to steer away from running unnecessary software from device manufacturers for this exact reason, it's far too common.

Aura Sync shouldn't cause this unless they've added something into it where they are trying to sync the cooler (which is what EVGA was doing with Precision XOC that caused problems). IF this is the case with Aura Sync, it'd be the first we've seen it here.

 

Sounds like I might as well try a new unit at this point and see how far that gets me.

At this point, this is the next logical step, especially with the clean laptop having an issue. The only potential thing to check here is that the cable is a data USB cable and not a charging-only USB cable. They do have those beasties and you can't tell the difference.

Link to comment
Share on other sites

It's always a matter of interpreting the logs. We have seen log entries like this when there is a conflict.

 

 

Aura Sync shouldn't cause this unless they've added something into it where they are trying to sync the cooler (which is what EVGA was doing with Precision XOC that caused problems). IF this is the case with Aura Sync, it'd be the first we've seen it here.

 

 

At this point, this is the next logical step, especially with the clean laptop having an issue. The only potential thing to check here is that the cable is a data USB cable and not a charging-only USB cable. They do have those beasties and you can't tell the difference.

 

Thanks for confirming. The cable used is a known-good data cable which I frequently use for programming radios and transferring tracks from my GPS device, so I guess that rules out another possibility.

Link to comment
Share on other sites

Thanks for confirming. The cable used is a known-good data cable which I frequently use for programming radios and transferring tracks from my GPS device, so I guess that rules out another possibility.

 

Yup ... the certainly rules out cable issues.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...