BSOD VIDEO_DXGKRNL_FATAL_ERROR after sleep/hibernate on windows 8.1 HP Zbook 14

I have a new HP ZBook Mobile 14 workstation that I have upgraded to windows 8.1.

Unfortunately after it has gone to sleep/hibernate the machine will always BSOD referencing VIDEO_DXGKRNL_FATAL_ERROR when I try to wake it up. I have tried uninstalling and re-installing all the drivers but am not having any joy. I have also disabled fast start up and hibernate from the power options but that has not improved the situation.

I have put the mini dumps on OneDrive: MiniDumps

Any help would be greatly appreciated!

Cheers, James


  • Edited by JR-JMVP 20 hours 25 minutes ago
August 30th, 2014 10:30am

James

Ouch 21 crashes in a week.  These were related to your video driver (igdkmd64.sys) causing DirectX to fail.  There is a known problem with the March 2014 drivers (yours) and the July 2014 drivers.  As a first step I would remove the current driver and revert back to a driver that is at least 6 months older at least until they release a less buggy driver.  This is one of those times when a newer driver isnt better.

*

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


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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\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
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`d8607000 PsLoadedModuleList = 0xfffff802`d88d12d0
Debug session time: Sat Aug 30 09:42:27.923 2014 (UTC - 4:00)
System Uptime: 0 days 0:43:20.664
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 113, {17, ffffe000b97f5010, 0, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44 )

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

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

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000017, The subtype of the bugcheck:
Arg2: ffffe000b97f5010
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x113

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8001d99c9ca to fffff802d875afa0

STACK_TEXT:  
ffffd000`20945a18 fffff800`1d99c9ca : 00000000`00000113 00000000`00000017 ffffe000`b97f5010 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20945a20 fffff800`1d82e990 : ffffe000`b97f5010 ffffe000`badcf880 ffffd000`20945a88 00000000`00000018 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`20945a60 fffff800`1f096e8c : ffffe000`b99f9000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+0x44
ffffd000`20945a90 ffffe000`b99f9000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 : igdkmd64+0x3be8c
ffffd000`20945a98 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 : 0xffffe000`b99f9000
ffffd000`20945aa0 00000000`00000000 : 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 ffffe000`c0689880 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
fffff800`1d82e990 4869cf08020000  imul    rcx,rdi,208h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539a2a6c

IMAGE_VERSION:  6.3.9600.17210

BUCKET_ID_FUNC_OFFSET:  44

FAILURE_BUCKET_ID:  0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB

BUCKET_ID:  0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x113_dxgkrnl!dxgadapter::setpowercomponentactivecb

FAILURE_ID_HASH:  {e8253e80-8827-02a0-2ed9-269d46938eb3}

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

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

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000017, The subtype of the bugcheck:
Arg2: ffffe000b97f5010
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x113

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8001d99c9ca to fffff802d875afa0

STACK_TEXT:  
ffffd000`20945a18 fffff800`1d99c9ca : 00000000`00000113 00000000`00000017 ffffe000`b97f5010 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20945a20 fffff800`1d82e990 : ffffe000`b97f5010 ffffe000`badcf880 ffffd000`20945a88 00000000`00000018 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`20945a60 fffff800`1f096e8c : ffffe000`b99f9000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+0x44
ffffd000`20945a90 ffffe000`b99f9000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 : igdkmd64+0x3be8c
ffffd000`20945a98 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 : 0xffffe000`b99f9000
ffffd000`20945aa0 00000000`00000000 : 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 ffffe000`c0689880 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
fffff800`1d82e990 4869cf08020000  imul    rcx,rdi,208h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539a2a6c

IMAGE_VERSION:  6.3.9600.17210

BUCKET_ID_FUNC_OFFSET:  44

FAILURE_BUCKET_ID:  0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB

BUCKET_ID:  0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x113_dxgkrnl!dxgadapter::setpowercomponentactivecb

FAILURE_ID_HASH:  {e8253e80-8827-02a0-2ed9-269d46938eb3}

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

1: kd> lmvm dxgkrnl
start             end                 module name
fffff800`1d818000 fffff800`1d999000   dxgkrnl    (pdb symbols)          c:\symbols\dxgkrnl.pdb\9D44B2A5938E41528DA86348D6D1F5C21\dxgkrnl.pdb
    Loaded symbol image file: dxgkrnl.sys
    Mapped memory image file: c:\symbols\dxgkrnl.sys\539A2A6C181000\dxgkrnl.sys
    Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
    Image name: dxgkrnl.sys
    Timestamp:        Thu Jun 12 18:32:12 2014 (539A2A6C)
    CheckSum:         00185C7C
    ImageSize:        00181000
    File version:     6.3.9600.17210
    Product version:  6.3.9600.17210
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     dxgkrnl.sys
    OriginalFilename: dxgkrnl.sys
    ProductVersion:   6.3.9600.17210
    FileVersion:      6.3.9600.17210 (winblue_gdr.140612-1509)
    FileDescription:  DirectX Graphics Kernel
    LegalCopyright:    Microsoft Corporation. All rights reserved.

Free Windows Admin Tool Kit Click here and download it now
August 30th, 2014 10:53am

thanks very much I will try that. Do I need to roll back the Intel display driver, the AMD / ATi one or both?

Thanks again, James

August 30th, 2014 6:39pm

James

The faulting driver was agdkmd64.sys which is the intel one but if you have both why arent you using the AMD card as I suspect it has better resolution

Free Windows Admin Tool Kit Click here and download it now
August 30th, 2014 6:51pm

I have a new HP ZBook Mobile 14 workstation that I have upgraded to windows 8.1.

Unfortunately after it has gone to sleep/hibernate the machine will always BSOD referencing VIDEO_DXGKRNL_FATAL_ERROR when I try to wake it up. I have tried uninstalling and re-installing all the drivers but am not having any joy. I have also disabled fast start up and hibernate from the power options but that has not improved the situation.

I have put the mini dumps on OneDrive: MiniDumps

Any help would be greatly appreciated!

Cheers, James


you might want to use the drivers and OS HP provided, they are bad for upgrades at the best of times

August 30th, 2014 7:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics