this BUG Code error is not gone, the laptop has been running clean for 7 days with no crashes.
the first thing I did after receiving the laptop was check the drivers and found the Dell wireless driver needed an update . after the update was installed ms update kept saying it needed to be updated but would also fail every time. I then found a ms fixit tool for this update issue of a driver already installed, and it got rid of it. also cleaned each USB port with compressed air and ran ms update until fully updated. according to the event viewer summary screen it is now running clean. Thanks to all who provided insight and recommendations.
You can also watch this video on how to trouble shoot BSOD's from Bill Detwiler. It's pretty easy to follow and can be very helpful and you'll learn something new. Microsoft has a tool called WinDbg and this video show's you how to use it.
I did download the debugging tools from Microsoft and ran the debugger with the 4 minidump files created from the crashes. Thanks for the link to the video, I'll watch it tomorrow. I do not have the problem laptop in my possession as yet, my daughter attends college about 400 miles north of here, we're in the process of swapping laptops via FedEx so I can begin to troubleshoot the thing. so far I've ran the Dell hardware check and everything passed, and reinstalled Windows 7 and all Windows updates. also went to the Dell website and downloaded the latest drivers. did that this last Saturday, Sunday morning after turning it on and after logging onto the internet it blue screened again.
I've noted each of the 4 minidump files are the exact same codes.
That certainly seems to point to the USBHUB.sys file. The problem is determining if the file is actually causing the errors or if there is some other program, service that is trying to access the file that is causing the problem.
Other than that the USB drivers are native to Windows 7. I don't think that will really help though.
If your daughter is using USB devices have her disconnect them and if possible disable their drivers and see if the problems continue.
If she has not been having the problem long, if she can remember when the problem started try system restore, and restore the system back to a date just prior to when the system started giving errors. For more on system restore please check out the following link.
If you get the error fairly often you can try msconfig to narrow down what the possible problem is.
Click start and search for msconfig and then double-click on msconfig.
Click the services tab and then check "hide all Microsoft services" then click disable all.
Click the startup tab and then click disable all.
Click ok and allow the system to restart.
When the system comes back up do you notice the errors? If there is a difference then there is likely a program of some type that is causing the errors. At this point you can try using process of elimination in msconfig to try to narrow down the cause. Return to msconfig, and enable the services while leaving the startup group unchecked. If the problems return then that indicates that it is one of the services that is causing the problems. If the problems don't return, since it is the startup groups that are disabled, it implies that one of them is causing the errors.
Once you have learned if it is a service or a startup group that looks to be causing the issue, you can return to msconfig and check half the group that seems to be causing the problem. That way if the errors don’t occur it points to half of the files disabled is where the problem lies. Of if the errors return it points to the half that is enabled.
This way you can keep going back to the list enabling half of them again, and keep dividing and concerning until whatever file is left is the problem file.
If the errors continue and you just can't seem to narrow down what is causing them, about the only thing I can suggest after that is either reinstalling Windows and if the problem continues afterwards have the system board replaced.
Bodega101
5 Posts
1
February 15th, 2012 15:00
this BUG Code error is not gone, the laptop has been running clean for 7 days with no crashes.
the first thing I did after receiving the laptop was check the drivers and found the Dell wireless driver needed an update . after the update was installed ms update kept saying it needed to be updated but would also fail every time. I then found a ms fixit tool for this update issue of a driver already installed, and it got rid of it. also cleaned each USB port with compressed air and ran ms update until fully updated. according to the event viewer summary screen it is now running clean. Thanks to all who provided insight and recommendations.
AardvarkTC
14 Posts
0
February 1st, 2012 18:00
Sounds like an incompatible driver.
msdn.microsoft.com/.../ff560407%28v=vs.85%29.aspx
You can also watch this video on how to trouble shoot BSOD's from Bill Detwiler. It's pretty easy to follow and can be very helpful and you'll learn something new. Microsoft has a tool called WinDbg and this video show's you how to use it.
Good luck,
Bryan
AardvarkTC
14 Posts
0
February 1st, 2012 18:00
Forgot to attach link for the video: www.zdnet.com/.../33558
Bodega101
5 Posts
0
February 1st, 2012 19:00
I did download the debugging tools from Microsoft and ran the debugger with the 4 minidump files created from the crashes. Thanks for the link to the video, I'll watch it tomorrow. I do not have the problem laptop in my possession as yet, my daughter attends college about 400 miles north of here, we're in the process of swapping laptops via FedEx so I can begin to troubleshoot the thing. so far I've ran the Dell hardware check and everything passed, and reinstalled Windows 7 and all Windows updates. also went to the Dell website and downloaded the latest drivers. did that this last Saturday, Sunday morning after turning it on and after logging onto the internet it blue screened again.
I've noted each of the 4 minidump files are the exact same codes.
Thanks for the response!
Bodega101
5 Posts
0
February 1st, 2012 20:00
data from the bug check analysis tool:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8006748160, TimeoutContext - PortData
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88003daba60 to fffff80002c9bc40
STACK_TEXT:
fffff880`033c4c18 fffff880`03daba60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033c4c20 fffff800`02f929e3 : fffffa80`066bf050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02e3c2b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033c4c80 fffff800`02ca6001 : fffff800`02e3c200 fffff800`02f92901 fffffa80`03b62b00 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`033c4cb0 fffff800`02f36fee : 00000000`00000000 fffffa80`03b62b60 00000000`00000080 fffffa80`03b4e740 : nt!ExpWorkerThread+0x111
fffff880`033c4d40 fffff800`02c8d5e6 : fffff880`031d3180 fffffa80`03b62b60 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033c4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`03daba60 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbhub
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15
FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
DELL-Terry B
4 Operator
•
3.5K Posts
0
February 3rd, 2012 14:00
That certainly seems to point to the USBHUB.sys file. The problem is determining if the file is actually causing the errors or if there is some other program, service that is trying to access the file that is causing the problem.
You can try reinstalling the chipset driver
www.dell.com/.../DriverFileFormats
Other than that the USB drivers are native to Windows 7. I don't think that will really help though.
If your daughter is using USB devices have her disconnect them and if possible disable their drivers and see if the problems continue.
If she has not been having the problem long, if she can remember when the problem started try system restore, and restore the system back to a date just prior to when the system started giving errors. For more on system restore please check out the following link.
support.dell.com/.../document
If you get the error fairly often you can try msconfig to narrow down what the possible problem is.
Click start and search for msconfig and then double-click on msconfig.
Click the services tab and then check "hide all Microsoft services" then click disable all.
Click the startup tab and then click disable all.
Click ok and allow the system to restart.
When the system comes back up do you notice the errors? If there is a difference then there is likely a program of some type that is causing the errors. At this point you can try using process of elimination in msconfig to try to narrow down the cause. Return to msconfig, and enable the services while leaving the startup group unchecked. If the problems return then that indicates that it is one of the services that is causing the problems. If the problems don't return, since it is the startup groups that are disabled, it implies that one of them is causing the errors.
Once you have learned if it is a service or a startup group that looks to be causing the issue, you can return to msconfig and check half the group that seems to be causing the problem. That way if the errors don’t occur it points to half of the files disabled is where the problem lies. Of if the errors return it points to the half that is enabled.
This way you can keep going back to the list enabling half of them again, and keep dividing and concerning until whatever file is left is the problem file.
If the errors continue and you just can't seem to narrow down what is causing them, about the only thing I can suggest after that is either reinstalling Windows and if the problem continues afterwards have the system board replaced.
TB
DELL-Terry B
4 Operator
•
3.5K Posts
0
February 16th, 2012 06:00
Thanks for posting and letting us know the outcome.
TB