You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

I know very little about computers and have tried my very best over the last few days to figure out how to analyse my blue screens to no avail. I've been getting blue screens on and off over the last few weeks. Usually they flash by so quickly that I can't see the codes, but this last one which occurred today I saw BUGCODE_USB_DRIVER. I've also had little notifications while using my computer that the USB device wasn't recognized or not functioning, even when there was no USB device plugged into the computer. None of the devices I have plugged in have had any problems functioning that I can remember.

I tried to update the USB drivers found under Device Manager, but it said they were all up-to-date. I can't think of any new USB devices that I've tried using that could have started the problem, but I could be remembering incorrectly.

I saw that on these forums, people usually request a readout from the minidump file after a BSOD. I've been trying for hours to figure out how to do that, with no success. I downloaded windows debugging tools and a symbol package, tried using command prompt to open the dmp file in windbg, but it told me it couldn't locate the file (and I triple-checked the file path, but this was my first time using the command prompt...). I then tried opening it from the debugger itself, put in the path to the symbol package and then tried to 'open crash dump', but upon selecting the proper file was told that I didn't have permission to open the file (even though I am the administrator).

I also tried running a disc check, but didn't really know what I was looking at.

If anyone can help me through this, I would be extremely grateful.

*I also have the worst timing of all time - I am leaving the country this Sunday, but thought I should post this before I left in case I could resolve the problem before leaving my laptop for a month. Barring that, perhaps when I get back, there will be some helpful posts to look at to get me started in the right direction.

Thanks - here it is. What I don't get is that it says on the minitoolbox readout that there are no minidump files, however, when I look in the minidump folder on my computer, I see a whole bunch (see screenshot).

CodeIntegrity Errors:
===================================
Date: 2012-12-20 02:36:10.063
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Windows\System32\drivers\PxHlpa64.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Date: 2012-12-20 02:36:10.016
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Windows\System32\drivers\PxHlpa64.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

I know that you only wish to help, but you need to learn when and why to suggest specific courses of action or testing. A Clean Boot is a good diagnostic tool, but it is meant to discern if there is a specific Service or Startup item is causing problems. A good indicator that this tool should be suggested would be if the problem does not occur in Safe Mode. Safe Mode has a very limited amount of drivers and services running, because of this a service or startup item which had been causing problems may not be running and run normally. This is when you would want to suggest running a Clean Boot. At this point nightheron12 has not posted anything that would suggest that a Clean Boot would be applicable.

Each tool is suggested because of the specific result it produces, you need to start thinking in those terms. Take the time to learn what the programs do and when they should be used and you can be of more help.

Family and loved ones will always be a priority in my daily life. You never know when one will leave you.

i hope i don't get shot from more experience members but looking at the amount of event log errors i would be tempted to do a clean reinstall of my operating system, after backing up my important files, reinstall my applications and go from there.

true,too use to ghosting an image at work,starts to become the normthinking about this i would do a manual check on the manufactures website for each device,Video, Sound, Nic, Wi-Fi, mouse,keyboard, and other specific devices, to see if all my usb driver is up to date, MS device manger up date is pants i feel and may well have old drivers.

Nightheron12 I realize that you have probably already left the country and will not be back for a month, so you will find this upon your return.

You need to update your Intel graphic drivers. You can find them at Intel's Download Center. You will need to set the operating system and version to find the correct drivers.

You also need to look in the Device Manager under DVD/CD-ROM drives. Click on the diamond just to the left of this to expand the tree, then double click on your optical drive.

A window will open with tabs across the top, click on Driver. When this opens click on uninstall. When you restart the computer the optical drive will be recognized as new hardware and drivers will be assigned to it.

Family and loved ones will always be a priority in my daily life. You never know when one will leave you.