Security App
Avira contributes to BSOD's, recommend to replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software
Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.
Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free
Warning
DO NOT start the free trial of MalwareBytes, unselect that option when prompted.
Tip
Make full scans with both separately.
Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows. Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7
Unplug any external device from the system (USB sticks etc)
Hard Drive/Storage
Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition -
How to Upload and Post a Screenshot and File in Seven Forums
Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure
This tutorial USB Selective Suspend - Turn On or Off may help you:
To Disable Selective Suspend:
Code:
1. open the control panel
2. go to power options (you may have to set view to small icons)
3. click change plan settings
4. in the window that opens:
5. click change plan settings
6. click change advanced power settings, expand usb and ensure usb selective suspend is disabled.
Basic checks: Please run these tests and report back the results
1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
BSOD BUGCHECK SUMMARY
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800a4b6cd0, fffff80000b9c3d8, fffffa8007e67b10}
*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a4b6cd0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8007e67b10, The blocked IRP
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'CTHWIUT' and 'usbaudio.sys' overlap
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: fffffa8009c9fc10
IMAGE_NAME: asmthub3.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50322d6d
MODULE_NAME: asmthub3
FAULTING_MODULE: fffff88006bc0000 asmthub3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0
STACK_TEXT:
fffff800`00b9c388 fffff800`030ff992 : 00000000`0000009f 00000000`00000003 fffffa80`0a4b6cd0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`0309a94c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`0309a7e6 : fffffa80`069265a8 fffffa80`069265a8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0309a6ce : 00000019`174095a5 fffff800`00b9cb18 00000000`000a8a68 fffff800`0320ef88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`0309a4b7 : 00000008`13efe4c2 00000008`000a8a68 00000008`13efe4ed 00000000`00000068 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0308794a : fffff800`0320be80 fffff800`03219cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys
Followup: MachineOwner
---------
0: kd> !irp fffffa8007e67b10
Irp is active with 9 stacks 6 is current (= 0xfffffa8007e67d48)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 fffffa800a4b6cd0 00000000 fffff8800a4829f4-00000000 Success Error Cancel pending
\Driver\asmthub3 hidusb!HumPowerCompletion
Args: 00015400 00000001 00000003 00000003
[ 16, 2] 0 e0 fffffa8007e0b060 00000000 fffff8800a4982ec-fffffa8007e0b1b0 Success Error Cancel
\Driver\HidUsb HIDCLASS!HidpFdoPowerCompletion
Args: 00015400 00000001 00000003 00000003
[ 16, 2] 0 e1 fffffa8007e0b060 00000000 00000000-00000000 pending
\Driver\HidUsb
Args: 00015400 00000001 00000003 00000003
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa800c817480
Args: 00000000 00000000 00000000 00000000