Hello everyone. I had just set my laptop to go to sleep (closed lid), and when I came back about 10 minutes later, it was turned off. When I turned it back on a BSOD error report had shown up.
I have attached the file that the BSOD guide said, but when entering "Perfmon / report", it said "The parameter is incorrect".
I have also uploaded a .txt file with the info that Event Viewer gave me.
Is Windows 7 . . .
- x64
- Original OS
- OEM
- OS is about two weeks old
Hello Niskala
& Welcome to SevenForums!
Let's get to it.
BSOD Summary
Ignore the error message I got in the analyse, I have problems with my debugger nowadays.Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.164\080911-28033-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.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e96650 Debug session time: Tue Aug 9 20:08:08.901 2011 (UTC + 2:00) System Uptime: 1 days 15:58:38.478 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list ........................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 6, fffffa8008347000} Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for usbfilter.sys *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys ************************************************************************* *** *** *** *** *** 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 : usbfilter.sys ( usbfilter+518c ) 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: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit Arg4: fffffa8008347000, 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 fffff880070487fa to fffff80002cd0d00 STACK_TEXT: fffff880`0fdf6718 fffff880`070487fa : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx fffff880`0fdf6720 fffff880`070535c1 : fffffa80`08347000 fffffa80`083471d8 fffffa80`08347000 fffffa80`07f52050 : usbhub!UsbhWaitEventWithTimeoutEx+0x3aa fffff880`0fdf67d0 fffff880`07052bdc : 00000000`00000000 fffffa80`50447100 fffffa80`08347000 00000000`00080000 : usbhub!Usbh_PCE_Disable_Action+0x4f1 fffff880`0fdf6830 fffff880`07057ff0 : fffffa80`07f52050 00000000`00000001 00000000`00000001 fffffa80`07f52708 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0x110 fffff880`0fdf6870 fffff880`07050744 : fffffa80`07f52050 fffffa80`08347000 fffffa80`08347000 00000000`00000000 : usbhub!UsbhPCE_Disable+0xb4 fffff880`0fdf68c0 fffff880`0704fa3c : 00000000`00000007 00000000`00000003 fffffa80`07f52050 fffffa80`07f52708 : usbhub!UsbhBusPause_Action+0x184 fffff880`0fdf6910 fffff880`0704feb6 : fffffa80`07f521a0 00000000`00000007 fffffa80`07f52050 00000000`00000000 : usbhub!Usbh_BS_BusRun+0x94 fffff880`0fdf6950 fffff880`0705092b : 00000000`00000003 fffffa80`07f52708 fffffa80`07f52050 00000000`00000000 : usbhub!UsbhDispatch_BusEvent+0x20e fffff880`0fdf69a0 fffff880`0706543e : fffffa80`086ae720 fffffa80`05451d10 fffffa80`05451d10 fffffa80`086ae720 : usbhub!UsbhSyncBusPause+0x4f fffff880`0fdf69e0 fffff880`07063b4e : fffffa80`07f52050 fffffa80`07f52708 fffffa80`07f52708 00000000`00000003 : usbhub!UsbhFdoSetPowerDx_Action+0x9a fffff880`0fdf6a40 fffff880`0706277f : fffffa80`086ae720 fffffa80`07f521a0 fffffa80`07f52050 fffffa80`086ae4a0 : usbhub!UsbhFdoDevicePowerState+0x206 fffff880`0fdf6a90 fffff880`07061a3b : fffffa80`086ae4a0 00000000`00000000 fffffa80`07f52050 fffff800`02dcba22 : usbhub!UsbhFdoPower_SetPower+0x93 fffff880`0fdf6ad0 fffff880`07048fdf : fffffa80`086ae4a0 fffffa80`07f55b80 fffffa80`04fabc90 fffff800`02e43e00 : usbhub!UsbhFdoPower+0xaf fffff880`0fdf6b10 fffff800`02dcbae2 : fffffa80`086ae4a0 00000000`00000000 fffffa80`07f55b80 fffffa80`086ae4a0 : usbhub!UsbhGenDispatch+0x7f fffff880`0fdf6b40 fffff880`085ec18c : fffffa80`07f55b80 fffff880`085e85cb fffffa80`086ae4a0 fffff800`02dbbf43 : nt!IopPoHandleIrp+0x32 fffff880`0fdf6b70 fffffa80`07f55b80 : fffff880`085e85cb fffffa80`086ae4a0 fffff800`02dbbf43 fffffa80`07f55cd0 : usbfilter+0x518c fffff880`0fdf6b78 fffff880`085e85cb : fffffa80`086ae4a0 fffff800`02dbbf43 fffffa80`07f55cd0 fffffa80`086ae720 : 0xfffffa80`07f55b80 fffff880`0fdf6b80 fffffa80`086ae4a0 : fffff800`02dbbf43 fffffa80`07f55cd0 fffffa80`086ae720 fffffa80`07f55cd0 : usbfilter+0x15cb fffff880`0fdf6b88 fffff800`02dbbf43 : fffffa80`07f55cd0 fffffa80`086ae720 fffffa80`07f55cd0 fffffa80`0791d020 : 0xfffffa80`086ae4a0 fffff880`0fdf6b90 fffff800`02dbc9be : fffffa80`07f55cd0 fffffa80`086ae720 fffff880`00000000 fffffa80`05357010 : nt!PopDiagTraceDeviceAcquireIrp+0xf3 fffff880`0fdf6c60 fffff800`02de3fb5 : fffffa80`07f55b80 fffffa80`086ae4a0 00000000`00000001 fffffa80`086ae548 : nt!PoDeviceAcquireIrp+0x3e fffff880`0fdf6c90 fffff800`02f6d32e : ffffffff`fa0a1f00 fffffa80`053fbb60 00000000`00000080 fffff800`02cc8817 : nt!PopIrpWorker+0x3c5 fffff880`0fdf6d40 fffff800`02cc2666 : fffff880`009e9180 fffffa80`053fbb60 fffff880`009f3fc0 fffff880`0140fcb0 : nt!PspSystemThreadStartup+0x5a fffff880`0fdf6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbfilter+518c fffff880`085ec18c ?? ??? SYMBOL_STACK_INDEX: f SYMBOL_NAME: usbfilter+518c FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbfilter IMAGE_NAME: usbfilter.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d0899c9 FAILURE_BUCKET_ID: X64_0xFE_usbfilter+518c BUCKET_ID: X64_0xFE_usbfilter+518c Followup: MachineOwner ---------
As you see, usbfilter.sys is the cause here. This would be your AMD USB Filter Driver, which is likely a part of your chipset drivers. Do you have any chance to uninstall/reinstall it?
Best Regards,
FredeGail
I don't see usbfilter.sys or AMD USB Filter Driver in Unistall a Program.
What should I be looking for?
Try just updating your chipset. Link below.
AMD.com | Support & Downloads
Select which motherboard model you have and so on whatever you have to fill
This should fix your trouble.
Best Regards,
FredeGail
I clicked the "Automatically Detect and Install" one, and upon running, it said " AMD Driver Installer- We were unable to find your product or OS."
Try searching your model manually. If you wonder what your model of your motherboard is, download Speccy, a great tool!
More information given here.
Speccy - System Information - Free Download
Best Regards,
FredeGail
AMD RAID/SATA Drivers
I found my way to this page. How do I know which of the 3 to click on?
Thank you.
From the link you posted previously, download the two (south/north bridge) drivers. Both of them. It shouldn't hurt.
Best Regards,
FredeGail
Quote