USB fails randomly. search here will not let me use USB?

Since the search here throws out USB as a term it is impossible to see if there is relevant posts here on this subject. Therefor, I must make a new question.

Okay, long story short. Mouse has taken to freezing up randomly, sometimes seconds from boot, sometimes as long as an hour. YES I have changed the mouse(wired), the keyboard, used a Bluetooth mouse, tried all the forums I can find to reset the windows UAC info, disconnected every usb device but the mouse/keyboard. Ran memtest for 14 hours. Used sfc /scannow. As far as the device manager knows everything is merry. A visual inspection of all ports shows no visible damage at 4X. As I am having this issue on 2 machines, similar but not identical, a P-55 and aZ-77, I believe it is a software issue. I hope someone here has new ideas or experiences to share that may help to resolve this as it renders these machines near useless.

My friend says the only solution to every windows issue is "Format C:". It would be nice if he were wrong....

Are you using usb 2.0 or 3.0 connections?

Have you install usb 3.0 drivers?

little more background. Machines are both over 4.5 years old and have never had any usb issue. Thus, YES, drivers for everything are installed and at least as far a (mentioned earlier) windows device manager are concerned are working very nicely. As they are P-55 and Z-77 both have 2.0 and 3.0.

More descriptively, the fail is a hard lock requiring turn off of power supply! the items all have power, ie, all lights stay on, just totally non-responsive. I have left them like this as long as 2 hours 10 minutes. They never come back.

I have actually removed every usb device except for the mouse/keyboard. Used in every available port. Ports appear to be pyhsicaly good.

I've seen that your mouse is a wired mouse. How old is it?
I have a MS mouse that had the same issue. It was a broken cable, about 1/2" from mouse.
As you use the mouse, the cable bends so many times, at the same point, that the copper breaks inside the wire. In some positions you have contact, in other you don't.
I've opened the mouse, cut ed the wire 4" and it began to work as new. I didn't cut ed near the connector. I've cut ed 2 cm (1") from it to have enough length to make a connection.
To open the mouse look for hidden screw under the label.

Hi,
This is a bad thing about KB3172605
The known issues of it killing blue tooth devices was removed when the new version was released this month
The fix was supposed to be issued by Intel.

So you might check and see if KB3172605 is installed
If it is create a system image before removing it to test.

Hello to both of you! As to the usb item in the uac. that is a enable/disable that is supposed to let the system turn off unused usb stuff. I have tried it both ways as I said in the first post. makes not difference and the system likes to reset it to the default of enabled anyhow. see below

I will certainly look for that KB. making a restore point is even kind of iffy now. Also, as you know Microsoft has made updating win 7 essentially impossible now. taking one out would likely be very possible, putting in anything now is not going to happen. Every person I know in 8 states and 4 countries has update made useless by microsoft and it is miraculously working again as soon as you are willing to swallow the poison pill of 10.


KB3172605 is not present. I have had it on just long enough to do the KB searches and verify that the uac setting to disable usb suspend is in fact still set to disable as it should be.
I am having to work the forum from a laptop as both desktops are now unreliable.

Do either of you know if there is a place to find out what shuts off after the fact, that is may be a log, recorder etc? the event logs I can find are incredibly long and I do not know what they are actually trying to inform me of.

one instance I see in event viewer here. 10/7/2016 3:59:43 calls it "bowser" the general tab says "The master browser has received a server announcement from the computer HELLHOLE that believes it is the master browser for the domain on transport Net8T_tcpio_(/ac340F02-443A-49D6-9887-7918B48B1FFAS). The master browser is stopping or an election is being forced." HELLHOLE is my other desktop which at that time was only on running memtest 86 which it is now doing for 48 hours trying to get to some magic number of 8 runs. It should thus have not had any interactions w/ this machine of which we are discussing. that error is one of many most of which are repeating at some time in every run of the computer. I made a short log text of the descriptions and will try and get it on a doc to put up if you think that could help/