Code:
mbamservice.exe c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe 2980 8 200 1380 2/18/2012 5:59 PM Not Available Not Available Not Available
pchooklaunch32.exe c:\program files\bitdefender\bitdefender 2011\antispam32\pchooklaunch32.exe 1464 8 200 1380 2/18/2012 5:56 PM 14.0.28.85 62.55 KB (64,048 bytes) 4/1/2011 5:17 PM
bdagent.exe c:\program files\bitdefender\bitdefender 2011\bdagent.exe 1804 8 200 1380 2/18/2012 5:56 PM 14.0.28.65 1.93 MB (2,026,680 bytes) 6/1/2011 3:38 PM
pchooklaunch64.exe c:\program files\bitdefender\bitdefender 2011\pchooklaunch64.exe 1792 8 200 1380 2/18/2012 5:56 PM 14.0.28.85 74.59 KB (76,384 bytes) 4/1/2011 5:17 PM
seccenter.exe c:\program files\bitdefender\bitdefender 2011\seccenter.exe 1004 8 200 1380 2/18/2012 6:11 PM 14.0.28.52 787.74 KB (806,648 bytes) 4/1/2011 5:17 PM
updatesrv.exe c:\program files\bitdefender\bitdefender 2011\updatesrv.exe 2836 8 200 1380 2/18/2012 5:56 PM 14.0.28.25 51.98 KB (53,224 bytes) 6/1/2011 3:38 PM
vsserv.exe c:\program files\bitdefender\bitdefender 2011\vsserv.exe 976 8 200 1380 2/18/2012 5:56 PM 14.0.28.55 2.54 MB (2,660,624 bytes) 5/19/2011 4:56 PM
I note that malwarebytes and bitdefender are both running. Are these both full versions, or are you using the standalone scanner for malwarebytes? Having two full security systems that accomplish the same task can cause conflicts on a system.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Kingston\BSODDmpFiles\Diabolicalz\Windows_NT6_BSOD_jcgriff2\020912-22136-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Thu Feb 9 00:32:04.703 2012 (GMT-7)
System Uptime: 0 days 5:50:06.482
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, fffffa80062c6b20}
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: fffffa80062c6b20, 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 fffff88005353a60 to fffff80002cdac40
STACK_TEXT:
fffff880`031eec18 fffff880`05353a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`031eec20 fffff800`02fd19e3 : fffffa80`0560d050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02e7b2b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`031eec80 fffff800`02ce5001 : fffff800`02e7b200 fffff800`02fd1901 fffffa80`03ce5b00 fffffa80`03ce5b60 : nt!IopProcessWorkItem+0x23
fffff880`031eecb0 fffff800`02f75fee : ffff7fff`2edffdfd fffffa80`03ce5b60 00000000`00000080 fffffa80`03c709e0 : nt!ExpWorkerThread+0x111
fffff880`031eed40 fffff800`02ccc5e6 : fffff880`009e8180 fffffa80`03ce5b60 fffff880`009f2f40 f7ffbfff`ffbffdf7 : nt!PspSystemThreadStartup+0x5a
fffff880`031eed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05353a60 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
--------- - Likely caused by a USB device conflicting with your system. Either it has an outdated/corrupted driver, it is conflicting with a device that is no longer used in the system, or the device itself is not functioning properly.
Start with the steps in
USB Driver - General Fix for Problems and see if it resolves the problem.
If the general fix does not resolve it, it may be that the ports themselves are stuck in a bad power state and need to be reset. To reset the ports, follow these steps:
- Shut down and turn off your computer.
- Remove the AC Adapter then the battery from the laptop.
- Hold down the power button for 30 seconds to close the circuit and drain all residual power from components. This resets software/hardware connections with the BIOS and also fixes hardware that has entered a bad power state to protect itself from a power surge (especially USB devices).
- Replace the battery and then the AC adapter.
- Turn on the computer and see if devices now function properly.
If you still have problems after the above, begin narrowing down any usb devices that may have faulty hardware.
I also have an older Toshiba that is part of the Satellite series, and its idle temperatures are 60-65 C, and it maxes at around 75 C. This seems to be normal behavior for these systems to run hot.