New
#11
Thank you for your response.
I am beginning to think that my internet modem's ZTE AX326 provider's custom written driver is the problem.
Cause at the moment i were using only bluetooth mouse (bluetooth is integrated) and that internet modem.
Any chance i could help them? Like sending that dumpfile? Or i should run driver verifier on that device?
Thanks again.
The crash files are still pointing to your USB devices. Do you have a USB wireless device, by chance? I do notice a bluetooth USB device...Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\BSODDmpFiles\Simbab\dump.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03009000 PsLoadedModuleList = 0xfffff800`0324e670 Debug session time: Thu Feb 16 03:36:41.942 2012 (GMT-7) System Uptime: 0 days 0:49:15.487 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa800730ec80} Probably caused by : usbhub.sys ( 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: fffffa800730ec80, TimeoutContext - PortData Debugging Details: ------------------ DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff88004a12a60 to fffff80003085c40 STACK_TEXT: fffff880`033afc18 fffff880`04a12a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033afc20 fffff800`0337c9e3 : fffffa80`07308050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032262b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033afc80 fffff800`03090001 : fffff800`03226200 fffff800`0337c901 fffffa80`03b68600 fffffa80`03b68680 : nt!IopProcessWorkItem+0x23 fffff880`033afcb0 fffff800`03320fee : 00000000`00000019 fffffa80`03b68680 00000000`00000080 fffffa80`03b4e9e0 : nt!ExpWorkerThread+0x111 fffff880`033afd40 fffff800`030775e6 : fffff880`031d3180 fffffa80`03b68680 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`04a12a60 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 ---------
Please follow the https://www.sevenforums.com/crashes-d...tructions.html and upload the files to your next post (not to a third party site). There is information included in the files generated through those instructions that will help us provide more informed troubleshooting steps.