Windows 7: BSOD Driver power state failure

Hi, all I just clean installed Windows 7 Ultimate 32bit on my Dell Vostro 1310 with 3gb ram, 1.8gHz Core2Duo, and 250gb hd. However I am getting BSOD stating driver power state failures, the computer will power up and work fine for about 20-mins then it will crash like clock work.
I do not have any exclamation marks in the device manager, I have update all my drivers with the latest and greatest Vista 32bit drivers from Dell as that is all they have right not, and I even updated the bios.
I tried to analyze the dump files myself but every time I attempt to install the debugging software it hangs at the progress bar until it becomes unresponsive then eventually crash the system. I have attached a dump file for review, if someone is willing to help me out.
Thanks

The OS becomes exasperated because the combination of the disk hardware and the drivers responsible for controlling it are taking too long to deal with a power state transition.

Try to update this driver...

iaStor Fri Jul 13 08:59:22 2007

... and get rid of this one:

SiWinAcc Tue Nov 02 06:21:31 2004

Ultimately, if the problem is not caused by a driver, the disk hardware itself may be suspect. Hopefully it's a driver!

In the short term, you may be able to work around the issue by disabling all power management - set everything to run at 100% constantly.

-----------------------------------
EDIT: BTW, the "do you have question marks in devmgmt.msc?" line of BSOD troubleshooting is a waste of time. The one thing you can pretty much rule out as the cause of a BSOD is the lack-of-driver for a device which hasn't been detected and enabled.

On a whim I just pulled my SD card and all the problems stopped responsiveness came back and no crashing.

Interesting. So presumably the drive which is slow to respond is the SD one. Thanks for letting us know.

Im going to try and find a more update driver then what I have now to see if that may help. Thanks for the help.

MG

this crash was caused by a driver causing an inconsistant power state I notice that there are some incredibly old drivers and suspect one them for the crash.

I suggest upgrading all the critical drivers like BIOS, video, wifi, etc



SiWinAcc.sys 0x8afbf000 0x8afc1880 0x00002880 0x41868cbb 11/1/2004 2:21:31 PM
secdrv.SYS 0x99a9c000 0x99aa6000 0x0000a000 0x45080528 9/13/2006 8:18:32 AM
SiRemFil.sys 0x8b5f7000 0x8b5f8580 0x00001580 0x45b7e904 1/24/2007 6:17:24 PM
SI3132.sys 0x8af3a000 0x8af4a900 0x00010900 0x4654df61 5/23/2007 7:42:09 PM
Apfiltr.sys 0x92200000 0x9222c000 0x0002c000 0x467f9086 6/25/2007 4:53:10 AM
iaStor.sys 0x8ae3d000 0x8af04000 0x000c7000 0x4696b24a 7/12/2007 5:59:22 PM
dump_iaStor.sys 0x90800000 0x908c7000 0x000c7000 0x4696b24a 7/12/2007 5:59:22 PM
tcusb.sys 0x955b9000 0x955c2e00 0x00009e00 0x46b52eb6 8/4/2007 8:58:14 PM
o2sd.sys 0x923a9000 0x923b2300 0x00009300 0x484e650c 6/10/2008 6:27:08 AM
o2media.sys 0x923b3000 0x923be100 0x0000b100 0x488e6af4 7/28/2008 7:57:24 PM




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


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

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`8078ada4?
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82808000 PsLoadedModuleList = 0x82950810
Debug session time: Sat Oct 31 14:27:17.672 2009 (GMT-5)
System Uptime: 0 days 0:22:45.576
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 8536e998

DEVICE_OBJECT: 877566a8

DRIVER_OBJECT: 86896460

IMAGE_NAME: disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf20

MODULE_NAME: disk

FAULTING_MODULE: 8b380000 disk

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 82844054 to 828e4d10

STACK_TEXT:
8078ad64 82844054 0000009f 00000003 86901030 nt!KeBugCheckEx+0x1e
8078add0 828438e8 8078ae70 00000000 8540d778 nt!PopCheckIrpWatchdog+0x1f5
8078ae08 8287204d 82949a20 00000000 28863ad2 nt!PopCheckForIdleness+0x73
8078ae4c 82871ff1 82931d20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
8078af38 82871eae 82931d20 8078af78 00000000 nt!KiProcessExpiredTimerList+0x101
8078afac 8287020e 000155f0 93d0ed34 00000000 nt!KiTimerExpiration+0x25c
8078aff4 8286f9dc 93d0ece4 00000000 00000000 nt!KiRetireDpcList+0xcb
8078aff8 93d0ece4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
8286f9dc 00000000 0000001a 00d6850f bb830000 0x93d0ece4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_disk.sys

BUCKET_ID: 0x9F_IMAGE_disk.sys

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