Windows 10: system_thread_exception_not_handled: what failed: igdkmd64.sys

Dell Optiplex790 USFF desktop with onboard Intel graphics, Win 10. In the last week a BSOD has randomly popped up about several times when I've been using FireFox. No game playing. In last case I was simply composing a post on a forum The system reboots and "fixes" itself, runs a few days, then another BSOD. The screen reads: "system_thread_exception_not_handled" and gives cause as igdkmd64.sys that 'appears' to be a graphic's driver issue according to this and that source. Those fixes however refer to a ‘VIDEO_TDR_FAILURE igdkmd64.sys’ error and not the exact "system_thread_" I'm seeing. Is this hardware or software issue? Attaching dmp files (which I only learned about today). TIA

:)

 

Blue Screen when upgraded to windows 10

After upgrading from windows 7 to 10 i've been getting the error "System_Thread_Exception_Not_Handled igdkmd64.sys"

Any fixes on this? or am I going to revert to windows 7?

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (igdkmd64.sys)

I updated my nvidia driver, when i tried to update the intel driver it didn't work and crashed again.

 

Hello mrag,

Welcome to TenForums *Smile

Please have another attempt at the posting the zip file - the one you uploaded is empty.

Thanks!

 

Well that's kind of embarrassing. Trying again, file says it's now 1.1 Mb so something is there if I can only get it attached. FWIW, have now gotten BSOD on Sept 2, 3, 4, 7, 8 at random times and while the pc has been on for a while (sometimes even overnight).

 

Yes, that has worked *Smile

DELL issued a BIOS update for your system that I would recommend that you apply. It could make a difference to this BSOD.

http://www.dell.com/support/home/us/...ivers/advanced

 

Hi mrag,

The bugchecks you are running into are likely being caused by by igdkmd64.sys, as you originally suggested.

From the stack below, you can see that the graphics driver is being reset, likely due to it becoming unresponsive. This is seen from dxgmms1!VidSchiResetEngine, and the subsequent calls referencing TDR, Timeout Detection and Recovery.

