Blue Screen after long shutdown

Hello I'm new to these forums and BSODs so bare with me, I think I attached the mini-dumps which you could analyze for me? I'm sure I have outdated drivers as I just built this computer. It hangs on shutdown for about 10-15 minutes then BSOD saying DRIVER-POWER-STATE-FAILURE. It didn't do this until recently. Thanks!

BSOdoubleD said:

Hello I'm new to these forums and BSODs so bare with me, I think I attached the mini-dumps which you could analyze for me? I'm sure I have outdated drivers as I just built this computer. It hangs on shutdown for about 10-15 minutes then BSOD saying DRIVER-POWER-STATE-FAILURE. It didn't do this until recently. Thanks!

Hi and welcome

All four dmps ponted to the same file. your creative sound driver (ctaud2k.sys)

I would update that driver and your raid driver. I f you are overclocking stop)

Hope this helps

Ken J+

Code:

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


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

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Tue Dec  8 16:58:57.011 2009 (GMT-5)
System Uptime: 5 days 4:40:01.597
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80074dca20, fffff80000b9c518, fffffa800c106b10}

*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : ctaud2k.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80074dca20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800c106b10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800c106b10

DEVICE_OBJECT: fffffa8009564060

DRIVER_OBJECT: fffffa8009432bb0

IMAGE_NAME:  ctaud2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a66eda7

MODULE_NAME: ctaud2k

FAULTING_MODULE: fffff8800612e000 ctaud2k

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ee7e23 to fffff80002e78f00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02ee7e23 : 00000000`0000009f 00000000`00000003 fffffa80`074dca20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02e84fa6 : fffff800`00b9c630 fffff800`00b9c630 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02e84326 : fffff800`03027700 00000000`01b64866 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02e84e7e : 00000414`f2991872 fffff800`00b9cc58 00000000`01b64866 fffff800`02ff4f48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02e84697 : 0000010e`c646c7c3 0000010e`01b64866 0000010e`c646c701 00000000`00000066 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e816fa : fffff800`02ff1e80 fffff800`02fffc40 00000000`00000000 fffff880`01483c50 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_

BUCKET_ID:  X64_0x9F_IMAGE_ctaud2k.sys

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