Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3119

June 4th, 2018 17:00

Dell Inspiron 15 5576 - Crashes related to GPU Driver

I am posting these so the engineers can find and fix the issues with the next Bios and Driver update...

so now they can look into and hopefully resolve them with this specific Model.

 

Crash Dump Analysis



Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 6/4/2018 7:17:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060418-11515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x119 (0xA, 0x1, 0x2, 0xFFFF9788A8B19000)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/4/2018 7:17:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!MmBuildMdlForNonPagedPool+0x3777)
Bugcheck code: 0x119 (0xA, 0x1, 0x2, 0xFFFF9788A8B19000)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion



2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

 

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 )

4 Operator

 • 

3.4K Posts

June 5th, 2018 10:00

Thank you for sharing the detailed crash analysis here.

 

How long have you been having this issue? Has there been any recent software changes made like installing a new software, game or Windows updates?

 

Did you update the graphics driver after the error? What is the current version of graphics driver & BIOS installed? How often do you get this blue screen error?

 

Please open device manager & expand display adapter – right click on the graphics driver & click on uninstall (do not check the box that says delete driver) restart the computer. This should refresh the driver.

 

Once complete update the graphics & chipset driver from our support site, complete all Windows update & restart the computer again.

 

Run a hardware diagnostics by following the video on this link http://bit.ly/2fJuGXB & check if there is an error.

 

For my reference, please click on the message tab next to your avatar– click “New Message” & search for my Dell username (Dell-Sreejith R) & send a private message with the service tag, registered name & email address.

June 5th, 2018 11:00

I recently did a Full PC reset wiping everything and starting over.from what I can tell everything works as it did when I bought it..

now,I have installed all the dell drivers and the like from the git go...as I started resetting up my pc the way I like...

I already did a ddu and reinstalled the driver from dell and the bios version is 1.0.7.

both were done in feb...I got them installed as well..all the drivers in the list were installed...from a fresh start...

 

so,I think it could be some issue to obsolete drivers.they are in fact several months old now.

June 5th, 2018 13:00

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

August 7th, 2018 07:00

the current drivers for this model are not 100 percent compatible. the biggest flaw is now the gpus are only using 512mb video ram from system memory leaving the 4gb gpu ram unused at all times and this is causing bottlenecks in most games.

No Events found!

Top