Code: *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys 0xffffc4001c94cd90 : 0xffffc4001c94ce70 : !da ""Vertex Buffer at 0x7499749a"" 0xffffc4001c94cda8 : 0xfffff80155aca5d8 : !da ""Vertex Buffer at 0x%x"" 0xffffc4001c94cdb0 : 0xffffd5851d21ca64 : !da ""Vertex Buffer at 0x7499749a"" 0xffffc4001c94cdb8 : 0xfffff80155aca5c8 : !da ""Context at 0x%x"" 0xffffc4001c94cde8 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94ce08 : 0xffffc4001c94ce70 : !da ""Vertex Buffer at 0x7499749a"" 0xffffc4001c94ce70 : 0x4220786574726556 : !da ""Vertex Buffer at 0x7499749a"" 0xffffc4001c94ce78 : 0x7461207265666675 : !da ""uffer at 0x7499749a"" 0xffffc4001c94ce80 : 0x3739393437783020 : !da "" 0x7499749a"" 0xffffc4001c94cea8 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94cf08 : 0xfffff80153a0b9b6 : dxgkrnl!DpSynchronizeExecution+0xa6 0xffffc4001c94cf30 : 0xfffff80155aca7f8 : !da "PR_History" 0xffffc4001c94cf40 : 0xfffff80155aca6d8 : !da ""Curr PR Batch"" 0xffffc4001c94cf50 : 0xfffff80155aca708 : !da ""Aux PR Batch"" 0xffffc4001c94cff0 : 0x2052502072727543 : !da ""Curr PR Batch at 0x1ef7c000"" 0xffffc4001c94cff8 : 0x7461206863746142 : !da ""Batch at 0x1ef7c000"" 0xffffc4001c94d000 : 0x6337666531783020 : !da "" 0x1ef7c000"" 0xffffc4001c94d010 : 0x4220525020787541 : !da ""Aux PR Batch at 0x1efb9000"" 0xffffc4001c94d018 : 0x2074612068637461 : !da ""atch at 0x1efb9000"" 0xffffc4001c94d020 : 0x3039626665317830 : !da "0x1efb9000" 0xffffc4001c94d0b0 : 0xfffff80155aca858 : !da "PR_Contents" 0xffffc4001c94d0b8 : 0xfffff80155aca6f0 : !da ""Prev PR Batch"" 0xffffc4001c94d0e8 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d1a0 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d230 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d270 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d278 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d288 : 0xfffff80153a03695 : dxgkrnl!DXGVALIDATIONPROCESSATTACH:XGVALIDATIONPROCESSATTACH+0x25 0xffffc4001c94d2b8 : 0xfffff80153b7e374 : dxgkrnl!DXGADAPTER::_DdiCollectDbgInfoNoLocks+0x100 0xffffc4001c94d2f8 : 0xfffff80153b9793e : dxgkrnl!TdrUpdateDbgReport+0x16e 0xffffc4001c94d308 : 0xfffff80153a03d7d : dxgkrnl!DXGADAPTER::AcquireDdiSync+0x3d 0xffffc4001c94d328 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d348 : 0xfffff80153b96411 : dxgkrnl!TdrCollectDbgInfoStage1+0x421 0xffffc4001c94d388 : 0xfffff80311f93bc8 : nt!NonPagedPoolDescriptor+0x8 0xffffc4001c94d3b0 : 0xffffd5851d205630 : !da "{D00CE1F5-D60C-41C2AF75A4370C9976A3}A" 0xffffc4001c94d428 : 0xfffff80153b95ea9 : dxgkrnl!TdrAllocatePool+0x35 0xffffc4001c94d458 : 0xfffff80153b96ea5 : dxgkrnl!TdrCreateRecoveryContext+0x15 0xffffc4001c94d488 : 0xfffff80155639c97 : dxgmms1!VidSchiResetEngine+0x24b 0xffffc4001c94d4b8 : 0xfffff80311c48208 : nt!KiSearchForNewThread+0x218 0xffffc4001c94d518 : 0xfffff80311c47ae6 : nt!KiSwapThread+0x1b6 0xffffc4001c94d5c8 : 0xfffff80311c47461 : nt!KiCommitThreadWait+0x101 0xffffc4001c94d668 : 0xfffff80311c46d78 : nt!KeWaitForSingleObject+0x2b8 0xffffc4001c94d698 : 0xfffff80153a03d7d : dxgkrnl!DXGADAPTER::AcquireDdiSync+0x3d 0xffffc4001c94d6a8 : 0xfffff80153a03cf6 : dxgkrnl!DXGADAPTER::ReleaseDdiSync+0x36 0xffffc4001c94d6d8 : 0xfffff80153a23dcf : dxgkrnl!ADAPTER_RENDER:diQueryDependentEngineGroup+0x21f 0xffffc4001c94d758 : 0xfffff80153b95f1a : dxgkrnl!TdrAllowToDebugEngineTimeout+0x5a 0xffffc4001c94d788 : 0xfffff80155681fa8 : dxgmms1!VidSchiResetEngines+0x98 0xffffc4001c94d7c8 : 0xfffff8015565483a : dxgmms1!VidSchWaitForCompletionEvent+0x48a 0xffffc4001c94d808 : 0xfffff80153a0344a : dxgkrnl!ADAPTER_RENDER:diPreemptCommand+0xfe 0xffffc4001c94d838 : 0xfffff80155622231 : dxgmms1!VidSchiUpdateNodeRunningTime+0x39 0xffffc4001c94d848 : 0xfffff80153a0b9b6 : dxgkrnl!DpSynchronizeExecution+0xa6 0xffffc4001c94d888 : 0xfffff80155653ea9 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d 0xffffc4001c94d898 : 0xfffff8015562bf07 : dxgmms1!VidSchiSendToExecutionQueue+0xa17 0xffffc4001c94d978 : 0xfffff80155623c44 : dxgmms1!VidSchiCompletePreemption+0x28 0xffffc4001c94d9b8 : 0xfffff8015562c78d : dxgmms1!VidSchiScheduleCommandToRun+0x78d 0xffffc4001c94dac8 : 0xfffff80155623498 : dxgmms1!VidSchiCompleteRewindPacket+0x1b8 0xffffc4001c94db18 : 0xfffff80311c77e98 : nt!ExReleaseResourceLite+0xb8 0xffffc4001c94db28 : 0xfffff8015562367a : dxgmms1!VidSchiSetTransferContextRunningTime+0x6a 0xffffc4001c94db78 : 0xfffff8015567064a : dxgmms1!VidSchiRun_PriorityTable+0x2a 0xffffc4001c94dbc8 : 0xfffff8015567060b : dxgmms1!VidSchiWorkerThread+0x9b 0xffffc4001c94dbe0 : 0xfffff80155670570 : dxgmms1!VidSchiWorkerThread 0xffffc4001c94dc08 : 0xfffff80311cf0ac7 : nt!PspSystemThreadStartup+0x47 0xffffc4001c94dc18 : 0xfffff80311d85967 : nt!SwapContext+0x317 0xffffc4001c94dc30 : 0xfffff8031200da40 : nt!KiInitialThread 0xffffc4001c94dc50 : 0xfffff8031200da40 : nt!KiInitialThread 0xffffc4001c94dc58 : 0xfffff80311d859e6 : nt!KiStartSystemThread+0x16 0xffffc4001c94dc70 : 0xfffff80311cf0a80 : nt!PspSystemThreadStartup[/quote]
I would suggest updating to the latest release of Intel's Video driver that Dell supports for your model.

 

To do a second spam here ;-)...windows eventlog shows that too:

