Intel Motherboards : H97M Pro4 USB amperage

Author: parsec
Subject: H97M Pro4 USB amperage
Posted: 17 Sep 2016 at 9:48pm

maxik wrote: parsec wrote: I don't believe the manufacture's response about power. I'm also not sure I understand which configuration does not work on the H97M Pro4. Are you saying the cradle, when connected as you described, has the problems? But if you just use an extension cable into the adapter itself, that worked? Exactly. The original cradle or the USB extension from an older Netgear WG111 adapter are not working. The adapter directly in the PC is working. An extension of about 30cm (the one you normally get with mobile data devices - has 2 plugs that goes into the pc, normally 1 for power and the other for data) is working too parsec wrote: Another topic question, when it worked on the other, older PC, what version of Windows is used in that PC? Question about both PCs, do they have the ASRock APP Charger program installed? Working PC - Build 1511 Windows 10 Pro Faulty PC - Build 1607 Windows 10 Pro Both should have the App Charger program - I'm sure for the faulty pc parsec wrote: In the BIOS, H/W Monitoring screen, you should see the +5V power supply voltage shown. If it is below 5V, say 4.75V, then your PSU has a problem. On the H97M Pro4 PC, go into Device Manager, and open the Properties of any/all of the USB Hubs. In the Power Management tab, are the Allow the computer to turn off this device to save power options checked? If so, uncheck them. Next, open your Windows 10 Power Plan, and go the the Change advanced options screen. Open the USB settings, and see what the USB selective suspend setting is set to. If it is Enabled, try Disabled. Both of these things alone may fix the issue, so both may not need to be set as I suggested. Experiment if you care to have either of these setting Enabled. Also in the Power Plan Advanced settings, check the setting of the Wireless Adapter, Power Saving Mode, which has four settings. You can compare what you found for all these settings on the two PCs, which may explain the different behavior. Voltage is 5,064v and even with the modifications you told me it is not working. But just a couple of minutes ago i tested 2 more things and I got some very very interesting results: 1. Ubuntu Live system - Adapter with original cradle working 2. (And this is the funniest one) - I took the HDD from the PC where the cradle works and swapped it in the faulty one...guess what? Adapter and cradle are working again!!  Conclusion - this problem is Windows related. The only thing that i have to do now is figure out how to get a W10 iso with Build 1511. Or, last hope, switch back to Windows 7

By moving the HDD, you mean you put the Win 10 1511 version from the B75 board PC, into the H97 board PC, and then the cradle and adapter worked fine, is that right?

If so, that seems to indicate it's not the USB ports power on the H97 board that is the problem, but a difference in the Win 10 Pro builds. Which is what your conclusion is, right?

Going from that, if the driver for the netis adapter is the same in both Win 10 installations, then it seems a change in Win 10 1607 is somehow causing the problem.

What about any configuration differences in the netis adapter entry in Device Manager between the two Win 10 versions? Or is the driver different between the two Win 10 versions?

I can tell you that Windows 10 in general from its beginning, has caused problems for some networking drivers. The Intel wired networking chips have had two standard features broken in their drivers, teaming and VLANs.

Six Intel wired network driver updates later, and those features are still not working with Win 10. Intel acknowledges these features do not work with Win 10 on the newer driver download pages, or I should say warns us they don't work. One early Win 10 build version and one Intel wired network driver version still had teaming working, but that is long gone. This is true with current Intel network chips, on their latest, in production PC platforms.

You might be able to find a 1511 ISO out there, MSoft does not provide older versions AFAIK.


Edited by parsec - 7 hours 43 minutes ago at 9:50pm