BSOD Bugcode_usb_driver. Uploading dumpfile and sysinfo in thread.Help

[13goyal]

Ive been having this BSOD problem for almot 4-5 months now. Earlier no error code was displayed. But now it displays "BUGCODE_USB_DRIVER". Someone please help me out with this.

 

[HarriePateman]

Hello and welcome to SevenForums.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck [COLOR="Red"]FE[/COLOR], {8, 6, 5, 87c3b760}

Probably caused by :[COLOR="red"] usbhub.sys ( usbhub!UsbhTrapFatalTimeout_x9f+28 )[/COLOR]

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="red"]BUGCODE_USB_DRIVER (fe)[/COLOR]
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 00000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 00000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: 87c3b760, TimeoutContext - PortData

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR="red"]WIN7_DRIVER_FAULT[/COLOR]

BUGCHECK_STR:  [COLOR="red"]0xFE[/COLOR]

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

LAST_CONTROL_TRANSFER:  from 9186acc5 to 82f27bfc

STACK_TEXT:  
8c587ca4 9186acc5 000000fe 00000008 00000006 nt!KeBugCheckEx+0x1e
8c587cc0 91853f6d 8535e028 00000005 87c3b760 usbhub!UsbhTrapFatalTimeout_x9f+0x28
8c587cec 8305d629 8535e028 87c3b760 853e1d48 usbhub!UsbhHubProcessChangeWorker+0xa2
8c587d00 82ec614b 860d6138 00000000 853e1d48 nt!IopProcessWorkItem+0x23
8c587d50 83052141 00000001 a9852f49 00000000 nt!ExpWorkerThread+0x10d
8c587d90 82ef9559 82ec603e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhTrapFatalTimeout_x9f+28
9186acc5 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  [COLOR="red"]usbhub!UsbhTrapFatalTimeout_x9f+28
[/COLOR]
FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5295476f

IMAGE_VERSION:  6.1.7601.18328

FAILURE_BUCKET_ID:  [COLOR="red"]0xFE_usbhub!UsbhTrapFatalTimeout_x9f+28[/COLOR]

BUCKET_ID:  0xFE_usbhub!UsbhTrapFatalTimeout_x9f+28

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfe_usbhub!usbhtrapfataltimeout_x9f+28

FAILURE_ID_HASH:  {e8cd5874-a9ac-119a-2f84-d215f16f34d5}

Followup: MachineOwner
---------

Okay so we know it is cause by a USB driver. So lets start with some simple solutions.

Firstly Uninstall any USB Drivers you have and reinstall them with new drivers.

1. Right click on Computer icon > manage. It will open the computer management window.
2. Click on "Device Manager" in the left pane, it will list all installed devices up.
3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
4. Click on one item to select, then right click and uninstall.
5. Do the same for all.
6. Restart the computer.
7. At restart, windows will auto configure the appropriate drivers.

Let me know how this goes.

 

[13goyal]

Hey Harrie,
Thanks alot for replying to the post.
I have tried the possible solution posted by you this very morning but the BSoD has persisted.


Over the past months, unaware as to what to do, Ive got my hard disk, battery and the exhaust fan replaced to no avail. Could we move on to another possible solution?

Thanks!

 

[HarriePateman]

Okay, try running driver verifier a tutorial on how can be found in the tutorials section.

 

[derekimo]

Here you go,

   Information

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

 

[13goyal]

Ran Verifier.exe. System crashed while rebooting. Uploading dmp

Hey,


Thanks for the instructions on how to run the verifier. I followed the instructions on how to run it and while I was rebooting the system after Enabling the verifier, BSOD occured thrice.

Ive attached around 6 dmp files. Please do check them out.

Im really hoping this will allow you to help me finally fix the problem!

Thanks!

 

[HarriePateman]

Okay brilliant:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {40, 0, 99baed70, 0}

*** WARNING: Unable to verify timestamp for [COLOR="red"]cnnctfy2.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="red"]cnnctfy2.sys[/COLOR]
Probably caused by : [COLOR="Red"]cnnctfy2.sys ( cnnctfy2+1e00 )[/COLOR]

Followup: MachineOwner
---------

This is your Connectify NDIS Driver.

 

[13goyal]

What can I do to fix this?

But I think you should also know that I had uninstalled Connectify for a long period and still got the BSOD!

 

[HarriePateman]

Here is a free tool to make sure the Driver is completely gone.

 

[13goyal]

Hey, It seems you forgot to post the link to the software that you said would help me get rid of the driver.

please link me.

 

[HarriePateman]

Guru3D - Driver Sweeper

Sorry

 

[derekimo]

Can you post this info,

To suggest the right steps, we need to see some more files. Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[13goyal]

Uploading sys info file

Hey, Im uploading the system info file.

 

[13goyal]

Hey Harrie, I was unable to understand how exactly to use the driver you linked to Me. It dint have any option to remove specific drivers. It had options only for removing NVIDIA and INTEL graphic drivers. Is there any other way?

 

[derekimo]

I see connectify still installed, and in your startup programs,

Connectify	c:\program files\connectify\connectify.exe	HP-PC\HP	HKU\S-1-5-21-4048547029-1265981774-1093888470-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Try using these instructions to uninstall,

Please save any work and exit other programs before proceeding with the uninstall. Note that the uninstaller will disconnect you from the the Internet and usually requires you to reboot.

Connectify's uninstaller can be reached in two ways:

1. In the Start Menu, select Control Panel, and then Programs and Features. In the list of installed programs you should see Connectify.

2. Simply double-click the program Uninstall.exe in the directory where Connectify was installed. This is usually c:\Program Files\Connectify\ for 32-bit Windows or C:\Program Files (x86)\Connectify for 64-bit Windows.

When the uninstaller runs, it will prompt you with the User Account Control settings dialog by asking if this program can make changes to your system. If you wish to continue with the removal process, you must select Allow.

On some systems, the driver uninstall can take several minutes and occasionally even require two reboots to complete. If so, the uninstaller will automatically run itself after the first reboot to wrap up the uninstall. When this happens please be sure to select Allow again when the computer reboots and Windows asks whether to allow the program to make changes to your system.

https://community.connectify.me/connectify/topics/how_do_i_uninstall_connectify

 

[13goyal]

Again BSOD. Latest dmp attached.

Hey, Ive done all that you guys suggested but I again just got a BSOD saying " BUGCODE_USB_DRIVER".

Im uploading the latest dmp. Please see.

 

[derekimo]

Please upload your info using this tool, single dump files are not enough info,

Additional information is required.

1. Download this file to your desktop or other convenient location,


Download



2. Double click on the file to run it.

3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

 

[13goyal]

files attached

Here you go. This seems to have all the Dump files present on the system.

 

[derekimo]

There are only dump files in that, did you let the tool finish?

There are a bunch of other reports we need from that tool.

 

[13goyal]

check out the revised one!