BSOD continues to happen

Hi -

The 6 BSODs all had the same bugcheck -

0xfe = USB hub driver encountered a fatal error

What is plugged into the USB ports?

Since the probable cause was listed as a Microsoft OS driver (usbhub.sys), run Driver Verifier -

https://www.sysnative.com/forums/bs...er-verifier-blue-screen-of-death-related.html

It will hopefully ID a 3rd party driver causing the problem, assuming one exists.

Regards. . .

jcgriff2


BSOD SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102313-20358-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Oct 23 17:52:57.246 2013 (UTC - 5:00)
System Uptime: 0 days 0:53:30.370
BugCheck FE, {8, 6, 5, fffffa8006cbbc80}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`00000005 fffffa80`06cbbc80
BiosVersion = F.1D
BiosReleaseDate = 10/05/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
MaxSpeed:     2130
CurrentSpeed: 2128

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102313-21060-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Oct 23 16:58:23.747 2013 (UTC - 5:00)
System Uptime: 0 days 1:36:30.887
BugCheck FE, {8, 6, 5, fffffa8006cfec80}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`00000005 fffffa80`06cfec80
BiosVersion = F.1D
BiosReleaseDate = 10/05/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
MaxSpeed:     2130
CurrentSpeed: 2128
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102313-21278-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Oct 23 15:21:18.894 2013 (UTC - 5:00)
System Uptime: 0 days 11:17:46.018
BugCheck FE, {8, 6, 5, fffffa8006cb6c80}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`00000005 fffffa80`06cb6c80
BiosVersion = F.1D
BiosReleaseDate = 10/05/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
MaxSpeed:     2130
CurrentSpeed: 2128
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102313-22339-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Oct 23 04:02:59.727 2013 (UTC - 5:00)
System Uptime: 0 days 11:23:02.226
BugCheck FE, {8, 6, 5, fffffa8006f8ec80}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`00000005 fffffa80`06f8ec80
BiosVersion = F.1D
BiosReleaseDate = 10/05/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
MaxSpeed:     2130
CurrentSpeed: 2128
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102213-80402-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 22 08:03:16.928 2013 (UTC - 5:00)
System Uptime: 0 days 11:40:45.052
BugCheck FE, {8, 6, 5, fffffa8006b9cc80}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`00000005 fffffa80`06b9cc80
BiosVersion = F.1D
BiosReleaseDate = 10/05/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
MaxSpeed:     2130
CurrentSpeed: 2128
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101413-28719-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Oct 14 04:51:55.803 2013 (UTC - 5:00)
System Uptime: 1 days 7:32:07.862
BugCheck FE, {8, 6, 5, fffffa8006cafc80}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`00000005 fffffa80`06cafc80
BiosVersion = F.1A
BiosReleaseDate = 04/01/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
MaxSpeed:     2130
CurrentSpeed: 2128
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

	    
             
       [color=#555555]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562][color=#555555][u]http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562[/u][/color][/url]   

           [url=https://www.sysnative.com][color=#555555][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#555555][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]
 
only a wireless mouse. Also, in talking to HP, I discovered that the touch pad is also connected via an internal USB port. When I have connected my smartphone, Kindle, or Neat scanner the usb port works fine but I only plug them in when I need to upload or download something to them. Will run the verifier as suggested and send the results.
 
only a wireless mouse. Also, in talking to HP, I discovered that the touch pad is also connected via an internal USB port. When I have connected my smartphone, Kindle, or Neat scanner the usb port works fine but I only plug them in when I need to upload or download something to them. Will run the verifier as suggested and send the results.

Do these devices have their own power source or do they use power obtained from the USB port?

When running Driver Verifier, please be sure to have all 3 devices plugged in as 3rd party drivers may load into RAM when the device(s) is detected.

It is a 3rd party driver that we are after. Driver Verifier will force your system to BSOD if it detects a violation in a 3rd party driver. If/when a BSOD occurs, please go to c:\windows\minidump, copy out the most recent dump to another folder such as Documents, zip it up and attach to your next post.

If a BSOD occurs and is listed as VERIFIER_ENABLED but names no 3rd party driver, then unknown hardware is the likely cause.

Regards. . .

jcgriff2
 
Last edited:
the kindle and the smartphone have their own power sources. the scanner seems to be powered by the usb.
 
Apologies for double post -- what is the exact model number of your HP dv7 system?

I'd like to check HP Support to see if there are any updates available, specifically for BIOS.

Thanks,

John
 
the kindle and the smartphone have their own power sources. the scanner seems to be powered by the usb.

OK... please be sure all are plugged into USB ports and are powered on.

If the scanner goes to sleep, please check for a setting to keep it on.

Driver Verifier needs to run for 24 hours minimum -- or BSOD, whichever comes first.

Use the system as you normally would; however, you may notice some slowness at times because Driver Verifier is utilizing system resources to stress-test the 3rd party drivers.

Are each of the 3 devices plugged into separate USB ports or do you use a USB hub device allowing >1 device to be plugged into 1 USB port?

Regards. . .

jcgriff2

EDIT:

p.s. What is a "kindle"? I'm not familiar with the term.
 
HP Pavilion dv7t-3100
VG420AV

HP Pavilion dv7 Notebook PC

Serial Number: CNF0171P12

HP Pavilion Entertainment PC

I just have plugged in all three devices.
The scanner is working fine. The phone is fine also. The Kindle had a yellow !
but I can access the Kindle files under Computer, Removable disk.

COULD THIS BE CAUSING THE CONFLICT??
 
I response to your above question....the USB devices are plugged into individual ports, two on the left and one on the right, directly into laptop, not multiplexers. A Kindle is the Ereader by Amazon which is a small computer (the Fire).
 
I appreciate the information -- thank you.

At this time, I would suggest that you let Driver Verifier do its job and hopefully it will force a BSOD and name a 3rd party driver.

Regards. . .

jcgriff2
 
HP Pavilion dv7t-3100
VG420AV

HP Pavilion dv7 Notebook PC

Serial Number: CNF0171P12

HP Pavilion Entertainment PC

I just have plugged in all three devices.
The scanner is working fine. The phone is fine also. The Kindle had a yellow !
but I can access the Kindle files under Computer, Removable disk.

COULD THIS BE CAUSING THE CONFLICT??

I just saw this ^^^^

Anything is possible.

Does Device Manager show a red or yellow flag next to the Kindle device?
START | type devmgmt.msc
 
Is there any message in Device Manager?

Double-click on the line-item; there s/b some type of message.

Also, click on the "driver" tab. What is the name and date of the driver?
 
It took all night and most of the day, but I finally got a BSOD. When I went to zip up minidump to send it to you, the folder is there but empty. I also had a problem restarting the computer and it had to go through so autmatic recovery.
 
Back
Top