Usb Root Hubs Show Yellow Triangle And Error 39

I am having HD problems and will be replacing it. I have coaxed it back to some degree with Restore but have USB problems as all USB Root hubs show yellow triangle and Error 39. Rest of USB Host controllers show "working properly". I have my mouse and keyboard working through PS/2 ports now, so have some control. Should I just uninstall each Root hub and reboot or what? I want to get enough working so that I can copy files from old to new HD, if possible. My Comp: HP d4996t desktop, Win 10 Pro v 1511, Core 2 Quad 6600, 4 gig ram, 400 gig Seagate squealing and ill. 1 tb WD coming to replace it. If I can keep old one alive I might be able to copy files from one to the other?? I also have a Macrium Image and Rescue disk to help. Suggestions/solutions appreciated. Also concerned with free updating Windows on new HD.

 

Yes.
Do one at a time at look if there's a difference.

 

Doing so now. Will report results. Thnx/

 

I did the last one at the bottom of the list of 8. Shut down and restarted. Got this " Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
{Bad File}
The attributes of the specified mapping file for a section of memory cannot be read." as a reply to clicking on 8, which had returned after uninstalling it with the yellow triangle.

 

Running sfc /scannow in Command Prompt(Admin) will scan for system file errors.
Might be worth trying.
s.

 

Attempted to install new driver and returned this message "encountered a problem install software driver for the device", further, that it found the software on the computer but encountered a problem while trying to install it, and suggested going to mfgr of device (intel) and look for software there.

 

Successfully ran SFC and these were the files that it found corrupted and would not install. What should I do with this information? I have a companion HP laptop that has the 8 USB root hubs that work just fine. Is that of any help? I am writing this on the laptop.

https://col131.afx.ms/att/GetInline.aspx?messageid=3759e997-4ad9-11e6-85e5-002264c1d610&attindex=1&cp=-1&attdepth=1&imgsrc=cid%3ainlineImage0&cid=d0f2e551d150ea6b&blob=MHxMb2cgZmlsZXMuSlBHfGltYWdlL2pwZWc_3d&hm__login=rovingus&hm__domain=outlook.com&ip=10.148.52.8&d=d2297&mf=0&hm__ts=Fri%2c%2015%20Jul%202016%2022%3a12%3a41%20GMT&st=rovingrv&hm__ha=01_2af9edd263005e5a64cdc3a5c5b35187da5bdfb65124de81fd47875b2bedadea&oneredir=1

 

Can't see the attached files in your thread #7.
You can use the Command DISM to repare the files that SFC finds corrupted. I think you need to have an ISO of the widows 10 installation disk which you need to mount... Have a look at
How to fix corrupted opencl.dll in Windows 10, if SFC and DISM are failing?
There is a response in that link towards the bottom that has 30 ticks associated with it. I used that to get me out of a crises. Forgot what the problem was...
Hope you find an answer.
s.

 

Here are the three logs: CBSPersist_20160616142431.cab
CBSPersist_20160618150628.cab
CBSPersist_20160701141746.cab
I'll give your other suggestions a try also.

 

Many thanks to all of you for your suggestions and help. With your suggestions and trial and error I finally got two front USB ports to be recognized allowing me to plug in my Transcend external backup HD and get to my Macrium HD backup files. I was able to Restore back to June 5 and after doing so all of my Root hubs came back to life and at this point all seems OK. At least until the HD finally dies, as it still squeals during the boot process. I will get it installed next week I hope so it will be ready for the upcoming big update of Win 10. Another affirmation of BACK UP, BACK UP. Again, thanks to all!