In the past few days I have been getting a BSOD with the DRIVER_POWER_STATE_FAILURE message. Boot times take a few minutes where it used to be only one. I can't see any drivers that need updating and I haven't made any hardware changes recently. My laptop is an Asus Zenbook UX303LA running windows 8.1.

If anyone could analyse he dump file and help me out, I would be eternally grateful!

Here's the link:
https://www.dropbox.com/sh/vbbngn3kpyh4ppd/AAAMLkCYMZMx8iFEoYfItvAna?dl=0

Thanks a million in advance!

Lumness

This was Related to iaStorA.sys Intel Matrix Storage Manager driver from Intel Corp.  Yours is from 2012.  I would remove the current driver and install the newest driver available.

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


Loading Dump File [C:\Users\Ken\Desktop\021415-289843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: 
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff803`54280000 PsLoadedModuleList = 0xfffff803`54559250
Debug session time: Sat Feb 14 16:34:41.577 2015 (UTC - 5:00)
System Uptime: 0 days 0:18:06.472
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe00086f07880, fffff80356015960, ffffe0008e073a80}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00086f07880, Physical Device Object of the stack
Arg3: fffff80356015960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0008e073a80, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff8003498c000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF8035601CFB0

STACK_TEXT:  
fffff803`56015928 fffff803`54488e3e : 00000000`0000009f 00000000`00000003 ffffe000`86f07880 fffff803`56015960 : nt!KeBugCheckEx
fffff803`56015930 fffff803`54488d5e : ffffe000`8dff1530 00000000`00000001 ffffe000`8dff1568 ffffe000`8dff15a8 : nt!PopIrpWatchdogBugcheck+0xde
fffff803`56015990 fffff803`54334428 : 00000000`00000000 00000000`00000001 fffff803`54583180 fffff803`00000002 : nt!PopIrpWatchdog+0x32
fffff803`560159e0 fffff803`543d44ea : fffff803`54583180 fffff803`54583180 fffff803`545dca00 ffffe000`86f02880 : nt!KiRetireDpcList+0x4f8
fffff803`56015c60 00000000`00000000 : fffff803`56016000 fffff803`56010000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.17238

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_iaStorA_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_iaStorA_IMAGE_pci.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_iastora_image_pci.sys

FAILURE_ID_HASH:  {7d15649d-af9d-aeb2-1222-6fa8a2b3c912}

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

0: kd> !irp  ffffe0008e073a80
Irp is active with 4 stacks 3 is current (= 0xffffe0008e073be0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 ffffe00086f07880 00000000 fffff80034a348a0-fffff80034a1022c    
	       \Driver\pci	ACPI!ACPIBuildRegOnRequest
			Args: 00000000 00000000 00000000 00000002
 [ 16, 0]   0  0 ffffe00086f04630 00000000 fffff8003519a4d8-00000000    
	       \Driver\ACPI	storport!RaidAdapterPowerUpDeviceCompletion
			Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 ffffe00086e80050 00000000 fffff8035439eefc-ffffe0008dff1530 Success Error Cancel pending
	      *** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
 \Driver\iaStorA	nt!PopRequestCompletion
			Args: 00051100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe0008dff1530    

			Args: 00000000 00000000 00000000 00000000

Hello lumness,

What is your current situation?
Have you tried the solution as MVP Zigzag mentioned?

Best regards,
Fangzhou CHEN

Thanks a million for your answer! When I try to update the driver in my device manager, it tells me it's up to date. Should I uninstall and re-install instead?

lumness

Yes remove the current driver then install the newest one.  You should never ask device manager to find a driver for you but instead go to either the computer maker or the driver developers site.