Highlighted
Johnmcl7
2 Iron

Dell Latitude 5175 blue screen of death during full screen video playback

I have a Dell Latitude 5175 (Core m5-6Y57, 8GB ram, 256GB SSD) which bluescreens during full screen video playback such as Netflix or Windows media player with a Driver_power_state_failure, it doesn't happen straight away but usually after around 10-15 minutes usage.

I checked the minidump file which suggested the Intel graphics card driver was to blame, I updated that to the latest one from Dell which made no difference, updated the chipset driver, bios and then installed the latest graphics card driver from Intel again with no difference, if anything it's worse now.  The issue also occurs when the tablet is docked or when it's not docked although in normal day to day usage, it seems fine.

I've found references to this problem on some other machines, noticeably the Surface Pro 4's but not really any solution.  The next step is to try a clean build but thought I'd see if there's anything else I can try first.  The machine is out of warranty and while it's always occurred I've just lived with it as I incorrectly through the PC had a three year warranty.

Knowledge is Power

0 Kudos
1 Reply
Johnmcl7
2 Iron

RE: Dell Latitude 5175 blue screen of death during full screen video playback

The text of the dump analysis is:

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff9209c23f7080, ffff880c2642f7f0, ffff9209c0df93f0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys

*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

Probably caused by : igdkmd64.sys

Followup: MachineOwner

---------

1: 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: ffff9209c23f7080, Physical Device Object of the stack

Arg3: ffff880c2642f7f0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffff9209c0df93f0, The blocked IRP

Debugging Details:

------------------

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a21923c

MODULE_NAME: igdkmd64

FAULTING_MODULE: fffff80b5be60000 igdkmd64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFF880C26437FB0

STACK_TEXT:  

ffff880c`2642f7b8 fffff801`2d235ab7 : 00000000`0000009f 00000000`00000003 ffff9209`c23f7080 ffff880c`2642f7f0 : nt!KeBugCheckEx

ffff880c`2642f7c0 fffff801`2d2359c2 : ffff9209`cc0a4530 ffffb980`c0868180 00000000`00000032 00000000`00000080 : nt!PopIrpWatchdogBugcheck+0xeb

ffff880c`2642f820 fffff801`2d050b63 : ffff9209`cc0a4568 ffffb980`c0868180 ffff880c`2642fa18 00000000`00000000 : nt!PopIrpWatchdog+0x22

ffff880c`2642f870 fffff801`2d051bfd : 00000000`00000000 00000000`0000b701 00000000`001687d0 ffffb980`c0868180 : nt!KiProcessExpiredTimerList+0x153

ffff880c`2642f960 fffff801`2d16b23a : 00000000`00000000 ffffb980`c0868180 00000000`00000000 ffffb980`c0874bc0 : nt!KiRetireDpcList+0x43d

ffff880c`2642fb60 00000000`00000000 : ffff880c`26430000 ffff880c`26429000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_iacamera64_IMAGE_igdkmd64.sys

BUCKET_ID:  0x9F_3_iacamera64_IMAGE_igdkmd64.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_iacamera64_image_igdkmd64.sys

FAILURE_ID_HASH:  {2e30b1d1-571c-a73d-05ea-43da6bd2b229}

Followup: MachineOwner

---------

Knowledge is Power

0 Kudos