Display Driver crashes with DMP file

[prizna]

I have been having a lot of trouble with my Display Driver crashing recently and haven't really been able to get an answer online for what may be causing it. I have tried old and new drivers as well as using DDU the make sure it is a full clean install with no change. The driver crashes very often, usually recovering but sometimes my screen will just freeze and I will have to force reboot my PC.

Looking in reliability history I have found some DMP files at the time of the crashes, these aren't BSOD DMPs, they can however be read in BlueScreenView, unfortunately I am unable to make much sense from the information given to me from BlueSCreenView, so if anyone is able to understand what the DMP means and maybe what is causing it, it would be appreciated.

Im not sure how else I could post the dmp file so here is an image of what it shows.

thanks,

EDIT: I just received this when attempting to boot my PC:

No overclocking is present on my PC.

 

[Trouble]

You may want to consider a BIOS Update.
Check with the Gigabyte support site specifically for your particular board's model and importantly Revision Number (there are a couple and it should be printed on your board).
Looks like there may be two updates since F11 (your current version), AND one "beta" BIOS which I wouldn't necessarily recommend.

 

[prizna]

You may want to consider a BIOS Update.
Check with the Gigabyte support site specifically for your particular board's model and importantly Revision Number (there are a couple and it should be printed on your board).
Looks like there may be two updates since F11 (your current version), AND one "beta" BIOS which I wouldn't necessarily recommend.

After pressing a key to continue, it seemed to boot as normal, I was running on windows 10 for quite some time before my issues started, they started about a month or so a go, is it possible for my BIOS to just all of a sudden become a problem?
Also do you think this is related to my Display Driver crashes or could they be separate issues? Did the DMP errors reveal anything?

 

[Trouble]

Did the DMP errors reveal anything?

There was no dump file included in your post. Just an image of Blue Screen Viewer.

 

[prizna]

There was no dump file included in your post. Just an image of Blue Screen Viewer.

Sorry, but that's what I meant, I was hoping the errors it shows could be enough to help, I couldn't find a way to include the DMP file as its not a BSOD DMP, but it is DMP from my driver crash.

 

[Trouble]

IF it is a typical dump file(s) contained in C:\Windows\minidump folder you should be able to copy the contents to another folder on your desktop.
Zip that folder up and attach it to your post.
Maybe someone will have a look and see if it includes any additional info.

is it possible for my BIOS to just all of a sudden become a problem?

I can't say for certain.
I can say that as you upgrade / update Windows 10, as well as various other hardware component drivers the BIOS that supports the underlying system architecture (Chipset, etc.,) may very well need to be updated.
Generally speaking that's why BIOS updates exist and why the system board manufacturers provide them. Sometimes they provide bug fixes (system stability) and sometimes they provide support for newer features

 

[prizna]

IF it is a typical dump file(s) contained in C:\Windows\minidump folder you should be able to copy the contents to another folder on your desktop.
Zip that folder up and attach it to your post.
Maybe someone will have a look and see if it includes any additional info.

I can't say for certain.
I can say that as you upgrade / update Windows 10, as well as various other hardware component drivers the BIOS that supports the underlying system architecture (Chipset, etc.,) may very well need to be updated.
Generally speaking that's why BIOS updates exist and why the system board manufacturers provide them. Sometimes they provide bug fixes (system stability) and sometimes they provide support for newer features

Thanks for the reply, I'm at work right now, so I will try to post the dump file when I get home.

 

[prizna]

IF it is a typical dump file(s) contained in C:\Windows\minidump folder you should be able to copy the contents to another folder on your desktop.
Zip that folder up and attach it to your post.
Maybe someone will have a look and see if it includes any additional info.

I can't say for certain.
I can say that as you upgrade / update Windows 10, as well as various other hardware component drivers the BIOS that supports the underlying system architecture (Chipset, etc.,) may very well need to be updated.
Generally speaking that's why BIOS updates exist and why the system board manufacturers provide them. Sometimes they provide bug fixes (system stability) and sometimes they provide support for newer features

Just one more thing, what are the potential causes of the boot failure I received? It mentions over clocking which I'm not doing, but also voltage changes, is it possible I may have a faulty PSU or possibly be a problem with my motherboard or GPU (I am also getting display driver crashes)

 

[Trouble]

