BSOD Vista64 Driver_Power_State_Failure

I'm going to make this brief, because the last time I had a BSOD in the middle of my post. Here's my situation, random BSODs. Diagnostics:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800a3b5050, fffffa800a2cc060, fffffa800bb39c60}
Probably caused by : sbp2port.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: fffffa800a3b5050, Physical Device Object of the stack
Arg3: fffffa800a2cc060, Functional Device Object of the stack
Arg4: fffffa800bb39c60, The blocked IRP
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800bb39c60
DEVICE_OBJECT: fffffa800a3b5050
DRIVER_OBJECT: fffffa80079dc5a0
IMAGE_NAME: sbp2port.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479198b3
MODULE_NAME: sbp2port
FAULTING_MODULE: fffffa60011de000 sbp2port
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80001eb905e to fffff80001e5a350
STACK_TEXT:
fffff800`02f2e9f8 fffff800`01eb905e : 00000000`0000009f 00000000`00000003 fffffa80`0a3b5050 fffffa80`0a2cc060 : nt!KeBugCheckEx
fffff800`02f2ea00 fffff800`01e628b3 : fffff800`02f2ead8 00000000`00000000 00000000`00000001 fffff800`01faaf01 : nt! ?? ::FNODOBFM::`string'+0x18318
fffff800`02f2ea70 fffff800`01e632f5 : fffff800`02f2ecd0 fffffa80`09e6ff02 fffff800`02f2ecc8 fffffa60`00000010 : nt!KiTimerListExpire+0x333
fffff800`02f2eca0 fffff800`01e63a9f : 000006e2`0de43fea 00000000`00000000 fffffa80`00000010 fffff800`01f7ca80 : nt!KiTimerExpiration+0x295
fffff800`02f2ed10 fffff800`01e64b62 : fffff800`01f79680 fffff800`01f79680 00000000`00000000 fffff800`01f7eb80 : nt!KiRetireDpcList+0x1df
fffff800`02f2ed80 fffff800`020325c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`02f2edb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_disk.sys_CNVIRP_IMAGE_sbp2port.sys
BUCKET_ID: X64_0x9F_disk.sys_CNVIRP_IMAGE_sbp2port.sys
Followup: MachineOwner

Can any guru tell me what may be going on? I've replaced drivers for firewire and for audio. Thanks.

Carl

Ok, now that the above is posted, I'll take a chance and try to give a little more detail. The machine is a new HP Pavillion A6750. It has an AMD CPU, with 8 gigs of RAM. The problem seemed to start after my old machine crashed (HD controller went bad) in the middle of a PCmover move. Afterwards I conducted a PCmover "undo," which consistently hung after about 90 completion. Perhaps some remnant of the aborted move is causing a problem? Seems strange, though, since PCmover doesn't move drivers, per se. I have already replaced the audio driver with the latest from realtek, and the deleted and had the system reconstruct drivers for the firewire HDs connected to the computer. I think I've pressed my luck here, so I'll save.

Info on external firewire drive: 750 gig, Maxtor One Touch; 500 gig, Seagate FreeAgent Pro.

Update: After disconnecting the Maxtor, but leaving the Seagate in place, it's now been several hours without a BSOD. The Maxtor was daisy-chained to he Seagate. I'll keep you posted tomorrow if this good behavior keeps up, or is just an anomaly.

Update: It's now been about 18 hours with no BSOD. Perhaps it was the drivers for the external Maxtor firewire drive. Anyone know if there are drivers that actually work with Vista64? Other thoughts?

It's now going on 24 hours since I disconnected the Maxtor firewire HD, and still no BSOD. Anyone have any idea what's wrong with Maxtor drivers on Vista64, and if there's a fix? -- assuming that I've actually found the problem. So far, this is an interesting conversation that I'm having with myself.

n8vz said:

So far, this is an interesting conversation that I'm having with myself.

Click to expand...

That's what happens when you price yourself out of the market by asking something very intelligent

Do you have SP1 applied? What's the timestamp on your sbp2port.sys driver?

Check this out:

You receive a Stop 0x9F error when you wake a Windows Vista-based computer that is connected to an IEEE 1394-based device

You might want to apply this hotfix and then test again:

Error message when you wake Windows Vista from sleep: "STOP: 0x000000B8"

My problem isn't related to coming out of hibernation. I've already read those threads and tried the hotfix. I do have SP1 and am up to date on all patches. My sbp2port.sys date stamp is 1/20/08. Thanks for your help. I'll try to act dumber the next time! :-)

The specific symptoms described by KB articles are frequently only a portion of what might happen due to a given root cause. Sure, that article talks about hibernation, but that might simply be the scenario in which MS encountered the problem - there may be others.

Since you seem to be able to repro easily, I'd suggest trying an even newer build of sbp2port.sys. KB seems to suggest that this one is the latest:

Stop error when you attach a Niveus Ice Vault Disc Changer to a Windows Vista SP1-based computer or to a Windows Server 2008-based computer: "STOP: 0x0000007E"

Thanks, I'll try the hotfix and report back.

Well, it's been about seven hours since the hotfix was applied and no BSOD with Maxtor Firewire external attached via diasy chain. Not sure I'm out of the woods yet, but this is encouraging.

Well, it's now two days and no BSOD. I think maybe the problem has been solved. I'll wait a little longer just to be sure, but I'm relatively confident at this point.

I'm glad to hear it.

It's now been almost a week and no more Driver_Power_State_Failure BSODs. I think I can safely conclude that this problem ihas been solved. Thank you very much H2SO4! BTW, with a screenname like that I'd expect an acid pen editorial writer, not a friendly neutralizer of acidic computer problems. :-)

No problem mate

Don't call me "friendly" though, or I'm liable to get offended.