BSOD on shutdown - tried everything

Hello! I have been getting a BSOD everytime my computer shuts down or tries to hibernate for about 2 months now. The STOP codes are as follows:

0x0000007e (0xc0000005, 0x993ca1b8, 0xa3aa0b30, 0xa3aa0710)
usbhub.sys

I finally had time tonight to try to resolve it and have got nowhere. My Computer specs are as follows:
Windows 7 Ultimate 32-bit: upgraded from OEM Vista.
HP Pavilion tx2000 tx2117cl
Processor: AMD Turion(tm) 64 X2 Mobile Technology TL-62
Hard Drive: Western Digital WD25 00BEVS-00UST SCSI
RAM: 3GB
Graphics Processor: NVIDIA GeForce Go 6150
Wi-fi is a broadcom card of some flavor

I have owned this computer for almost 3 years.

I first tried to look at my minidump files, and there are none. I went to my advanced system settings and "Write debugging information to" was set to "Kernel Memory dump". Since the dump file was not in "C:\Windows\MEMORY.DMP" like specified, I switched it to "small memory dump 128k" and shut down. I still have no minidump files on my computer as far as I can tell.

Then I installed a hotfix for this issue Link
Which did nothing.

I enabled the driver for my Authentec fingerprint reader and updated the driver with DriverMax. I did this because I found a thread on another forum where updating all his drivers with this program fixed this BSOD on his vista computer. I have never used a driver program like this before.

I couldn't update them all with the free version, only 2 a day. I tried googling for the files instead of going through drivermax, but since the devices that needed updating are OEM specific, I was nervous about installing anything from another laptop.

I didn't see any other USB devices that needed updating. To make a long story short, this helped nothing. I used System restore to undo it and disabled the fingerprint reader in the device manager, because I know it has a hardware problem that prevents it from working. Namely my daughter was eating glazed doughnuts and trued to use it and it hasn't worked properly since, even though it's recognized fine by the computer.

I also tried to find information in Event Viewer. I made a filter to filter all 1001 and 1003 events and the newest thing I found was a "BugCheck" event on december 29th. This is where I found the BSOD info:

param1 0x0000007e (0xc0000005, 0x993ca1b8, 0xa3aa0b30, 0xa3aa0710)
param2 C:\Windows\MEMORY.DMP
param3 122510-29109-01

that dump file is not anywhere on this computer. That event also happened on days previous to Dec 29th, but not after.

I noticed perfmon shows my OfficeJet 7310 printer as being disabled. I don't know why, it works fine. Although recently my option for automatic duplexing has disappeared. I troubleshot the printer itself and the duplexer is installed and recognized and works. I believe this is due to a communication error of some sort, probably related to what I observed in perfmon. I am not asking for help on that, I just wanted to mention it. It is not connected via USB, but over the network.

Since I ran across this forum multiple times when googling for information, I decided to join and seek help. I sincerely have no more ideas as to what I should do. I appreciate any and all ideas related to this, thank you.

My required files are attached to this post

There is no dump files in the jcgriff folder.

Navigate to C:\Windows\MiniDump\
Select all of the dumps in the MiniDump folder and copy all of it to your desktop.
On your desktop, zip the dumps into a .zip or a .rar file.
Upload it in the Seven Forums Attachment.

N.B: If you have CCleaner, make sure it doesn't remove dump files.

EDIT:

If you do not have a minidump folder, create one "Minidump" (without the quotations) in C:\Windows\

The Minidump folder exists, but there are no files there. I can't figure out why. I do use CCleaner, but haven't ran it in a few weeks. Thanks for your input.

Go to CCleaner Settings and make sure it doesn't delete dump files.

I do not know where to navigate - I never use Registry Cleaners before.

Just to add from Tews Suggestion.

Once you got a BSOD from Driver Verifier - just go to Safe Mode and turn it off.

DeanP said:

Go to CCleaner Settings and make sure it doesn't delete dump files.

I do not know where to navigate - I never use Registry Cleaners before.

I know how to disable this. I do not use the registry cleaning portion of this program, only the temp file deleting portion. It does not run in the background. I have to manually run it. Regardless I will disable the deletion of minidump files.

Tews said:

Lets enable Driver Verifier ... this will stress the drivers and will force a BSOD and create a .dmp file and hopefully we will be able to narrow down your problem..

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

I will report back with the results of this. Thanks for the suggestion!

I ran the Driver verifier as instructed. Upon reboot, I got a BSOD before it got to the login screen, The screen was showing the windows flag when it happened. The stop codes are as follows:
0xc9 (0x23B, 0x8E1ECA8C, 0x94592ED8, 0x0)

I restarted the computer again to see if it would happen again in the same way and it did. So I booted into safe mode as suggested by DeanP and deleted the Driver verifier settings. To exit safe mode, I just restarted normally and while shutting down, I got the original BSOD that is in the OP.

I assume you would like to see the minidump files from this. Unfortunately, there are none in my minidump folder, just like before. I also checked my BSOD filter in Event Viewer and there's nothing there either.

What's my next move?

nevarDeath said:

I ran the Driver verifier as instructed. Upon reboot, I got a BSOD before it got to the login screen, The screen was showing the windows flag when it happened. The stop codes are as follows:
0xc9 (0x23B, 0x8E1ECA8C, 0x94592ED8, 0x0)

I restarted the computer again to see if it would happen again in the same way and it did. So I booted into safe mode as suggested by DeanP and deleted the Driver verifier settings. To exit safe mode, I just restarted normally and while shutting down, I got the original BSOD that is in the OP.

I assume you would like to see the minidump files from this. Unfortunately, there are none in my minidump folder, just like before. I also checked my BSOD filter in Event Viewer and there's nothing there either.

What's my next move?

The first BSOD codes from the previous were memory exceptions caused either by a driver passing bad data or the memory itself

If you have not download memtest burn it, boot from it, and run it for 6-7 passes.

This current BC code indicates driver verifier was running and did capture at least some data on the crash but we need the DMP file to see what.

If you cant boot from the computer normally can you boot in safe mode?

if not here are some comprehensive instructions that may help. If they dont let us know

Beyond that, please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users