USB Insertion troubleshooting

To find out what  is causing this problem we must  log USB insertion.

USB insertion is not a logged event in windows event viewer by default. 

You can create event traces for USB devices using logman by following these steps located in this Technet article:

In an administrative command prompt enter the following:

logman create trace -n usbtrace -o %SystemRoot%\Tracing\usbtrace.etl -nb 128 640 -bs 128

logman update trace -n usbtrace -p Microsoft-Windows-USB-USBXHCI (Default,PartialDataBusTrace)

logman update trace -n usbtrace -p Microsoft-Windows-USB-UCX (Default,PartialDataBusTrace)

logman update trace -n usbtrace -p Microsoft-Windows-USB-USBHUB3 (Default,PartialDataBusTrace)

logman update trace -n usbtrace -p Microsoft-Windows-USB-USBPORT

logman update trace -n usbtrace -p Microsoft-Windows-USB-USBHUB

logman update trace -n usbtrace -p Microsoft-Windows-Kernel-IoTrace 0 2

logman start -n usbtrace

This will create a trace at %SystemRoot%\Tracing\usbtrace.etl
 This log can become excessively large and logging all activity for the USB stacks is not going to be a good idea between multiple sessions, this is more for troubleshooting USB activity.

Alternatively, you can do this with a third-party utility. This is a good one to log USB activity: http://www.nirsoft.net/utils/usb_log_view.html 

USBLogView is a small utility that runs in the background and records the details of any USB device that is plugged or unplugged into your system. For every log line created by USBLogView, the following information is displayed: Event Type (Plug/Unplug), Event Time, Device Name, Description, Device Type, Drive Letter (For storage devices), Serial Number (Only for some types of devices), Vendor ID, Product ID, Vendor Name, Product Name,