For the sake of having important information distributed in this thread, I’d like to point some things out here, though you may receive this information and help from our support team.
In the screen shot of USB controllers (http://i.imgur.com/pS7NgRY.png) you provided above, one can see that there are actually two USB 3.0 controllers on your system.
Except the “Intel(R) USB 3.0 eXtensible Host Controller”, there is also a “ASMedia XHCI Controller”. Maybe one comes with the mother board, and that the other with an externally connected USB 3.0 port, like a PCI card.
So, the first important thing is to decide which USB 3.0 controller governs the USB 3.0 port the EyeX Controller is connected to.
Unfortunately, if it is the ASMedia XHCI Controller, this is a known issue with no solution at the moment. Tobii EyeX uses libusb to access the EyeX Controller, but it seems the ASMedia USB 3.0 drivers do not respond correctly when libusb requests information about connected devices. The request fails with an error that there are no connected devices. We have been in contact with both libusb and ASMedia developers about this issue.
In your case, though, if you have another USB 3.0 port, that is governed by the Intel(R) USB 3.0 eXtensible Host Controller, the EyeX Controller may actually work with that port.
(For those who just jumped in on this thread: This is a problem seen on Windows 7, where each USB 3.0 port manufacturer have to provide their own USB 3.0 driver and root hub driver, and these drivers are not consistently implemented. In Windows 8, Microsoft provides a generic USB 3.0 stack.)