Random BSOD

[arcticking]

Windows 7 32Bit - Build 7601 Version 6.1.
Graphics card newly bought less than 3 months ago.
SATA cable connecting HDD to motherboard is somewhat broken, but reads and writes fine.
System Specifications in my Profile.

Hi guys, I'm quite new here and am trying to solve my problem with the random BSOD's at times. Can someone here please figure it out for me?

I've attached the BSOD.zip file:

 

[zigzag3143]

Windows 7 32Bit - Build 7601 Version 6.1.
Graphics card newly bought less than 3 months ago.
SATA cable connecting HDD to motherboard is somewhat broken, but reads and writes fine.
System Specifications in my Profile.

Hi guys, I'm quite new here and am trying to solve my problem with the random BSOD's at times. Can someone here please figure it out for me?

I've attached the BSOD.zip file:

Related to your USB audio drive re-install it with newest

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060611-19796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`83537ad4?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8340f000 PsLoadedModuleList = 0x83559850
Debug session time: Mon Jun  6 11:39:58.375 2011 (GMT-4)
System Uptime: 13 days 23:30:42.482
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.................................
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 88a92c68, Physical Device Object of the stack
Arg3: 83537ae0, Functional Device Object of the stack
Arg4: 8661a2a8, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  8661a2a8

DEVICE_OBJECT: 88a97ad8

DRIVER_OBJECT: 88a8cf38

IMAGE_NAME:  usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79c0f

MODULE_NAME: usbaudio

FAULTING_MODULE: 9f9c8000 usbaudio

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 834d5f35 to 834edf20

STACK_TEXT:  
83537a94 834d5f35 0000009f 00000003 88a92c68 nt!KeBugCheckEx+0x1e
83537b00 834d5fae 83537ba0 00000000 83544380 nt!PopCheckIrpWatchdog+0x1f5
83537b38 83489039 83552a60 00000000 fdb2d495 nt!PopCheckForIdleness+0x73
83537b7c 83488fdd 8353ad20 83537ca8 00000001 nt!KiProcessTimerDpcTable+0x50
83537c68 83488e9a 8353ad20 83537ca8 00000000 nt!KiProcessExpiredTimerList+0x101
83537cdc 8348700e 049d6a97 864a9ad0 83544380 nt!KiTimerExpiration+0x25c
83537d20 83486e38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
83537d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_usbaudio.sys

BUCKET_ID:  0x9F_IMAGE_usbaudio.sys

Followup: MachineOwner
---------

 

[arcticking]

Thanks, how do I re-install this? I mean like, where can I find it under? Device Manager? Every time my computer goes into sleep mode it goes BSOD.