AOC E1759FWU only works on some USB ports on a machine
 

Good morning,

I recently purchased an external monitor from AOC, the E1759FWU model.
I have three PCs: 2 desktops (Based respectively on an MSI X99s SLI Plus and a Gigabyte AORUS Z170) and 1 one laptop (MSI GT70 from 2012).

I could only make my monitor work on only one PC, and it has to be plugged on the front USB plugs, otherwise no picture if I plug it on the rear of my rig. Since I can make it work on one PC (the desktop one with the MSI motherboard) and not on the others, the only conclusion I can draw at this moment is that you messed up something with the communication between the driver and the USB 3.0 controllers.

The symptom is that the screen is kind of recognized by the driver, but the external screen does not appear in the Device Management window under the "Graphics Device" section.

And before you ask: yes, I do have the latest version of Intel's host controller driver.

Thank you very much for your feedback.

Are you using the Y-cable that AOC is likely to send with their monitor?
If your problem is port dependent, I fail to understand how you came up with the driver messing up the USB communication when Windows will invoke the same driver in both cases.

If the device is not in Device Manager, Windows hasn't even selected which driver to use yet... It's not up to a device driver to grab a device, otherwise that'd be a security problem.
Your AOC monitor probably doesn't stay up because it doesn't get enough power to light up and it's got a brownout issue.

The last link in my forum signature also explains how to gather the logs files which can be posted here for relevant commenting.
I've renamed the thread to something a bit less abusive.

Kind regards,
Alban

Yes, and I plugged it on two ports.

That's a surprising statement as it worked fine while plugging it on the front ports on the only PC I could make this screen work. Plugging them on the rear ports has no effect. The screen lights up, but all I get is an icon telling me to plug it on a PC.

Thanks I will check that as soon as I can.

Hello,
There is no difference in the driver based on which port you are connected. The connection path is not looked at by the driver. There can be a maximum connection depth (hub behind a hub behind a hub), but I don't see it being in play here.
There is an expected difference in characteristics, like power they can deliver, between ports of the same machine based on location, and how much they have been used in the past.

Based on the information I had at the time, and the questions I've had about that monitor model in the past, the most likely explanation was the power.
However, as you now say the monitor is stable with an icon on the screen, that seems unlikely as the symptoms tend to be a reboot loop with screen flashing.

We can see with the logs gathered when connected, what is the status for Windows. The key first information is to see if a device is recognised by Windows.
If it is identified properly, then we can look at the driver side and the logs will tell me what takes place.
If there is no device properly identified, then the issue is before the driver is selected by Windows, so we need to look on the monitor side.

Regards,
Alban

Please find attached the archive generated by the support software

Hello,

This machine has 3 USB Host Controllers (USB HC).
The logs show there was no enumeration of the device. This means the driver is not invoked yet by the Windows as there's no device seen.

The reason you could have a different behaviour on some USB ports is because they are connected to different host controllers.

You're mentioning you have the latest Intel host controller drivers... In these logs, the Intel USB HC is using the Microsoft inbox driver, and that's fine.
The VIA USB HC also uses the Microsoft inbox driver.
However, the ASMedia USB HC uses its custom driver.

Do you know which USB HC is used in the both the working and non-working cases?
Unless Windows sees and talk to a USB device, which is identified then the driver won't be invoked because it doesn't know the device is present and doesn't know what driver to select.

Kind regards,
Alban

Name: Contrôleur hôte VIA USB*3.0 eXtensible*-*1.0 (Microsoft)
Driver Provider: Microsoft
Driver Version: 10.0.16299.125
Name: ASMedia USB3.1 eXtensible Host Controller
Driver Provider: ASMedia Technology Inc
Driver Version: 1.16.36.1
Name: Contrôleur hôte Intel(R) USB*3.0 eXtensible*-*1.0 (Microsoft)
Driver Provider: Microsoft
Driver Version: 10.0.16299.125