IDK..... the message was apparently from the System Setup Utility (BIOS) that's one of the reasons I suggest that perhaps a BIOS Update might be a consideration.
With respect to your PSU, I couldn't possible say as I don't have any idea what you are using but a faulty or failing PSU or simply one that is not up to the task can result in any number of problems including BSODs.

 

[prizna]

IDK..... the message was apparently from the System Setup Utility (BIOS) that's one of the reasons I suggest that perhaps a BIOS Update might be a consideration.
With respect to your PSU, I couldn't possible say as I don't have any idea what you are using but a faulty or failing PSU or simply one that is not up to the task can result in any number of problems including BSODs.

Here are my dump files from the display driver crash.

 

[Saltgrass]

First, I agree with the Bios update suggestion just in case it may be involved.

Second, are you using the onboard Intel Graphics on that system. I have an ASUS board with that processor but I have not upgraded it to Windows 10. The link below is for the Bug Check code you received. I would check it but it seems when I left the Insider program I lost access to the Windows 10 debuggers.

Also, some of those boards have a CPU boosting utility which may be speeding up the processor. If it does you might try turning that off for testing.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557271(v=vs.85).aspx

Most of this is over my head but you may see something to help understand the problem.

 

[Trouble]

Both dump files are very similar with a slightly different Bugcheck String.

BugCheck 117, {ffffe000b6305010, fffff800373c03c4, 0, 0}
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe000b6305010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800373c03c4, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

FAULTING_IP:
nvlddmkm+1703c4
fffff800`373c03c4 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

STACK_TEXT:
ffffd000`22b61a00 fffff800`35186b1c : ffffe000`b6305010 00000000`80000000 ffffe000`b6305010 ffffe000`bc04e8f0 : watchdog!WdDbgReportRecreate+0x104
ffffd000`22b61a50 fffff800`3518607f : ffffc000`00000000 ffffc000`f78e06d0 ffffe000`b6305010 ffffe000`b9885408 : dxgkrnl!TdrUpdateDbgReport+0xec
ffffd000`22b61aa0 fffff800`35172b75 : ffffc000`f9050630 ffffe000`b98853a0 ffffe000`b98853a0 ffffe000`b9885408 : dxgkrnl!TdrCollectDbgInfoStage2+0x1df
ffffd000`22b61ad0 fffff800`35186785 : fffff800`33e401c0 00000000`00000000 00000000`00000000 fffff801`457b2200 : dxgkrnl!DXGADAPTER::Reset+0x21d
ffffd000`22b61b20 fffff800`351868db : 00000000`00000200 fffff801`457b2340 ffffe000`bc25fcc8 fffff800`333b32c0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`22b61b50 fffff801`454706a9 : ffffe000`bb093200 fffff800`35186880 ffffe000`bbf1cc00 ffffe000`bc25fcc8 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b
ffffd000`22b61b80 fffff801`45502895 : 00000004`ad9bbffe 00000000`00000080 ffffe000`b5624040 ffffe000`bb093200 : nt!ExpWorkerThread+0xe9
ffffd000`22b61c10 fffff801`45566906 : ffffd000`4629c180 ffffe000`bb093200 fffff801`45502854 fffff800`33e7d8af : nt!PspSystemThreadStartup+0x41
ffffd000`22b61c60 00000000`00000000 : ffffd000`22b62000 ffffd000`22b5c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

AND

BugCheck 141, {ffffe00088fb7010, fffff801cd7e03c4, 0, 2b5c}

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe00088fb7010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff801cd7e03c4, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000002b5c, Optional internal context dependent data.

FAULTING_IP:
nvlddmkm+1703c4
fffff801`cd7e03c4 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

