when i try hooking up usb ddevices to my port ANY of them i get unknown device and when i double click that from device manager i get that error
Windows has stopped this device because it has reported problems. (Code 43)
plz help i dont mean to spam but this is actually a new problem i guess
http://www.filedropper.com/untitled_66 here is image of it all how do i fix this?
Hi, try this way to upload a picture.
A Preferred Method of Uploading/Posting Screen Shots
i have a hp pavillion dv8301nr windows 7 (64bit) 7600 rtm, allthou this happens in every version, i have a amd turion 64 ml-34 processor, and phenix f.54 (latest) bios, and i can only suspect i have the latest chipset drivers, i installed them from hp site, if someone knows a place where i can get the chipset drivers please provide me with a html link. i dunno which mobo i have i think ati something. anyways my problem is...
i have 4 USB ports, 3 are 1.1 and 1 is 2.0, no matter what i try to connect, the windows detects the device but says unknown device detected? i have tried everything to fix this, plz help, in device mngr it shows 3 usb communication processor controllers 2 are OHCI 1.1 and one is EHCI 2.0 under them i have 3 usb root hubs, when i plug something in an extra one pops up for every device and is named unknown device with a yellow exp. point. PLZ SOMEONE HELP ME, maybe you can find my mobo chipset drivers for me, i am not sure but i think ati makes my mobo since the internal gfx card is a 200m express ati. here is a similar problem but in the other post i havent mentioned about the 43 error, i think it is dif problem or it might be related thats why i started dif thred, and attached is my desktop scren shoot 620-220 16bit color for ez dl, it in sludes everest mobo specks and problem shoot when attaching a device, also what it looks like in device manager
Attachment 28045
Last edited by szalajko; 14 Sep 2009 at 16:35. Reason: forgot to attach file
I have the same problem, although i know why, i have an external hard drive which worked fine before, but recently the cable has been damaged and ever since i have had this problem.
I just thought it would be helpful for you to know this and that the problem might be that it has been damaged in some way.
Please update your bios and chipset drivers. Then in bios, disable all unused ports like serial, parallel, floppy, com....etc...
Yes Boothy. The error means things aren't communicating well. How you fixed it and what I say above are possible ways or alleviating. Yours is much more rare than my fixes. Good find!
Yes but as of now they don't have any official error codes with that number range posted anywhere. I've looked and the only thing MS has that I could find are XP error codes, and I'm going to bet my testicle that they mean the same thing. =P Why change error code meanings now? That'd piss some hard core tech's off.
Quote