New
#31
Noel, I followed your instructions and am running sfc /scannow. Will post log file when it's done. I hope I did this right.
Noel, I followed your instructions and am running sfc /scannow. Will post log file when it's done. I hope I did this right.
Here is the log file.
Here is the screenshot after running drivecleanup. Should I have rebooted before taking the screenshot of device manager? It looks the same as before.
Last edited by Brink; 11 Jan 2015 at 13:32. Reason: blocked out your serial number that you do not want the public to see
Thanks Crabby,
First a few things that will help communicate information on the forum
1) screenshots: Alt+PrtScn grabs just a window, not the full screen.
You still have to paste it into Paint and save it though. It makes it easier to read, that's all.
2) System information: I prefer Speccy reports - just my preference.
But ... keep in mind any time you post anything to review it before posting.
Many reports or screenshots contain information you wouldn't want on a public forum (such as your eMail address)
Paint has an eraser that makes it easy to remove anything from an image that you think should be kept private.
Just a heads up for your own privacy.
See if re-installing the USB chipset drivers solves the problem
I reinstalled the USB chipset drivers earlier in the week and it didn't work... I tried it again just now and the USB ports still don't work. I have attached a screen shot of device manager. Hope I did the screen shot right this time.
The install fixed the unknown device - most likely the USB eXtrensible host controller.
It is now known, but it still has an error.
I'll have to dig a little deeper.
This Chipset update seems as though it only changes the name shown in Device manager.
While I dig around some more, please do two things
1) install the above driver Chipset update - even if it only cosmetic.
2) Manually run Windows update and look in the optional updates section.
Select all that are offered that are related to the issue. There might be some that are touchpad, monitor, or network adapter related - don't select those at this time, you can and should come back to select those updates later.
I'm trying to limit the changes specifically to the issue at hand - the USB controllers
If you're not sure, post a screen shot of the optional Windows Updates and I will review and advise.
You seem fairly capable though.
Bill
.
Please also double click on each of the problem devices in Device Manager and post a screen shot of the general property tab.
This should show the error.
Thanks again.
Bill
Don't do anything with this yet, I'm posting it for later reference.
Your BIOS is version F.0B (from the HP assistant image), but the HP support site only show BIOS F.0A
BIOS F.0A
Don't go any further with this post until I get back to you.
There's either a typo on the HP support page, the HP assistant is wrong, or you have the wrong BIOS.
I'll try to figure out what BIOS F.0B is on the HP site and how it might have been put on your machine. It's too much detective work to really figure out what happened, so I just have to verify what HP has (is it a typo?? or is F.0A the version you need).
It's interesting from a technical standpoint, that F.0B didn't brick your machine. PCs are commodities and the difference between one model and another from the same vendor might be minor and you skated by with only the USBs being affected.
So again, hold off on doing anything in this post.
Thanks,
Bill
.