I have started to get a BSOD on Boot-up, and this has happened a number of times. On boot-up, the system crashes, reboots and goes through the Startup Repair process, and all is well. Then the next time I boot up it happens again.
Can anyone help me with this, please?
I attach the files as requested.
I have a new (3 months old) system (64 bit) with full retail Win 7
It appears to be a problem with the parent USB driver during enumeration. This is a default driver for composite devices such as keyboard and mouse. Check all cabled devices connected via USB. Also check that you have current drivers from the OEM of the devices.
By the way--Any relation to the "plating" family?
Thank you for your quick response. I had a BSOD problem about 2 months ago that seemed to be about the USB driver. It went away after some investigation, but I really didn't quite know why - I didn't change the driver, nor any of my devices.
Windows update tells me that I have an up to date driver.
Is there any way to tell whether it is a problem with the driver, or my hub ( have a powered Belkin USB hub), or a device?
Not sure about your reference to the 'plating' family, so I guess no connection
LOL... No problem about the plating. Just thought I'd mention I'm a long time user of their products of the same name. So there goes my discount. :)
The USB enumeration is at start-up so it could be your Belkin hub. This is more likely hardware related. The BIOS does a quick check of USB hubs but it's the driver that assigns the hardware for Windows (enumeration). Check for loose or poor connections. Sometimes a simple unplug/plug a few of times will clean the contacts. Do the same for all USB connected devices and their power supplies. (With the PC powered off.)
Also check the USB hub assignments in Device Manager to see if your GoFlex drive is sharing a machine hub with another device. If it is, a change in ports may help. Normally not a problem but some drives will over-draw current at startup and this will cause the hub to shutdown temporarily while the Windows driver thinks it's still active.
Quote