driver_power_state_failure - 0x0000009F - ATI Catalyst v9.7
- I receive the following error and bsod upon shutting down, driver_power_state_failure 0x0000009F. This is a fresh install of Windows 7 RTM x64 and I have narrowed it down to the installation of ATI Catalyst v9.7 drivers. What would be the cause of this error?
Motherboard
Cards not getting enough power
Bad card(s)
Bad driver
Asus P6T Deluxe v2
2X - MSI Radeon 4890 (CrossfireX)
Corsair HX1000W power supply
Intel i7 920
Only drivers installed are -
Intel Matrix Storage Manager
Intel Chipset Software Installation Utility
Intel GT Pro 1000 (nic driver)
Samsung T240 (monitor driver)
Auzentech Forte v1.1
[edit] Corrected typos [/edit]- Edited byΩIII Thursday, August 13, 2009 5:48 PM
All Replies
- I can't seem to find any information on your P5T Deluxe v2 motherboard. Where did you purchase it? The closest I could find was a P6T Deluxe v2. Do you know if they are similar?
If your motherboard has onboard audio and onboard NIC, I would remove the drivers for each of them one at a time to see if that makes a difference. There could be a conflict with one of them. Do this by removing the driver and then shutting down the computer and removing the plug-in card. - Don't you think that your PSU is a bit low (if the info is right) for a Crossfire 2x video solution?
Mobile AMD64 3000+, VIA Apollo K8T800 chipset, 1 G RAM, ATIRadeonMobility 9700, 20x DVDRW, C:XPSP3 (55G),D:WIN7 (25G),F:DATA (250G) - Sorry guys, those were typos. Post edited to correct. Mobo is infact a P6T Deluxe v2 and the power supply is in fact 1000W not 100W
- I would still recommend removing the plug-in cards to see if it makes a difference. You may very well have hardware and/or software conflicts.
@Rick Dee - removed tested and re installed, bsod's only when cards installed.
Copied from windbg
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: fffffa8006298060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800a0264c0, The blocked IRPDebugging Details:
------------------*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800a0264c0
DEVICE_OBJECT: fffffa80075ad060
DRIVER_OBJECT: fffffa80075a8470
IMAGE_NAME: ctaud2k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a66eda7
MODULE_NAME: ctaud2k
FAULTING_MODULE: fffff880042f0000 ctaud2k
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002d45e23 to fffff80002cd6f00
STACK_TEXT:
fffff800`00b9c4c8 fffff800`02d45e23 : 00000000`0000009f 00000000`00000003 fffffa80`06298060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ce2fa6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02ce2326 : fffffa80`09be5c68 fffffa80`09be5c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ce2e7e : 00000006`05fc6707 fffff800`00b9cc58 00000000`000287c9 fffff800`02e53ba8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ce2697 : 00000001`9284b9c3 00000001`000287c9 00000001`9284b994 00000000`000000c9 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cdf6fa : fffff800`02e4fe80 fffff800`02e5dc40 00000000`00000000 fffff880`04833db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kbFOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_ctaud2k.sys
BUCKET_ID: X64_0x9F_IMAGE_ctaud2k.sys
Followup: MachineOwner
---------0: kd> !devobj fffffa80075ad060 f
Device object (fffffa80075ad060) is for:
00000065 \Driver\ctaud2k DriverObject fffffa80075a8470
Current Irp 00000000 RefCount 0 Type 0000002f Flags 00002850
Dacl fffff9a10057c491 DevExt fffffa80075ad1b0 DevObjExt fffffa80075ad4b8
ExtensionFlags (0000000000)
AttachedDevice (Upper) fffffa80075abda0 \Driver\ksthunk
AttachedTo (Lower) fffffa8006298060 \Driver\pci
Device queue is not busy.
0: kd> !drvobj fffffa80075a8470 f
Driver object (fffffa80075a8470) is for:
\Driver\ctaud2k
Driver Extension List: (id , addr)Device Object list:
fffffa80075ad060DriverEntry: fffff88004390f08 ctaud2k
DriverStartIo: 00000000
DriverUnload: fffff880043657fc ctaud2k
AddDevice: fffff8800436597c ctaud2kDispatch routines:
[00] IRP_MJ_CREATE fffff880043676d0 ctaud2k+0x776d0
[01] IRP_MJ_CREATE_NAMED_PIPE fffff80002cbd65c nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE fffff880043676d0 ctaud2k+0x776d0
[03] IRP_MJ_READ fffff88000c30508 ks!DispatchRead
[04] IRP_MJ_WRITE fffff88000c305a4 ks!DispatchWrite
[05] IRP_MJ_QUERY_INFORMATION fffff80002cbd65c nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION fffff80002cbd65c nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA fffff80002cbd65c nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA fffff80002cbd65c nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS fffff88000c30640 ks!DispatchFlush
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff80002cbd65c nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION fffff80002cbd65c nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL fffff80002cbd65c nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff80002cbd65c nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL fffff88004367710 ctaud2k+0x77710
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff88004367710 ctaud2k+0x77710
[10] IRP_MJ_SHUTDOWN fffff88004366204 ctaud2k+0x76204
[11] IRP_MJ_LOCK_CONTROL fffff80002cbd65c nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP fffff80002cbd65c nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT fffff80002cbd65c nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY fffff88000c30850 ks!DispatchQuerySecurity
[15] IRP_MJ_SET_SECURITY fffff88000c308ac ks!DispatchSetSecurity
[16] IRP_MJ_POWER fffff880043675dc ctaud2k+0x775dc
[17] IRP_MJ_SYSTEM_CONTROL fffff8800439b300 portcls!PcWmiSystemControl
[18] IRP_MJ_DEVICE_CHANGE fffff80002cbd65c nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA fffff80002cbd65c nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA fffff80002cbd65c nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP fffff880043675b4 ctaud2k+0x775b4
If I am reading this correctly then ctaud2k.sys is the offender (which is part of my sound card drivers - Auzentech Forte). I'd have to guess that there is a driver conflict with the Catalsyt drivers as my system only bsod's when the catalyst driver is installed. I have since reformatted and reinstalled, and have been able to reproduce.
Are my assumptions correct?If I am reading this correctly then ctaud2k.sys is the offender (which is part of my sound card drivers - Auzentech Forte). I'd have to guess that there is a driver conflict with the Catalsyt drivers as my system only bsod's when the catalyst driver is installed. I have since reformatted and reinstalled, and have been able to reproduce.
Are my assumptions correct?
You're correct that the audio driver looks like the offender.
I wouldn't suspect it to be an issue with the video drivers, because I don't think there's any sort of shared components between the audio and video drivers.
When you don't have the catalyst drivers installed, what drivers are loaded on the video card?
You should send the details above to Auzentech tech support. They might want a memory dump from your machine to be able to debug this issue.- Perhpas it is strange coincidence that the bsod would occur after the Catalyst drivers were installed.
I assumed the Catalyst drivers were to blame as I only installed 1 driver then reboot, 1 driver then reboot, etc.
The first bsod occured after I installed the Catalyst drivers and attempted to reboot.
The installation sequnce was as followed;
Intel Matrix Storage Manager
Intel Chipset Software Installation Utility
Auzentech Forte v1.1
ATI Catalyst v9.7
As far as my previous video card drivers are concerned, as this was a fresh install it would of been the default drivers packaged with Windows 7.
This problem has been reproduced. I have formated and installed 3 times now. I have sent detailes to Auzentech and opened a support ticket. Intel Matrix Storage Manager
Intel Chipset Software Installation Utility
Auzentech Forte v1.1
ATI Catalyst v9.7
As far as my previous video card drivers are concerned, as this was a fresh install it would of been the default drivers packaged with Windows 7.
This problem has been reproduced. I have formated and installed 3 times now. I have sent detailes to Auzentech and opened a support ticket.
Did you ever get a resolution on this issue? Even here months later it seems this issue is still present and affecting us Forte users. After reinstalling and poking around their site and finding no answers, I'm still getting similiar crash dumps:
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: fffffa800b2b4060, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800aa846d0, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800aa846d0 DEVICE_OBJECT: fffffa800bf05b30 DRIVER_OBJECT: fffffa800c08c7b0 IMAGE_NAME: ctaud2k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a66eda7 MODULE_NAME: ctaud2k FAULTING_MODULE: fffff88004246000 ctaud2k DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002d3fe23 to fffff80002cd0f00
STACK_TEXT: fffff800`00b9c4c8 fffff800`02d3fe23 : 00000000`0000009f 00000000`00000003 fffffa80`0b2b4060 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02cdcfa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000004 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`00b9c570 fffff800`02cdc326 : fffff880`03558ad0 fffff880`03558ad0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02cdce7e : 00000005`db4d94b9 fffff800`00b9cc58 00000000`000275db fffff800`02e4dde8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02cdc697 : 00000001`d4dc8cc5 00000001`000275db 00000001`d4dc8ca5 00000000`000000db : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02cd96fa : fffff800`02e49e80 fffff800`02e57c40 00000000`00000000 fffff880`011814c0 : 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
