 |
Windows 7: BSOD often, on my dell studio 1558, bccode fe, when i do something
|
29 Dec 2011
|
#1 | |
windows 7 Professional Service Pack 1 Italia |
BSOD often, on my dell studio 1558, bccode fe, when i do something
Hi,
i'm an italian boy, this is my first thread in sevenforums.
My Notebook often restart with a BSoD, i've posting in zip in allegate the occurence do help me.
can be the monitor?
Because, often the BSoD start when i open or close my notebook's monitor.
Help me, please.
| My System Specs |
| OS windows 7 Professional Service Pack 1
|
29 Dec 2011
|
#2 | |
Windows 7 Home Premium 64 Bit Colorado |
Code: -
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\giovix89\Windows_NT6_BSOD_jcgriff2\120511-18844-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*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`02e16000 PsLoadedModuleList = 0xfffff800`0305b670
Debug session time: Mon Dec 5 06:56:30.410 2011 (UTC - 7:00)
System Uptime: 1 days 22:36:55.530
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, fffffa8007ef2160}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
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: fffffa8007ef2160, TimeoutContext - PortData
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88005f15a60 to fffff80002e92c40
STACK_TEXT:
fffff880`035a8c18 fffff880`05f15a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`035a8c20 fffff800`031899e3 : fffffa80`07ee9050 00000000`00000001 ffffffff`dc3a58a0 fffff800`030332b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`035a8c80 fffff800`02e9d001 : fffff800`03033200 fffff800`03189901 fffffa80`04185000 fffffa80`04185040 : nt!IopProcessWorkItem+0x23
fffff880`035a8cb0 fffff800`0312dfee : 00000000`00800000 fffffa80`04185040 00000000`00000080 fffffa80`0416fb30 : nt!ExpWorkerThread+0x111
fffff880`035a8d40 fffff800`02e845e6 : fffff880`033d3180 fffffa80`04185040 fffff880`033ddfc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`035a8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05f15a60 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
---------
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\giovix89\Windows_NT6_BSOD_jcgriff2\120811-18049-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*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`02e12000 PsLoadedModuleList = 0xfffff800`03057670
Debug session time: Thu Dec 8 07:36:01.954 2011 (UTC - 7:00)
System Uptime: 0 days 2:53:49.406
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, fffffa8007305160}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Followup: MachineOwner
---------
3: 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: fffffa8007305160, TimeoutContext - PortData
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88005e82a60 to fffff80002e8ec40
STACK_TEXT:
fffff880`035a1c18 fffff880`05e82a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`035a1c20 fffff800`031859e3 : fffffa80`072fb050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0302f2b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`035a1c80 fffff800`02e99001 : fffff800`0302f200 fffff800`03185901 fffffa80`0418a100 fffffa80`0418a1a0 : nt!IopProcessWorkItem+0x23
fffff880`035a1cb0 fffff800`03129fee : 00000000`00000000 fffffa80`0418a1a0 00000000`00000080 fffffa80`0416fb30 : nt!ExpWorkerThread+0x111
fffff880`035a1d40 fffff800`02e805e6 : fffff880`033d3180 fffffa80`0418a1a0 fffff880`033ddfc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`035a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05e82a60 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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\giovix89\Windows_NT6_BSOD_jcgriff2\122611-19016-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*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`02e0f000 PsLoadedModuleList = 0xfffff800`03054670
Debug session time: Mon Dec 26 15:07:24.892 2011 (UTC - 7:00)
System Uptime: 0 days 8:04:53.344
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, fffffa8007ebc160}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Followup: MachineOwner
---------
2: 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: fffffa8007ebc160, TimeoutContext - PortData
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88005ea7a60 to fffff80002e8bc40
STACK_TEXT:
fffff880`035a1c18 fffff880`05ea7a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`035a1c20 fffff800`031829e3 : fffffa80`07ebf050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0302c2b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`035a1c80 fffff800`02e96001 : fffff800`0302c200 fffff800`03182901 fffffa80`0418a100 fffffa80`0418a1a0 : nt!IopProcessWorkItem+0x23
fffff880`035a1cb0 fffff800`03126fee : 00000000`40402000 fffffa80`0418a1a0 00000000`00000080 fffffa80`0416fb30 : nt!ExpWorkerThread+0x111
fffff880`035a1d40 fffff800`02e7d5e6 : fffff880`033d3180 fffffa80`0418a1a0 fffff880`033ddfc0 fff7f7ff`7fbfffdf : nt!PspSystemThreadStartup+0x5a
fffff880`035a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05ea7a60 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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\giovix89\Windows_NT6_BSOD_jcgriff2\122911-18548-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*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`02e11000 PsLoadedModuleList = 0xfffff800`03056670
Debug session time: Thu Dec 29 07:09:28.384 2011 (UTC - 7:00)
System Uptime: 2 days 16:01:36.835
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, fffffa80072ec160}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Followup: MachineOwner
---------
2: 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: fffffa80072ec160, TimeoutContext - PortData
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88005ef0a60 to fffff80002e8dc40
STACK_TEXT:
fffff880`035b6c18 fffff880`05ef0a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`035b6c20 fffff800`031849e3 : fffffa80`072e6050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0302e2b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`035b6c80 fffff800`02e98001 : fffff800`0302e200 fffff800`03184901 fffffa80`041a0600 fffffa80`041a0680 : nt!IopProcessWorkItem+0x23
fffff880`035b6cb0 fffff800`03128fee : ba416d00`c2f7cc05 fffffa80`041a0680 00000000`00000080 fffffa80`0418ab30 : nt!ExpWorkerThread+0x111
fffff880`035b6d40 fffff800`02e7f5e6 : fffff880`033d3180 fffffa80`041a0680 fffff880`033ddfc0 eb43adfb`7677b7fb : nt!PspSystemThreadStartup+0x5a
fffff880`035b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05ef0a60 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
---------
Your blue screens are all due to usbhub.sys. Follow the steps in USB Driver - General Fix for Problems and see if it fixes the issue.
If you continue to have problems after following the above steps, let us know, and we can explore further options. | | My System Specs | | System Manufacturer/Model Number HP Pavilion e9110t
OS Windows 7 Home Premium 64 Bit
CPU Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard Pegatron IPIEL-LA3
Memory 6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card ATI Radeon HD 4850
Sound Card Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays Acer AL2216W
Screen Resolution 1680x1050
Keyboard HP Keyboard
Mouse HP Mouse
PSU Unknown/installed by HP
Case HP generic case
Cooling Intel Stock Cooling
Hard Drives Hitachi HDP725050GLA360 ATA Device 500 GB
Internet Speed Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
|
29 Dec 2011
|
#3 | |
windows 7 Professional Service Pack 1 Italia |
Sorry before to do it.
But, if i have connected no peripherals usb, why it appared to me? | | My System Specs | | OS windows 7 Professional Service Pack 1
|
29 Dec 2011
|
#4 | |
Windows 7 Home Premium 64 Bit Colorado |
Quote: Originally Posted by giovix89  Sorry before to do it.
But, if i have connected no peripherals usb, why it appared to me? The system can have usb devices installed on it at other times and those can still exist on the system in a hidden state. That is why you must uninstall all hidden usb devices within the steps in that tutorial. | | My System Specs | | System Manufacturer/Model Number HP Pavilion e9110t
OS Windows 7 Home Premium 64 Bit
CPU Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard Pegatron IPIEL-LA3
Memory 6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card ATI Radeon HD 4850
Sound Card Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays Acer AL2216W
Screen Resolution 1680x1050
Keyboard HP Keyboard
Mouse HP Mouse
PSU Unknown/installed by HP
Case HP generic case
Cooling Intel Stock Cooling
Hard Drives Hitachi HDP725050GLA360 ATA Device 500 GB
Internet Speed Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
|
29 Dec 2011
|
#5 | |
windows 7 Professional Service Pack 1 Italia |
i've uninstall all faded device.
But i can't find the file infcache.1.
Another question, the BSod can depend of virtualbox?
And, in my computer i can see the screen, which is in file zip, but i havn't no usb composite peripherals attached.
why it appared? | | My System Specs | | OS windows 7 Professional Service Pack 1
|
29 Dec 2011
|
#6 | |
Windows 7 Home Premium 64 Bit Colorado |
Quote: Originally Posted by giovix89 i've uninstall all faded device.
But i can't find the file infcache.1.
Another question, the BSod can depend of virtualbox?
And, in my computer i can see the screen, which is in file zip, but i havn't no usb composite peripherals attached.
why it appared? Virtualbox installs virtual drivers to link with your USB hardware for the virtual machine. Try uninstalling it (after first backing up your virtual machines to an external drive) and see if the problem persists. You may install the latest version after testing, and it may fix your issue if Virtualbox is indeed the cause. | | My System Specs | | System Manufacturer/Model Number HP Pavilion e9110t
OS Windows 7 Home Premium 64 Bit
CPU Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard Pegatron IPIEL-LA3
Memory 6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card ATI Radeon HD 4850
Sound Card Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays Acer AL2216W
Screen Resolution 1680x1050
Keyboard HP Keyboard
Mouse HP Mouse
PSU Unknown/installed by HP
Case HP generic case
Cooling Intel Stock Cooling
Hard Drives Hitachi HDP725050GLA360 ATA Device 500 GB
Internet Speed Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
|
29 Dec 2011
|
#7 | |
Windows 7 Home Premium 64 Bit Colorado |
Quote: Originally Posted by giovix89 i've uninstall all faded device.
But i can't find the file infcache.1.
Another question, the BSod can depend of virtualbox?
And, in my computer i can see the screen, which is in file zip, but i havn't no usb composite peripherals attached.
why it appared? infcache.1 may not show up through search. Windows folder is not indexed in the search.
Go to C:\Windows\System32\Driverstore and see if infcache.1 is listed in that folder. Then follow the steps. | | My System Specs | | System Manufacturer/Model Number HP Pavilion e9110t
OS Windows 7 Home Premium 64 Bit
CPU Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard Pegatron IPIEL-LA3
Memory 6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card ATI Radeon HD 4850
Sound Card Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays Acer AL2216W
Screen Resolution 1680x1050
Keyboard HP Keyboard
Mouse HP Mouse
PSU Unknown/installed by HP
Case HP generic case
Cooling Intel Stock Cooling
Hard Drives Hitachi HDP725050GLA360 ATA Device 500 GB
Internet Speed Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
|
29 Dec 2011
|
#8 | |
windows 7 Professional Service Pack 1 Italia |
Thank's Mike.
I've done all.
So, now I can only hope.
But the device composite which you can see into the file zip, why it appears ? | | My System Specs | | OS windows 7 Professional Service Pack 1
|
29 Dec 2011
|
#9 | |
Windows 7 Home Premium 64 Bit Colorado |
Do you have a mouse, keyboard, or other device plugged in? A composite device is typically a USB device that has multiple facets to it. Some computers have these built in, so if you do not have something plugged in, that may be the case for you. | | My System Specs | | System Manufacturer/Model Number HP Pavilion e9110t
OS Windows 7 Home Premium 64 Bit
CPU Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard Pegatron IPIEL-LA3
Memory 6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card ATI Radeon HD 4850
Sound Card Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays Acer AL2216W
Screen Resolution 1680x1050
Keyboard HP Keyboard
Mouse HP Mouse
PSU Unknown/installed by HP
Case HP generic case
Cooling Intel Stock Cooling
Hard Drives Hitachi HDP725050GLA360 ATA Device 500 GB
Internet Speed Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
|
29 Dec 2011
|
#10 | |
windows 7 Professional Service Pack 1 Italia |
Yes i havn't device plugged in.
How i can know what device is? If is a device interconnnect with a some program? | | My System Specs | | OS windows 7 Professional Service Pack 1
BSOD often, on my dell studio 1558, bccode fe, when i do something problems? All times are GMT -5. The time now is 12:11 PM. |  |
