I am constantly getting "thread stuck in device driver" blue screens only when I play games. I have tried updating all of my drivers and it still happens frequently and I am out of ideas. But I noticed my Windows 10 is not activated and i'm having trouble activating it. But can Windows 10 not being activated cause blue screens like this?
Can windows 10 not being activated cause blue screens?
- Thread starter Jon_76
- Start date
Solution
lets see, the program Microsoft give people to read the dump files is currently broken, it sees all dump files as corrupted. If anyone does pop in and read these, you might be lucky but what I would do is either.
a) Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
or b) have a look at posting instructions at top of this page and post a question on here as they have different tools to us and might be able to sort it out for you - https://www.tenforums.com/bsod-crashes-debugging/
I didn't know this was case when I asked you to leave the minidumps, or I would shown you these instead.
a) Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
or b) have a look at posting instructions at top of this page and post a question on here as they have different tools to us and might be able to sort it out for you - https://www.tenforums.com/bsod-crashes-debugging/
I didn't know this was case when I asked you to leave the minidumps, or I would shown you these instead.
Colif
Win 11 Master
- Jun 12, 2015
- 67,208
- 7,042
- 168,140
that bsod maybe caused if you have an AMD GPU? try http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html
unactivated won't cause BSOD. Did you have a legit licence as if so, you should contact MS via a number in settings/update & security/activation and show them proof and they should reactivate win 10.
unactivated won't cause BSOD. Did you have a legit licence as if so, you should contact MS via a number in settings/update & security/activation and show them proof and they should reactivate win 10.
Colif
Win 11 Master
- Jun 12, 2015
- 67,208
- 7,042
- 168,140
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD
that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it
dumps will tell us for sure, I won't guess what might be cause.
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD
that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it
dumps will tell us for sure, I won't guess what might be cause.
Colif
Win 11 Master
- Jun 12, 2015
- 67,208
- 7,042
- 168,140
lets see, the program Microsoft give people to read the dump files is currently broken, it sees all dump files as corrupted. If anyone does pop in and read these, you might be lucky but what I would do is either.
a) Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
or b) have a look at posting instructions at top of this page and post a question on here as they have different tools to us and might be able to sort it out for you - https://www.tenforums.com/bsod-crashes-debugging/
I didn't know this was case when I asked you to leave the minidumps, or I would shown you these instead.
a) Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
or b) have a look at posting instructions at top of this page and post a question on here as they have different tools to us and might be able to sort it out for you - https://www.tenforums.com/bsod-crashes-debugging/
I didn't know this was case when I asked you to leave the minidumps, or I would shown you these instead.
- Jun 16, 2016
- 4,266
- 508
- 26,590
On Sat 3/11/2017 3:07:06 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\031117-19625-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFE70B367AD080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
crash dump file: C:\WINDOWS\Minidump\031117-19625-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFE70B367AD080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Colif
Win 11 Master
- Jun 12, 2015
- 67,208
- 7,042
- 168,140
looks like B is the better response then since the debugger is broken. Whocrashed is blaming direct X again.
I was going to work out how to use debugger and then MS break it.
you could try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
Once it bsod, run Who crashed and see what driver it reveals
note: sometimes this puts you into a boot loop so helps to have a copy of win 10 installer handy to turn it off
On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB
to turn it off
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type verifer /reset and press enter
type exit and press enter
restart PC
@gardenman, how did you import that into whocrashed? I can't see anything apart from export? did you copy the dump into the minidump folder? Would help if I had a minidump folder - last BSOD was 18 months ago or so, not recorded anymore.
I was going to work out how to use debugger and then MS break it.
you could try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
Once it bsod, run Who crashed and see what driver it reveals
note: sometimes this puts you into a boot loop so helps to have a copy of win 10 installer handy to turn it off
On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB
to turn it off
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type verifer /reset and press enter
type exit and press enter
restart PC
@gardenman, how did you import that into whocrashed? I can't see anything apart from export? did you copy the dump into the minidump folder? Would help if I had a minidump folder - last BSOD was 18 months ago or so, not recorded anymore.
- Jun 16, 2016
- 4,266
- 508
- 26,590
Colif, I have a VM setup where I can throw anything in it, reboot and reset it all.
Anyway, I download the WhoCrashed (each time) and install it. I create a C:\Windows\minidump folder (it doesn't seem to be there in my Windows install in my VM). I usually get 2 UAC prompts as I do it. I copy (usually unzip) the dump file to that folder. I then run WhoCrashed and analyze the dump file and just copy/paste what it says from there, to here. If you can't figure it out, PM me questions and we'll discuss it more.
I also *think* I have the debugger installed, I have the Windows 10 kit installed, but I'm kinda clueless on how to use it. John is alot more skilled than myself when it comes to that.
Anyway, I download the WhoCrashed (each time) and install it. I create a C:\Windows\minidump folder (it doesn't seem to be there in my Windows install in my VM). I usually get 2 UAC prompts as I do it. I copy (usually unzip) the dump file to that folder. I then run WhoCrashed and analyze the dump file and just copy/paste what it says from there, to here. If you can't figure it out, PM me questions and we'll discuss it more.
I also *think* I have the debugger installed, I have the Windows 10 kit installed, but I'm kinda clueless on how to use it. John is alot more skilled than myself when it comes to that.
Colif
Win 11 Master
- Jun 12, 2015
- 67,208
- 7,042
- 168,140
I don't have minidump folder or i would have copied it in there, its only made if you get a bsod and I haven't had one in 18 months.
until debugger fixed, John & Paul NZ may have problems reading the dumps. I haven't seen them on for a few weeks. All I can offer is who crashed, driver verifer and the link to tenforums if the other 2 don't give enough clues as to what cause is.
until debugger fixed, John & Paul NZ may have problems reading the dumps. I haven't seen them on for a few weeks. All I can offer is who crashed, driver verifer and the link to tenforums if the other 2 don't give enough clues as to what cause is.
Colif
Win 11 Master
- Jun 12, 2015
- 67,208
- 7,042
- 168,140
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffffe70b367ad080, 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 "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 9.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V8.4
BIOS_DATE: 08/10/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A68HM-E33 V2 (MS-7721)
BASEBOARD_VERSION: 9.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe70b367ad080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: 367ad080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 38
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: backgroundTaskHost.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: UHHHH_COLIF-PC
ANALYSIS_SESSION_TIME: 05-13-2017 11:48:04.0986
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8060ed62dff to fffff8002d3ca6f0
STACK_COMMAND: .thread 0xffffe70b367ad080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff806`0ed62dff cc int 3
FAULT_INSTR_CODE: c48b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a7780
IMAGE_VERSION: 10.0.14393.576
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2017-03-11T20:07:06.000Z
OSBUILD: 14393
OSSERVICEPACK: 693
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-21 01:50:57
BUILDDATESTAMP_STR: 161220-1747
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.693
ANALYSIS_SESSION_ELAPSED_TIME: 164d4
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Uhhhhhh_COLIF\Desktop\031117-19625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff800`2d280000 PsLoadedModuleList = 0xfffff800`2d585060
Debug session time: Sat Mar 11 16:07:06.024 2017 (UTC - 4:00)
System Uptime: 0 days 0:04:58.721
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {ffffe70b367ad080, 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+3f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffffe70b367ad080, 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 "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 9.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V8.4
BIOS_DATE: 08/10/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A68HM-E33 V2 (MS-7721)
BASEBOARD_VERSION: 9.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe70b367ad080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: 367ad080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 38
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: backgroundTaskHost.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: UHHHH_COLIF-PC
ANALYSIS_SESSION_TIME: 05-13-2017 11:46:33.0554
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8060ed62dff to fffff8002d3ca6f0
STACK_TEXT:
ffffbb01`67e74ac8 fffff806`0ed62dff : 00000000`000000ea ffffe70b`367ad080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbb01`67e74ad0 fffff806`0ed62ebe : ffffbb01`67e74ba8 fffff806`11c2f430 ffffbb01`67e74ba8 ffffbb01`67e74c90 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f
ffffbb01`67e74b40 fffff806`11bd36d0 : ffffe70b`3705a000 00000000`00000000 ffffbb01`67e74c90 fffff806`11c2f41c : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffbb01`67e74b80 ffffe70b`3705a000 : 00000000`00000000 ffffbb01`67e74c90 fffff806`11c2f41c 00000000`00002710 : atikmdag+0x536d0
ffffbb01`67e74b88 00000000`00000000 : ffffbb01`67e74c90 fffff806`11c2f41c 00000000`00002710 00000000`00000028 : 0xffffe70b`3705a000
STACK_COMMAND: .thread 0xffffe70b367ad080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff806`0ed62dff cc int 3
FAULT_INSTR_CODE: c48b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a7780
IMAGE_VERSION: 10.0.14393.576
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2017-03-11T20:07:06.000Z
OSBUILD: 14393
OSSERVICEPACK: 693
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-21 01:50:57
BUILDDATESTAMP_STR: 161220-1747
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.693
ANALYSIS_SESSION_ELAPSED_TIME: 16524
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffffe70b367ad080, 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 "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 9.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V8.4
BIOS_DATE: 08/10/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A68HM-E33 V2 (MS-7721)
BASEBOARD_VERSION: 9.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe70b367ad080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: 367ad080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 38
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: backgroundTaskHost.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: UHHHH_COLIF-PC
ANALYSIS_SESSION_TIME: 05-13-2017 11:48:04.0986
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8060ed62dff to fffff8002d3ca6f0
STACK_COMMAND: .thread 0xffffe70b367ad080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff806`0ed62dff cc int 3
FAULT_INSTR_CODE: c48b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a7780
IMAGE_VERSION: 10.0.14393.576
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2017-03-11T20:07:06.000Z
OSBUILD: 14393
OSSERVICEPACK: 693
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-21 01:50:57
BUILDDATESTAMP_STR: 161220-1747
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.693
ANALYSIS_SESSION_ELAPSED_TIME: 164d4
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Uhhhhhh_COLIF\Desktop\031117-19625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff800`2d280000 PsLoadedModuleList = 0xfffff800`2d585060
Debug session time: Sat Mar 11 16:07:06.024 2017 (UTC - 4:00)
System Uptime: 0 days 0:04:58.721
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {ffffe70b367ad080, 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+3f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffffe70b367ad080, 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 "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 9.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V8.4
BIOS_DATE: 08/10/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A68HM-E33 V2 (MS-7721)
BASEBOARD_VERSION: 9.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe70b367ad080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: 367ad080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 38
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: backgroundTaskHost.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: UHHHH_COLIF-PC
ANALYSIS_SESSION_TIME: 05-13-2017 11:46:33.0554
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8060ed62dff to fffff8002d3ca6f0
STACK_TEXT:
ffffbb01`67e74ac8 fffff806`0ed62dff : 00000000`000000ea ffffe70b`367ad080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbb01`67e74ad0 fffff806`0ed62ebe : ffffbb01`67e74ba8 fffff806`11c2f430 ffffbb01`67e74ba8 ffffbb01`67e74c90 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f
ffffbb01`67e74b40 fffff806`11bd36d0 : ffffe70b`3705a000 00000000`00000000 ffffbb01`67e74c90 fffff806`11c2f41c : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffbb01`67e74b80 ffffe70b`3705a000 : 00000000`00000000 ffffbb01`67e74c90 fffff806`11c2f41c 00000000`00002710 : atikmdag+0x536d0
ffffbb01`67e74b88 00000000`00000000 : ffffbb01`67e74c90 fffff806`11c2f41c 00000000`00002710 00000000`00000028 : 0xffffe70b`3705a000
STACK_COMMAND: .thread 0xffffe70b367ad080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff806`0ed62dff cc int 3
FAULT_INSTR_CODE: c48b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a7780
IMAGE_VERSION: 10.0.14393.576
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2017-03-11T20:07:06.000Z
OSBUILD: 14393
OSSERVICEPACK: 693
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-21 01:50:57
BUILDDATESTAMP_STR: 161220-1747
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.693
ANALYSIS_SESSION_ELAPSED_TIME: 16524
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
Bug check thanks to Gardenman
TRENDING THREADS
-
-
-
-
-
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 4K
-
Question No POST, BIOS and video output after SSD. Reinstalling HDD makes everything work.
- Started by Fra-17x
- Replies: 2
Facebook
Twitter
Instagram