Security Software:
Code:
msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 892 8 200 1380 3/22/2012 5:35 PM 3.0.8402.0 12.48 KB (12,784 bytes) 4/27/2011 5:21 PM
nissrv.exe c:\program files\microsoft security client\antimalware\nissrv.exe 2432 8 200 1380 3/22/2012 5:37 PM 3.0.8402.0 281.52 KB (288,272 bytes) 4/27/2011 5:21 PM
msseces.exe c:\program files\microsoft security client\msseces.exe 1108 8 200 1380 3/22/2012 5:36 PM 2.1.1116.0 1.37 MB (1,436,736 bytes) 6/15/2011 2:35 PM
Possible out of date drivers:
Code:
LVUSBS64 fffff880`07b71000 fffff880`07b7d980 Sat Feb 03 11:05:16 2007 (45c4cedc) 0001bba8 LVUSBS64.sys
TVALZFL fffff880`05ff4000 fffff880`05ffb000 Fri Jun 19 04:05:44 2009 (4a3b62f8) 00010921 TVALZFL.sys
pgeffect fffff880`07bac000 fffff880`07bb2e80 Mon Jun 22 03:00:11 2009 (4a3f481b) 00017d48 pgeffect.sys
thpdrv fffff880`01b29000 fffff880`01b35000 Sun Jun 28 20:02:56 2009 (4a4820d0) 000138cc thpdrv.sys
Thpevm fffff880`01b27000 fffff880`01b28f80 Mon Jun 29 02:15:37 2009 (4a487829) 000124b8 Thpevm.SYS
The driver in red is a likely culprit to your crashes.
LVUSBS64.sys
TVALZFL.sys
pgeffect.sys
thpdrv.sys
Thpevm.SYS
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Christcpd\Windows_NT6_BSOD_jcgriff2\032212-22448-01.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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03262650
Debug session time: Thu Mar 22 17:34:36.680 2012 (UTC - 6:00)
System Uptime: 0 days 1:21:25.804
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, fffffa8008c02160}
*************************************************************************
*** ***
*** ***
*** 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: fffffa8008c02160, 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 fffff880046a8a60 to fffff8000309ad40
STACK_TEXT:
fffff880`033c4c18 fffff880`046a8a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033c4c20 fffff800`03390723 : fffffa80`08bf7050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0323a2b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033c4c80 fffff800`030a4471 : fffff800`0323a200 fffff800`03390701 fffffa80`03b7eb00 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`033c4cb0 fffff800`03334f7a : 48380033`a3040000 fffffa80`03b7eb60 00000000`00000080 fffffa80`03b679e0 : nt!ExpWorkerThread+0x111
fffff880`033c4d40 fffff800`0308b9c6 : fffff880`031d3180 fffffa80`03b7eb60 fffff880`031ddfc0 064700b0`48841c44 : nt!PspSystemThreadStartup+0x5a
fffff880`033c4d80 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`033c4970 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`046a8a60 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
---------
A USB device is causing the crash, but Microsoft symbols do not contain the information about the device. What USB devices do you have plugged in?
For USB problems:
You may want to replace your webcam if it does not have any driver updates. It does not seem to be compatible with Windows 7.
Quote