Jump to content
Corsair Community

H80i v2 not resuming and showing in CL4 after waking from Sleep mode


Rickets

Recommended Posts

Okay, so I have been doing a lot of searching and reading about this problem. This seems to be a common problem without any clear resolve. I tried a few things such as the edit Device Parameters in REGEDIT, but there were no entries regarding the fix, so I left it as is. It is in my device manager, so I know that is okay. (View attachments) I do have a question about the events though in the properties of the Device. Even though it says the device is running properly, in the Events Tab there are a couple of entries I question. (View attachments) Is this normal? And is there any other fix that I may have missed? Thank you for replies and any help in advance.

 

CL4 version I am using is 43.0.154

2016-12-11_9-45-16.jpg.fa969234ed95391bb64ff1fea9d90231.jpg

2016-12-11_9-47-49.jpg.9f9245c409368e2a0cd49f578bedd463.jpg

Link to comment
Share on other sites

As far as I can tell there is a bug in the 7289 driver handling of power transitions.

 

I suspect that when the device has the issue you do as follows this will get it working again, does it?

  1. Close down/totally exit CL4.
  2. Use Device Manager to Disable the 7289 device.
  3. Use Device Manager to Enable the 7289 device.
  4. run CL4.

Assuming this get's the H80iV2 back then this confirms it's a driver issue that Corsair should fix.

Link to comment
Share on other sites

As far as I can tell there is a bug in the 7289 driver handling of power transitions.

 

I suspect that when the device has the issue you do as follows this will get it working again, does it?

  1. Close down/totally exit CL4.
  2. Use Device Manager to Disable the 7289 device.
  3. Use Device Manager to Enable the 7289 device.
  4. run CL4.

Assuming this get's the H80iV2 back then this confirms it's a driver issue that Corsair should fix.

 

Thank you very much. That worked. Is there anyway to create a bat file to do this for the mean time? Hopefully there will be a fix in CL updates.

Link to comment
Share on other sites

In the end I did a work-a-round in my software.

 

Well I guess I got my work cut out for me. I will start doing some research and reading and see if I can come up with a minor solution for the mean time instead of having to go through the steps you gave. I read some of your other threads, it seems you got good knack for this.

 

You probably heard this many times already, Corsair should really put you on their payroll or consider it. Granted, you probably make a decent wage already.:laughing: Thanks again red-ray.

Link to comment
Share on other sites

Well I guess I got my work cut out for me.

 

Corsair should really put you on their payroll.

 

I suspect to do a good work-a-round you would need a program and have it active all the time. Do you wish to do this? What would be need is:

  1. Register for power state change notifications
  2. On resume from sleep for each 7289 device do as below.
  3. Wait a while (By default SIV waits 15 seconds).
  4. Acquire the CL locking mutex.
  5. Disable the 7289 device.
  6. Enable the 7289 device.
  7. Release the CL locking mutex.

This is really the wrong solution, but only Corsair have (should have?) the 7289 driver source code and could implement the correct solution which is to fix the driver.

 

I can't remember when I started working on the work-a-round, but it was there when I posted http://forum.corsair.com/forums/showthread.php?p=857462.

 

For me to consider working with Corsair some within Corsair would need to eat rather a lot of humble pie! CL4 was/is developed by a 3rd party and I get the impression the CL product manager does not understand how poor the implementation is.

Link to comment
Share on other sites

Do you wish to do this? What would be need is:
  1. Register for power state change notifications
  2. On resume from sleep for each 7289 device do as below.
  3. Wait a while (By default SIV waits 15 seconds).
  4. Acquire the CL locking mutex.
  5. Disable the 7289 device.
  6. Enable the 7289 device.
  7. Release the CL locking mutex.

This is really the wrong solution, but only Corsair have (should have?) the 7289 driver source code and could implement the correct solution which is to fix the driver.

 

I would like to try this. I was also reading about DevCon. It is part of Windows SDK. It has the parameters to control drivers in device manager. Do you know of this as well?

 

For me to consider working with Corsair some within Corsair would need to eat rather a lot of humble pie! CL4 was/is developed by a 3rd party and I get the impression the CL product manager does not understand how poor the implementation is.

 

:laughing:! I know what you mean about management. At my place of work it seems they cannot get things done right as well.

 

Well, I will look into your list and see what I can come up with. I need to figure some of this stuff out on my own. How else am I going to learn? But the help is much appreciated.

Link to comment
Share on other sites

I would like to try this. I was also reading about DevCon. Do you know of this as well?

 

Using DEVCON directly is a poor solution as if CL4 is interacting with the 7289 device when you do a DEVCON RESTART this may fail as CL4 will have the device open. I guess if you want a mickey mouse solution you could try doing sc stop CLink4Service, but I suspect the CL4 GUI may well restart the service before the DEVCON RESTART executes.

 

In SIV after claiming the lock it uses CM_Disable_DevNode() than CM_Enable_DevNode(). Your code will also need to scan all the DevNodes to find the 7289 devices that need to be restarted.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...