|
Turned the entire system off
Pulled the cord out of the wall
Waited more than five minutes
Behavior remains constant
|
|
|
|
|
Get: USBDeview[^] ... it's freeware and might be able to tell you something you don't already know about your USB configuration.
|
|
|
|
|
I'm guessing The "_Download USBDeview for x64 systems_" is the one I want
HUH ???
Ran it
Did not do a thing, just ran it; changed nothing
Fixed it
Huh ?
You young people know so much about these computers !
|
|
|
|
|
It was probably the USB controller chip had got wedged, and the process of querying it about all USB devices reset it.
I've had cases on my old desktop (an HP Z420) like the one you had, where Device Manager indicated that the USB controller had just stopped responding...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Something to try;
A couple of times while working on Arduino projects the USB ports shut down and kept getting a "Unrecognized device" error or it just didn't work.
After much knashing of teeth and pulling of hair I found a sight that suggested;
Shut down computer
Unplug main power (very important) for 30 seconds
Start back up
This reinitializes the USB ports and it will reload drivers for the devices that are plugged in.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Powered down and waited five (plus) minutes
Pulled every single USB item out of the machine; even the mouse and keyboard
This also included my USB WIFI thingy which is my internet connection.
Reboot produced the same result.
Does windows find the new drivers on the interent during boot ?
|
|
|
|
|
C-P-User-3 wrote: Does windows find the new drivers on the interent during boot ?
Drivers are already on your device, just looks for the current one.
Sorry it didn't work, was a long shot and worth the try.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Beware that a "soft" power down is not a complete power down, and won't reboot your PC completely. The PC can be configured to come back to life again at a selection of events, such as network requests, keyboard activity etc. So the circuits handling such interrupts must be powered, and driver software ready to handle them.
For a complete boot, you have to turn off the power through the mechanical switch on the power supply, or unplug the power cable. I have had problems that persisted across a "soft" power down, but disappeared when I turned off the power supply switch for a couple minutes.
I mainly work on old style tower cabinet PCs, rather than portable ones. I guess that unplugging the power supply from a laptop will not do the trick - the battery will keep the wakeup functions powered. So on a laptop, you probably have to remove the battery for a minute or two.
(Several years ago, I learned the hard way that a soft power down is not a full power off: I did a Windows shutdown, opened the PC cabinet to plug in another disk, accidentally dropping my keyring onto the mainboard. So I had to get myself a new mainboard.)
|
|
|
|
|
Also the default shutdown starting IIRC in w10 is to only terminate usermode and suspend/hibernate the kernel to allow a fast restart. Which is great, except when you need to bludgeon the system completely down because you think something went wrong.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
Restore to a previous restore point?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
maybe a motherboard problem. any diagnostics from Dell to confirm?
Still under warranty?
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
one potential reason: the interface on your desktop is broken and your USB is working.
diligent hands rule....
|
|
|
|
|
Try putting a bootable USB drive in the slot, hit F12 to go to the boot menu. If the drive does not show up or try to boot, you probably have a hardware failure.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Is your (USB) keyboard working so you can at least navigate around the BIOS?
Assuming you can boot from an external drive, or have a DVD drive that still works - try to boot from some so-called "live" Linux distributions that can work off the original media without being installed. If everything works, then you should at least be able to rule out a hardware failure, and the problem should be with Windows.
|
|
|
|
|
I don't even have any USB on the laptop, Even if a ZAP came then that's messed up, Bruh.   
|
|
|
|
|
DEll's next-day business support is usually great... what was their response?
|
|
|
|
|
Do you have a (recent) System Restore Point you can go back to? Doing that is reversible, in case it screws up something else.
Paul Sanders.
Some of my best work is in the undo buffer.
|
|
|
|
|
How old is your system? If it's fairly old, you might be having power supply issues. The electrolytic capacitors in the supply degrade over time and can honk up your voltage levels. This capacitor degradation happens even if the supply isn't being used. If you've got a volt meter, you might want to check your supply levels. I've had systems at work that would start acting flaky and the fix almost always turned out to be a dying power supply. I've learned over the years to NEVER skimp on the power supply.
|
|
|
|
|
Sorry if this has already been said. I'm too lazy to read every response before posting.
Could be physical damage to the motherboard. Some (older) motherboards have fuses specific to usb. I suspect that even mbs that do not have fuses would have north bridge regulation components specific to the ss usbs, so that could be damaged. As to what caused it, it could be that you have been red-lining it without knowing it, accidental static discharge, or perhaps a driver update caused a device to draw more power than before. Some devices may even increase their own power demand over time, like fans as dust builds up or the lube wears out.
I accidentally destroyed one of my mb's ss usbs by sticking a thunderbolt into it, shorting some of the many pins. This is in spite of the usb standard being very clear that short-circuits between any pin pair should not cause damage.
|
|
|
|
|
Wordle 325 2/6
⬛⬛🟨🟩🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 325 4/6
⬜⬜⬜🟨⬜
⬜⬜🟨⬜⬜
⬜🟩⬜⬜⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
4 again:
Wordle 325 4/6
⬜⬜⬜🟨⬜
⬜⬜🟨⬜🟨
🟨⬜⬜🟨⬜
🟩🟩🟩🟩🟩 That was a lucky guess ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yeah, you stare at the ceiling and you find the answer! 
|
|
|
|
|
"Pine beams supporting the floor above"?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Well, in tropical countries you don’t have pine beams!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
