BSOD Driver Power State Failure

[70runner]

BSOD Driver Power State Failure...Continuing

Just started happening within last 2 days.

Gateway P7811FX laptop (approx 2yrs old), full retail Win7 Pro x86 installed early June 2011. Never had a BSOD until last couple days. Both crashes occurred seemingly at random (not at startup).

Ran verifier as instructed here and OS crashed at startup. Able to turn off Driver Verifier in Safe Mode. Restarted normally to collect dump and perfmon files.

TIA

 

[yowanvista]

A device driver is probably the cause
For that reason old drivers should be updated:

Synaptic Touchpad driver Drivers | Synaptics
SD reader driver Fujitsu Gateway Support - Downloads & Support Documents
Conexant modem driver(s) Gateway Support - Downloads & Support Documents
Marvel Yukon Network driver Marvell - Support

*******************************************************************************
*                                                                             *
*                        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: 87bff2d8, Physical Device Object of the stack
Arg3: 82b2cae0, Functional Device Object of the stack
Arg4: 85e51ef8, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  85e51ef8

DEVICE_OBJECT: 87999510

DRIVER_OBJECT: 85dc24b0

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf20

MODULE_NAME: disk

FAULTING_MODULE: 8b218000 disk

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82acbf35 to 82ae3f2c

STACK_TEXT:  
82b2ca94 82acbf35 0000009f 00000003 87bff2d8 nt!KeBugCheckEx+0x1e
82b2cb00 82acbfae 82b2cbac 00000000 82b39380 nt!PopCheckIrpWatchdog+0x1f5
82b2cb38 82a7f039 82b476e0 00000000 7589937f nt!PopCheckForIdleness+0x73
82b2cb7c 82a7efdd 82b2fd20 82b2cca8 00000001 nt!KiProcessTimerDpcTable+0x50
82b2cc68 82a7ee9a 82b2fd20 82b2cca8 00000000 nt!KiProcessExpiredTimerList+0x101
82b2ccdc 82a7d00e 001131d2 88b95770 82b39380 nt!KiTimerExpiration+0x25c
82b2cd20 82a7ce38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82b2cd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_disk.sys

BUCKET_ID:  0x9F_IMAGE_disk.sys

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

 

[70runner]

Thx for response. Updated listed drivers. Driver Verifier returned startup BSOD. Re-collected info and attached.

Using driver verifier, could I march through each non-MS driver to see which one(s) is causing the BSOD. Painful but manageable.

TIA again

 

[70runner]

Using Driver Verifier I checked each set of non-MS drivers and discovered the O2Micro SD reader drivers would crash win7 at startup. O2Micro site doesn't have drivers - anyone know where I can find them?

 

[yowanvista]

Using Driver Verifier I checked each set of non-MS drivers and discovered the O2Micro SD reader drivers would crash win7 at startup. O2Micro site doesn't have drivers - anyone know where I can find them?

Try obtaining them from Windows Update. If no new drivers are found you should uninstall that device
The oldest driver I found in your dumps belongs to PowerISO or any other such CD/DVD Imaging software

 

[70runner]

Windows update says they are latest and greatest. After googling a bit I discovered some about 6mos newer and installed them. Ran Driver Verifier with those and no BSOD at startup. Hopefully that will do the trick. I'll update the others as well. Thx for your help.