STACK_TEXT:
ffffd000`4f51a5a0 fffff801`c97c6b1c : ffffe000`88fb7010 ffffd000`4f51a740 ffffe000`88fb7010 ffffe000`842295a0 : watchdog!WdDbgReportRecreate+0x104
ffffd000`4f51a5f0 fffff801`cb751549 : 00000000`00000000 00000000`00000000 ffffe000`86ba1000 ffffe000`86ba1000 : dxgkrnl!TdrUpdateDbgReport+0xec
ffffd000`4f51a640 fffff801`cb7ba9f8 : ffffe000`86ba1000 00000000`00000000 00000000`00000001 ffffe000`86ba3001 : dxgmms2!VidSchiResetEngine+0x675
ffffd000`4f51a920 fffff801`cb7a11b1 : ffffe000`86ba1000 ffffe000`86ba3000 00000000`00000000 ffffe000`86ba3000 : dxgmms2!VidSchiResetEngines+0x84
ffffd000`4f51a960 fffff801`cb76a5ad : 00000000`00000002 00000000`00165ba9 00000000`0032d031 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x36ba1
ffffd000`4f51a9c0 fffff801`cb73aed4 : 00000000`00000002 ffffe000`843116b0 00000000`c0000000 ffffe000`8b361740 : dxgmms2!VidSchiWaitForSchedulerEvents+0x31d
ffffd000`4f51aa80 fffff801`cb79a68d : ffffe000`839a8980 ffffd000`4f51abd0 ffffe000`839a8900 ffffe000`86ba3000 : dxgmms2!VidSchiScheduleCommandToRun+0x5a4
ffffd000`4f51ab80 fffff801`cb79a650 : ffffe000`86ba3500 ffffe000`86ba3000 00000000`00000080 ffffe000`82a1c000 : dxgmms2!VidSchiRun_PriorityTable+0x2d
ffffd000`4f51abd0 fffff800`f115b895 : 00000004`ad9bbffe fffff800`f11bf7cf 7253df73`00010023 00000000`01060f4e : dxgmms2!VidSchiWorkerThread+0x80
ffffd000`4f51ac10 fffff800`f11bf906 : ffffd000`54255180 ffffe000`86bfd840 fffff800`f115b854 75b07d88`48401f7d : nt!PspSystemThreadStartup+0x41
ffffd000`4f51ac60 00000000`00000000 : ffffd000`4f51b000 ffffd000`4f515000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

Both are showing a problem with "dxgkrnl" Microsoft DirectX graphics kernel subsystem (Dxgkrnl.sys) and both are blaming nvlddmkm (nVidia GPU driver). Which I'm betting is a false positive and nVidia is just getting the blame.
AGAIN..... consider updating the BIOS (last time I will mention it). Double check with the board manufacturer / Intel and make sure you have the latest Chipset drivers and Storage controller drivers.
The following five drivers need your attention

anodlwfx.sys 3/6/2009 Alpha Networks Filer driver (too old)
HECIx64.sys 10/19/2010 Intel Management Engine Interface (probably too old) Go here https://downloadcenter.intel.com/ run the auto update utility and see if Intel has any updates for your board.
Dnetr28ux.sys 1/7/2013 Dlink wireless adapter. If you are using this see if Dlink has something newer for a Windows 10 driver
PLTGC.sys 4/12/2013 C-Media USB Audio Driver. See if there is anything newer than a 3 + year old driver
RTKVHD64.sys 9/10/2013 Realtek Audio Driver. Not sure why you are using two different Audio drivers. You might consider picking one and removing the other.

The HECIx64 driver does not bode well for you having all your drivers installed and up to date.

 

[prizna]

The HECIx64 driver does not bode well for you having all your drivers installed and up to date.

Just to clarify, by this quote are you saying that the HECIx64 driver will not operate well if all others are not up to date?

I will be updating my BIOS I just want to make sure that I check everything else first, as I have heard that updating BIOS can be harmful to the PC if the update fails.

 

[Saltgrass]

I will be updating my BIOS I just want to make sure that I check everything else first, as I have heard that updating BIOS can be harmful to the PC if the update fails.

A failed Bios Update can make a system unusable. You will see several warnings about not interrupting the process because that will cause it to be in an intermediate state and refuse to boot.

Newer Bioses have emergency recovery options, so check you motherboard manual before you start an update and make sure you know what process to follow if something goes wrong. If you have the correct bios update image things should be fine. But, of course, it is your decision...

 

[Trouble]

A BIOS update, can be a bit tense.
Fortunately most board manufacturers have a Windows app to perform the firmware update for you so it's rare that you need to do anything special with boot disks like in the old days.
IT is however, absolutely critical that you obtain the exact BIOS download for your board number and revision number specifically.

Just to clarify, by this quote are you saying that the HECIx64 driver will not operate well if all others are not up to date?

All I'm saying is that, that driver seems incredibly old and I would suspect the Intel has something much more current. I'm not even sure that the Intel Management Engine even uses that particular driver anymore.
Unfortunately, my Intel based system is not up and running right now, so I can't look to verify.