[BSOD] - Driver Power Failuer & IRQ Less or Not Equal

[diznanl]

Windows 7 . . .
- x64
- the original installed OS on the system? YES
- Retail
- 1.5 - 2 year old system
- Original OS install (have not had to re-install Windows 7)

I'm about to swap the motherboard out for an M5A99X Evo but want to make sure it's the MB that's bad, first... I'm sure I'm having some driver issues, at least with my Alesis I|O26 FireWire. Lots of BSOD dumps in that zip file attached!

All help is appreciated!

Thanks,
Dan

 

[writhziden]

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [H:\BSODDmpFiles\diznanl\Windows_NT6_BSOD_jcgriff2\123111-53929-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0341a000 PsLoadedModuleList = 0xfffff800`0365f670
Debug session time: Sat Dec 31 13:08:10.316 2011 (UTC - 7:00)
System Uptime: 2 days 2:22:18.078
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
...............................
Unable to load image ha20x2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ha20x2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha20x2k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880076ed51b, fffff880061f3718, fffff880061f2f70}

Probably caused by : ha20x2k.sys ( ha20x2k+8551b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880076ed51b, The address that the exception occurred at
Arg3: fffff880061f3718, Exception Record Address
Arg4: fffff880061f2f70, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
ha20x2k+8551b
fffff880`076ed51b 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  fffff880061f3718 -- (.exr 0xfffff880061f3718)
ExceptionAddress: fffff880076ed51b (ha20x2k+0x000000000008551b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000c50
Attempt to read from address 0000000000000c50

CONTEXT:  fffff880061f2f70 -- (.cxr 0xfffff880061f2f70)
rax=00000000000000ec rbx=fffffa80084ec7d0 rcx=0000000000000c50
rdx=0000000000000014 rsi=fffffa80084ec7d0 rdi=00000000000006cf
rip=fffff880076ed51b rsp=fffff880061f3950 rbp=0000000000000008
 r8=00000000000000ec  r9=fffff880046b91e0 r10=fffff88004a463a0
r11=0000000000000008 r12=000000000000000f r13=000000000000000f
r14=0000000000000000 r15=0000000000000025
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
ha20x2k+0x8551b:
fffff880`076ed51b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000c50=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000c50

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c9100
 0000000000000c50 

FOLLOWUP_IP: 
ha20x2k+8551b
fffff880`076ed51b 488b01          mov     rax,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000010 to fffff880076ed51b

STACK_TEXT:  
fffff880`061f3950 00000000`00000010 : 00000000`00000207 fffff880`061f3978 00000000`00000018 fffff880`061f3a20 : ha20x2k+0x8551b
fffff880`061f3958 00000000`00000207 : fffff880`061f3978 00000000`00000018 fffff880`061f3a20 fffff880`076ed877 : 0x10
fffff880`061f3960 fffff880`061f3978 : 00000000`00000018 fffff880`061f3a20 fffff880`076ed877 00000000`00000008 : 0x207
fffff880`061f3968 00000000`00000018 : fffff880`061f3a20 fffff880`076ed877 00000000`00000008 00000000`00000213 : 0xfffff880`061f3978
fffff880`061f3970 fffff880`061f3a20 : fffff880`076ed877 00000000`00000008 00000000`00000213 fffff880`061f39a8 : 0x18
fffff880`061f3978 fffff880`076ed877 : 00000000`00000008 00000000`00000213 fffff880`061f39a8 00000000`00000018 : 0xfffff880`061f3a20
fffff880`061f3980 00000000`00000008 : 00000000`00000213 fffff880`061f39a8 00000000`00000018 00000000`00000008 : ha20x2k+0x85877
fffff880`061f3988 00000000`00000213 : fffff880`061f39a8 00000000`00000018 00000000`00000008 fffff880`076ed9b3 : 0x8
fffff880`061f3990 fffff880`061f39a8 : 00000000`00000018 00000000`00000008 fffff880`076ed9b3 fffff880`061f3a20 : 0x213
fffff880`061f3998 00000000`00000018 : 00000000`00000008 fffff880`076ed9b3 fffff880`061f3a20 00000000`00000000 : 0xfffff880`061f39a8
fffff880`061f39a0 00000000`00000008 : fffff880`076ed9b3 fffff880`061f3a20 00000000`00000000 00000000`000000aa : 0x18
fffff880`061f39a8 fffff880`076ed9b3 : fffff880`061f3a20 00000000`00000000 00000000`000000aa 00000001`00000000 : 0x8
fffff880`061f39b0 fffff880`061f3a20 : 00000000`00000000 00000000`000000aa 00000001`00000000 00000000`00000002 : ha20x2k+0x859b3
fffff880`061f39b8 00000000`00000000 : 00000000`000000aa 00000001`00000000 00000000`00000002 00000000`80004005 : 0xfffff880`061f3a20


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ha20x2k+8551b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ha20x2k

IMAGE_NAME:  ha20x2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be16b9e

STACK_COMMAND:  .cxr 0xfffff880061f2f70 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_ha20x2k+8551b

BUCKET_ID:  X64_0x7E_ha20x2k+8551b

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

[*]
Loading Dump File [H:\BSODDmpFiles\diznanl\Windows_NT6_BSOD_jcgriff2\122211-29406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03464000 PsLoadedModuleList = 0xfffff800`036a9670
Debug session time: Thu Dec 22 19:40:44.458 2011 (UTC - 7:00)
System Uptime: 0 days 1:05:42.238
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, fffffa8006a2d040, fffff80000b9c510}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006a2d040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006a2d040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000356cca6 to fffff800034e0c40

STACK_TEXT:  
fffff800`00b9c4d8 fffff800`0356cca6 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`06a2d040 : nt!KeBugCheckEx
fffff800`00b9c4e0 fffff800`0371e2fc : 00000000`00000000 fffff800`00000000 00000000`00000000 fffff800`034e95fa : nt!PnpBugcheckPowerTimeout+0x76
fffff800`00b9c540 fffff800`034ec5fc : fffffa80`07a864a0 fffffa80`00000000 00000000`40220a88 00000000`01ccc11c : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff800`00b9c570 fffff800`034ec496 : fffff880`0409d710 00000000`0003db21 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034ec37e : 00000009`2dc1c941 fffff800`00b9cc58 00000000`0003db21 fffff800`036596a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034ec167 : 00000002`829bb9c2 00000002`0003db21 00000002`829bb92a 00000000`00000021 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034d896a : fffff800`03656e80 fffff800`03664cc0 00000000`00000001 fffffa80`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .thread 0xfffffa8006a2d040 ; kb

FOLLOWUP_IP: 
nt!PnpBugcheckPowerTimeout+76
fffff800`0356cca6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PnpBugcheckPowerTimeout+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

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


[/list]

Most of your problems are likely due to

ASACPI	fffff880`05580000	fffff880`05588000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Thanks to JMH and zigzag3143 for the above information.

Your sound card drivers are also old. Suggest updating them from the Creative site since Creative is the manufacturer.

 

[diznanl]

Hey writhziden,

Thanks for the response. I'm using the PAX MASTER PCI XFI ALL OS Driver Suite V1.30 ... reportedly more stable / sounding better than the default creative drivers. The author integrates the best parts from numerous creative driver releases.

PAX MASTER PCI XFI ALL OS Driver Suite V1.30 Release

Do you have a take on this, or still think I should upgrade?

 

[writhziden]

You can try leaving your sound card drivers as is and see if ASACPI.SYS is the cause of the Creative related crash in the first crash I posted, crash 1.

 

[diznanl]

New BSOD - Driver Power State Failure

I updated the ASUS file above ... I moved from a 2005 to 2009 version driver! Thanks for this!

I got a new BSOD today: Driver Power State Failure. Please have a look at the most recent BSOD from 1/29/2012 and confirm that it is the creative drivers. I can update these today, but wanted to double check again that it was creative and not another issue.

Thanks,
Dan

 

[writhziden]

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


Loading Dump File [K:\BSODDmpFiles\diznanl\Windows_NT6_BSOD_jcgriff2\012912-38657-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0345d000 PsLoadedModuleList = 0xfffff800`036a2670
Debug session time: Sun Jan 29 13:22:27.844 2012 (GMT-7)
System Uptime: 2 days 16:39:19.937
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
..........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, fffffa8006a4eb60, fffff80000b9c510}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006a4eb60, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006a4eb60

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003565ca6 to fffff800034d9c40

STACK_TEXT:  
fffff800`00b9c4d8 fffff800`03565ca6 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`06a4eb60 : nt!KeBugCheckEx
fffff800`00b9c4e0 fffff800`037172fc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffff800`034dffda : nt!PnpBugcheckPowerTimeout+0x76
fffff800`00b9c540 fffff800`034e55fc : 00000000`00000000 fffffa80`00000000 00000000`40dd0000 00000000`0000003f : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff800`00b9c570 fffff800`034e5496 : fffffa80`06aa44c8 fffffa80`06aa44c8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034e537e : 0000021d`efbbd438 fffff800`00b9cc58 00000000`00e3aadd fffff800`03653e28 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034e5167 : 000000b9`3b8c7ec3 000000b9`00e3aadd 000000b9`3b8c7ed9 00000000`000000dc : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034d196a : fffff800`0364fe80 fffff800`0365dcc0 00000000`00000000 fffffa80`07ec7210 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .thread 0xfffffa8006a4eb60 ; kb

FOLLOWUP_IP: 
nt!PnpBugcheckPowerTimeout+76
fffff800`03565ca6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PnpBugcheckPowerTimeout+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9F_nt!PnpBugcheckPowerTimeout+76

BUCKET_ID:  X64_0x9F_nt!PnpBugcheckPowerTimeout+76

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

These crashes are caused by drivers failing to respond and wake up hardware from or signal hardware to enter into a low power/shut down state when the computer enters or resumes from sleep. The most common driver problems that cause these are network adapter drivers. Recommend updating or re-installing your network adapter drivers. The current driver may be outdated or corrupt.

If you continue to have this crash after switching out network adapter drivers, run Driver Verifier and reproduce the events that led to the crash. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​

Did you determine which driver/device caused your power state failure?