BSOD On Shutdown "DRIVER_POWER_STATE_FAILURE"

Hi all, not long after installing a Creative Labs X-Fi Titanium HD I've been having long hang ups during shutdown which, after 5-15 minutes, results in the error "DRIVER_POWER_STATE_FAILURE". Can anyone tell me how to fix this?

Jarlaxle said:

Hi all, not long after installing a Creative Labs X-Fi Titanium HD I've been having long hang ups during shutdown which, after 5-15 minutes, results in the error "DRIVER_POWER_STATE_FAILURE". Can anyone tell me how to fix this?

You currently have two problems



1-sptd.sys used in daemon tools and alcohol120 remove it
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-Your audio driver ctaud2k.sys. Re-install with the newest driver avail.

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\Seven Forums\011711-50825-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*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03203000 PsLoadedModuleList = 0xfffff800`03440e50
Debug session time: Mon Jan 17 03:05:24.638 2011 (GMT-5)
System Uptime: 0 days 1:26:13.871
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800601fa20, fffff80000b9c518, fffffa80063923f0}

*** 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: fffffa800601fa20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80063923f0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80063923f0

DEVICE_OBJECT: fffffa80071a9b30

DRIVER_OBJECT: fffffa8007049960

IMAGE_NAME:  ctaud2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b67e426

MODULE_NAME: ctaud2k

FAULTING_MODULE: fffff88004400000 ctaud2k

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032e21b3 to fffff80003273600

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`032e21b3 : 00000000`0000009f 00000000`00000003 fffffa80`0601fa20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0327f6a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`0327ea26 : fffffa80`097ecc68 fffffa80`097ecc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0327f57e : 0000000c`0bde272e fffff800`00b9cc58 00000000`00050f88 fffff800`033f1388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0327ed97 : 00000003`5570dcc2 00000003`00050f88 00000003`5570dc38 00000000`00000088 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0327bdfa : fffff800`033ede80 fffff800`033fbc40 00000000`00000000 fffff880`011364c0 : 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_ctaud2k.sys

BUCKET_ID:  X64_0x9F_IMAGE_ctaud2k.sys

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

Thanks for that, installed the latest (beta) driver and now working perfectly.