Code: 2017-08-17 05:43:11 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-17 06:46:05 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-17 06:50:07 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-17 06:54:52 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-18 10:52:48 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-19 01:35:29 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-19 01:35:31 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-19 01:35:34 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-19 06:43:23 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-19 06:43:46 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-19 07:00:06 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-21 08:26:07 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-21 22:09:54 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-22 02:15:00 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-22 02:15:17 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-22 02:15:21 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-22 19:25:04 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-23 04:49:42 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-23 12:50:13 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-23 20:38:20 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-24 03:31:07 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-24 07:02:10 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 09:28:51 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 09:35:06 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 09:56:15 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 10:45:15 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 20:50:03 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 20:50:05 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-26 21:38:45 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-27 06:09:57 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-28 12:17:18 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-28 12:38:14 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-28 21:10:19 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-29 04:13:24 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-29 04:14:30 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-29 04:14:43 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-30 02:26:01 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-30 11:11:56 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-30 11:13:00 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-30 23:53:52 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-31 07:51:28 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-31 19:58:10 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-08-31 20:44:05 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-01 15:43:18 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-02 07:46:17 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-02 08:09:47 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-02 11:03:03 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-02 12:48:47 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 11:47:44 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 18:40:48 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 18:45:47 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:00:39 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:00:45 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:00:47 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:00:50 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:00:51 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:04:20 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:04:23 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:04:23 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:10:20 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-03 21:11:17 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-04 09:34:21 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-04 09:34:37 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-04 10:16:27 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-05 17:35:28 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-06 01:51:49 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-06 03:10:22 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-06 09:44:52 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-06 15:49:02 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-06 20:48:45 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 06:27:41 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 06:30:45 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 20:32:48 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 20:33:21 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 20:33:57 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 20:34:49 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-07 21:34:25 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-08 07:06:20 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-08 07:08:14 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-08 11:21:02 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 13:02:53 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 13:03:56 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:06:28 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:07:05 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:08:48 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:09:37 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:10:37 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:11:47 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 20:14:53 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 22:26:45 Warning: Display driver igfx stopped responding and has successfully recovered. 2017-09-09 22:32:50 Warning: Display driver igfx stopped responding and has successfully recovered.[/quote]

 

I would suggest updating to the latest release of Intel's Video driver that Dell supports for your model.[/quote]
That would have been enough:

Code: BugCheck 1000007E, {ffffffffc0000005, fffff80d4f038a88, ffffcb8147766ab8, ffffcb8147766300} Probably caused by : igdkmd64.sys ( igdkmd64+c8a88 ) Followup: MachineOwner[/quote]

 

For last two days, everything appeared working well. Today a few minutes after starting and with only Firefox and one tab running, I got the same BSOD as before. System rebooted and now seems operational again. I noted in a previous reply here the sentence

One thing I have been noticing for 2-3 weeks, perhaps longer, sometimes if I left the machine running with Firefox open and come back an hour or more later, I will have a message "FireFox is not responding" and it can take a while to get into task manager to shut Firefox down as the mouse is also affected. I'm now wondering if this was a warning sign. Note if Firefox reported "not responding" I did not then get the BSOD. The BSOD seems to suddenly pop up.

Does this intermittent issue sound strictly like a driver update problem? Or might it be a hardware issue?

 

Did you apply the BIOS update as I advised?

 

I have not applied the BIOS update. I have no experience in that area and in the past have heard it can be involved and possibly create a doorstop of my pc. I was also hoping to narrow down the issue a little more as I am also facing a very short warranty time window. I'm worried I can screw up both.

Is a Dell BIOS update a simple download and "automatic self-installed" process?
Given the intermittent BSOD, Is this likely a software or hardware issue?

Thanks for the help.

 

I believe the DELL BIOS installations are self installing and in that sense they are less trouble to install than some other systems

Please explain the warranty statement.

It is not possible at this stage to be definitive about software versus hardware - I would tend to suspect software until proven otherwise.

 

In the event logs was: Application firefox.exe has been blocked from accessing Graphics hardware.

1) See if you can save your Firefox browser bookmarks to another browser.
2) Then uninstall and reinstall Firefox.

3) And reinstall the Intel graphics driver.

4) open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /restorehelath
7) chkdsk /scan
8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread



Code: Event[6541]: Log Name: System Source: Display Date: 2017-08-22T02:15:37.018 Event ID: 4109 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-59MHFCS Description: Application firefox.exe has been blocked from accessing Graphics hardware.[/quote]


Code: Name Intel(R) HD GraphicsPNP Device ID PCI\VEN_8086&DEV_0102&SUBSYS_04AD1028&REV_09\3&11583659&0&10 Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible Adapter Description Intel(R) HD Graphics Adapter RAM 1.75 GB (1,883,795,456 bytes) Installed Drivers igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32 Driver Version 9.17.10.4459 INF File oem6.inf (iSNBD0 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 59 hertz Bits/Pixel 32 Memory Address 0xE0C00000-0xE0FFFFFF Memory Address 0xD0000000-0xDFFFFFFF I/O Port 0x00003000-0x0000303F IRQ Channel IRQ 4294967294 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\drivers\igdkmd64.sys (9.17.10.4459, 5.13 MB (5,382,856 bytes), 3/9/2017 1:16 AM)[/quote]

 

Since so many Problems found I really recommend a clean install of win 10. Some more bad stuff I found too.