AnsweredAssumed Answered

Radeon 18.5.1/Radeon 18.2.1/Radeon Dell Variant 17.7/ TDR and Thread Exception not Handled Errors after install of Drivers/Then crash druing game and recording

Question asked by me262schwalbe1 on May 25, 2018

I did sfc and dism  adm cmd....

I did microsoft visuals c++ repairs...

I uninstalled malware bytes and turned off windows defender....

I got the driver notification in my old radeon 18.2.1 driver version.....

 

I am using Dell Inspiron 15 5576

Baffin series....

 

nevermind,I resolved Error code 1603.

 

Now,TDR and Thread Exception Not Handled?

 

But,I have a question?

these drivers your writing and making for all the Vega users and 580 and 570 users are working right?

 

why is it that you can't get the drivers to work flawlessly on something with hybrid graphics or switchable graphics configuration?

 

Or is this happening because the hardware doesn't have the correct Firmware?

 

 

*Edited 6/6/2018 4:28PM Eastern standard time U.S.

Can you please work with Dell and Microsoft on fixing the drivers for this system.....I did not by this to throw it in the trash.....

I need Bios,Graphics Driver and firmware updates.....

I made posts to Dell and Microsoft.......

 

now I came here and edited an old posts with updates....

 

 

On Fri 5/25/2018 9:58:28 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052518-11734-01.dmp
This was probably caused by the following module: atikmpag.sys (0xFFFFF8018582FCE8)
Bugcheck code: 0x116 (0xFFFFC20B8BBF6330, 0xFFFFF8018582FCE8, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0328911.inf_amd64_a81756cbffedb936\B328940\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


On Fri 5/25/2018 7:39:46 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052518-13875-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF802778E33EE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802778E33EE, 0xFFFF84047B71E668, 0xFFFF84047B71DEB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0328911.inf_amd64_a81756cbffedb936\B328940\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: atikmdag.sys Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


 

 


Conclusion


 

2 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

 

Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

 

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

Loading Dump File [C:\Windows\Minidump\052618-9812-01.dmp]

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

 

 

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 17134 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff801`5be9d000 PsLoadedModuleList = 0xfffff801`5c25a2f0

Debug session time: Sat May 26 00:02:29.650 2018 (UTC - 4:00)

System Uptime: 0 days 0:56:27.442

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, {ffff9f01b3655700, 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

---------

 

 

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

 

Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\052518-11609-01.dmp]

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

 

 

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 17134 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff802`bb89b000 PsLoadedModuleList = 0xfffff802`bbc582f0

Debug session time: Fri May 25 23:05:46.554 2018 (UTC - 4:00)

System Uptime: 0 days 0:37:07.346

Loading Kernel Symbols

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

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

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

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

Loading User Symbols

Loading unloaded module list

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

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 116, {ffffd70792fcd010, fffff80336a4fce8, ffffffffc0000001, 3}

 

Unable to load image atikmpag.sys, Win32 error 0n2

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

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

Probably caused by : atikmpag.sys ( atikmpag+fce8 )

 

Followup:     MachineOwner

---------

 

 

 

Message was edited by: mike shanks

 

Message was edited by: mike shanks

 

Message was edited by: mike shanks

 

Message was edited by: mike shanks

 

Message was edited by: mike shanks

 

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

 

06-05-2018 01:41 PM

Here is more from the Dell Assist logs: first two are June 3rd,last one is June 4th.

Bug check code
0x000000ea
Bug check parameters

0xffff88078edb7500,

0x0000000000000000,

0x0000000000000000,

0x0000000000000000

Device name
DirectX Graphics Kernel
Driver version
10.0.17134.81 (WinBuild.160101.0800)
Driver path
C:\Windows\System32\drivers\dxgkrnl.sys
---------------------------------------------------------------------------------------------------------------
Bug check code
0x000000ea
Bug check parameters

0xffffad8fcf729040,

0x0000000000000000,

0x0000000000000000,

0x0000000000000000

Device name
DirectX Graphics Kernel
Driver version
10.0.17134.81 (WinBuild.160101.0800)
Driver path
C:\Windows\System32\drivers\dxgkrnl.sys
------------------------------------------------------------------------------------------------
Bug check code
0x00000119
Bug check parameters

0x000000000000000a,

0x0000000000000001,

0x0000000000000002,

0xffff9788a8b19000

Device name
Watchdog Driver
Driver version
10.0.17134.1 (WinBuild.160101.0800)
Driver path
C:\Windows\System32\drivers\watchdog.sys

 

Message was edited by: mike shanks

Outcomes