AnsweredAssumed Answered

Blue Screen

Question asked by constdi on Dec 7, 2018
Latest reply on Dec 7, 2018 by constdi

For several months, my computer spontaneously reboots, it happens when the computer is idle, the result of the CrashDump file analysis makes it clear that the problem is in the video card drivers, below are the contents of the analysis of one of the files.

 

Microsoft (R) Windows Debugger Version 10.0.17763.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

 

Loading Dump File [C:\Users\Endurance\Desktop\112218-4305-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

************* 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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.24260.amd64fre.win7sp1_ldr.180908-0600

Machine Name:

Kernel base = 0xfffff800`01e0d000 PsLoadedModuleList = 0xfffff800`02047c90

Debug session time: Thu Nov 22 01:45:35.459 2018 (UTC + 10:00)

System Uptime: 0 days 8:57:48.053

Loading Kernel Symbols

.

 

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

..............................................................

................................................................

.................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {fffffa800dacfa50, 0, 0, 0}

 

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

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

Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

 

Followup:     MachineOwner

---------

 

6: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

THREAD_STUCK_IN_DEVICE_DRIVER (ea)

The device driver is spinning in an infinite loop, most likely waiting for

hardware to become idle. This usually indicates problem with the hardware

itself or with the device driver programming the hardware incorrectly.

If the kernel debugger is connected and running when watchdog detects a

timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()

and detailed message including bugcheck arguments will be printed to the

debugger. This way we can identify an offending thread, set breakpoints in it,

and hit go to return to the spinning code to debug it further. Because

KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck

information in this case. The arguments are already printed out to the kernel

debugger. You can also retrieve them from a global variable via

"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).

On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is

interrupted by hardware interrupt and ISR or DPC routine is running at the time

of the bugcheck (this is because the timeout's work item can be delivered and

handled on the second CPU and the same time). If this is the case you will have

to look deeper at the offending thread's stack (e.g. using dds) to determine

spinning code which caused the timeout to occur.

Arguments:

Arg1: fffffa800dacfa50, Pointer to a stuck thread object.  Do .thread then kb on it to find

the hung location.

Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.

Arg3: 0000000000000000, Pointer to offending driver name.

Arg4: 0000000000000000, Number of times this error occurred.  If a debugger is attached,

this error is not always fatal -- see DESCRIPTION below.  On the

blue screen, this will always equal 1.

 

 

Debugging Details:

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

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.24260.amd64fre.win7sp1_ldr.180908-0600

SYSTEM_MANUFACTURER:                                  

SYSTEM_PRODUCT_NAME:                                  

SYSTEM_VERSION:                                  

BIOS_VENDOR:  Intel Corp.

BIOS_VERSION:  BLH6710H.86A.0160.2012.1204.1156

BIOS_DATE:  12/04/2012

BASEBOARD_MANUFACTURER:  Intel Corporation

BASEBOARD_PRODUCT:  DH67BLR

BASEBOARD_VERSION:  AAG44434-200

DUMP_TYPE:  2

BUGCHECK_P1: fffffa800dacfa50

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  0dacfa50

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: d40

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 15'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  SPARK-PC

ANALYSIS_SESSION_TIME:  12-07-2018 18:07:15.0677

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff880060a2f63 to fffff80001ea09a0

 

STACK_TEXT: 

fffff880`009b0248 fffff880`060a2f63 : 00000000`000000ea fffffa80`0dacfa50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

fffff880`009b0250 fffff880`060a3112 : fffff880`009b0328 fffff880`030f5638 fffff880`009b0328 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37

fffff880`009b02c0 fffff880`0306cf24 : fffffa80`0d3db000 00000000`00000000 fffff880`009b0410 fffff880`030f5624 : dxgkrnl!TdrTimedOperationDelay+0xbe

fffff880`009b0300 fffffa80`0d3db000 : 00000000`00000000 fffff880`009b0410 fffff880`030f5624 00000000`00002710 : atikmdag+0x6af24

fffff880`009b0308 00000000`00000000 : fffff880`009b0410 fffff880`030f5624 00000000`00002710 00000000`00000028 : 0xfffffa80`0d3db000

 

STACK_COMMAND:  .thread 0xfffffa800dacfa50 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  56c67e7e6ec8a2a5ff689d3b1b7fd05135caeeef

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

 

FOLLOWUP_IP:

dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

fffff880`060a2f63 cc              int     3

 

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b94677d

IMAGE_VERSION:  6.1.7601.24260

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  X64_0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2018-11-21T15:45:35.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-09-09 10:17:35

BUILDDATESTAMP_STR:  180908-0600

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.24260.amd64fre.win7sp1_ldr.180908-0600

ANALYSIS_SESSION_ELAPSED_TIME:  36e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {b58a0dfd-90f3-63cd-1b07-7ce1b53744cb}

Followup:     MachineOwner

---------

 

If you need the CrashDump files for analysis, then I downloaded a whole pack of both my and friend's files (he has this problem)

https://drive.google.com/open?id=1pbmmL2UjMehbBLXFXNWDoHYBMDCEXBXb

 

In the release of driver 18.8.1, there is no such problem, but in all subsequent ones I observed spontaneous reboots during inactivity

Outcomes