BSoD Please Help me!

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by HeavenLee, Dec 14, 2011.

  1. HeavenLee

    HeavenLee New Member

    Joined:
    Dec 14, 2011
    Messages:
    2
    Likes Received:
    0
    Hello everyone,

    I am at my wits end and I don't know what to do. I keep getting the BSoD randomly. I reinstalled windows, I did window recovery and it still happens. I'm running windows 7 home premium. I am also running Norton Business class. I also attached the file from the SF diagnostic tool with all the info. Thank you soooo much in advance. ;)
     

    Attached Files:

  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Hello and welcome to the forum.
    If you have done a recent clean install of Windows 7, make sure to go here and update all your system drivers specific for your installed hardware paying particular attention to Chipset, Video, Audio, LAN, Wifi, and consider a BIOS update as well, looks like there have been several since your V1.10 November 2010.
    Your OP would suggest that this has been going on for a while, but your attachment only included a single dump file from today, additional files might prove useful in displaying a pattern.
    As Norton / Symantec products are often identified as being to some extent complicit in these types of issues, please uninstall it for now and follow up the conventional uninstall with this vendor specific proprietary removal tool and replace it with Microsoft Security Essentials for testing. You can change back later if it proves not to be at issue.
    Couple old pre-Windows 7 RTM drivers to address;
    NTIDrvr.sys 3/24/2009 and UBHelper.sys 4/27/2009 both seemed to be associated with NTI Software products, from NewTech Infosystems Inc. maybe NTI Backup NOW or NTI CD & DVD-Maker not sure. Update, or uninstall or last resort rename to .OLD extension.
    DUMP:
    Code:
    ....................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck FE, {8, 6, 5, fffffa8008a3e000}
    [COLOR=#ff0000][U][B]Probably caused by : usbhub.sys[/B][/U][/COLOR] ( usbhub!UsbhHubProcessChangeWorker+ec )
    Followup: MachineOwner
    ---------
    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: fffffa8008a3e000, TimeoutContext - PortData
    Debugging Details:
    ------------------
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xFE
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff88003041a60 to fffff80002c97c40
    STACK_TEXT:  
    fffff880`033f5c18 fffff880`03041a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
    fffff880`033f5c20 fffff800`02f8e9e3 : fffffa80`08a23050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02e382b8 : usbhub!UsbhHubProcessChangeWorker+0xec
    fffff880`033f5c80 fffff800`02ca2001 : fffff800`02e38200 fffff800`02f8e901 fffffa80`04167b00 fffffa80`04167b60 : nt!IopProcessWorkItem+0x23
    fffff880`033f5cb0 fffff800`02f32fee : 00000000`00000000 fffffa80`04167b60 00000000`00000080 fffffa80`04150040 : nt!ExpWorkerThread+0x111
    fffff880`033f5d40 fffff800`02c895e6 : fffff880`009e9180 fffffa80`04167b60 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033f5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    usbhub!UsbhHubProcessChangeWorker+ec
    fffff880`03041a60 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
    Followup: MachineOwner
    
    The usbhub.sys identified as a probably cause is a Windows 7 system file and not likely the culprit. But the problem could be associated with any device using the bus, anything from a thumb drive to a integrated camera / microphone. Updating all the notebooks drivers from at least the PC manufacturer, if not the actual hardware device manufacturer might help.
    Regards
    Randy
     
    1 person likes this.

Share This Page

Loading...