Driver crash during HEVC playback w/DXVA2 (resume)

[GW]

Hello,

Over in the Kodi forums, many users are reporting an ongoing problem with Intel Graphics drivers for the past 2 years when it comes to playing back HEVC(x265) content on intel graphics hardware in Windows 7 and 10. This problem is widespread and affects many hardware platforms including the NUC, HD4600, HD5500, i7 6770HQ and likely most others. This crash happens when attempting to resume a HEVC encoded video file using current drivers on a windows platform with Kodi v15,16,17 and should affect any media player which uses DirectX 11 and up.

One user reports that the issue is linked to the use of "open-gop" parameter used for encoding media files using HEVC (which is default for most encoders).

I'm an IT professional but not in software development, I'd like to help in any way I can but please have a look over at the forum thread linked below for further details. This will likely affect most of your platforms as HEVC becomes more and more prevalent. Other players which are unaffected typically use a much older version of Direct X.

https://forum.kodi.tv/showthread.php?tid=289533 https://forum.kodi.tv/showthread.php?tid=289533

[GW]

Update - it seems that this is directly linked to the intel driver with DX11 + DXVA2. Disabling DXVA2 and using DXVA rendering seems to avoid this crash.

[RonaldM_Intel]

Hello WiGuy,

Thank you for bringing this situation to our attention. Can you please report this to us using the following template: ?

I would like to highlight the importance of the "Steps to Replicate" part. If you could also provide us with link(s) to some video files that can be used for testing that would be great.

Once we have this information we will try to replicate the issue internally.

Kindest Regards,

Ronald M.

[GW]

Category

Questions

Answers (N/A if not applicable)

Description

Provide a detailed description of the issue

Over in the Kodi forums, many users are reporting an ongoing problem with Intel Graphics drivers for the past 2 years when it comes to playing back HEVC(x265) content on intel graphics hardware in Windows 7 and 10. This problem is widespread and affects many hardware platforms including the NUC, HD4600, HD5500, i7 6770HQ and likely most others. This crash happens when attempting to resume a HEVC encoded video file using current drivers on a windows platform with Kodi v15,16,17 and should affect any media player which uses DirectX 11 and up with DirectPlay(DXVA2).

One user reports that the issue is linked to the use of "open-gop" parameter used for encoding media files using HEVC (which is default for most encoders).

This will likely affect most of your platforms as HEVC becomes more and more prevalent. Other players which are unaffected typically use a much older version of Direct X.

https://forum.kodi.tv/showthread.php%3Ftid%3D289533 https://forum.kodi.tv/showthread.php?tid=289533

Please place an X to the right of the option showing how often you see this issue using specific steps. (Ex: 'Every few times a game is started it flickers.' <- This would be "Often")<p> 

Always (100%):X

Often (51-99%):

Sporadic (20-50%):

Very Sporadic (<20%):

Hardware (HW)

Brand and Model of the system.

Dell Lattitude E5450

NUC based systems also

<p style="margin-bottom: 0.0001pt; font-weight: inherit; fon...

[GW]

Hi Rondald, is there any more information I can provide to help you recreate this issue?

[idata]

Hello all,

Thank you for the information you kindly provided to replicate this issue. I was able to reproduce the issue with the driver version .4624; however, with the latest systems using driver version .4729 I was not able to reproduce it. The error I get when resume the video you can check the attachment. Thank you for your interest on reporting this issue and for your kindness. We will further investigate and once we get an answer it will be post here. Best regards, Ivan U.

[GW]

Thank you for looking into this Ivan.

The error message you received is Kodi crashing as a result of the crash inside the intel driver as far as I'm told by the application developers.

I couldn't find the updated driver you mentioned using the driver update utility, please see attached screenshot. Can you advise me on how to proceed?

[DChap3]

From what I can find online the 4729 driver is only available for 6th and 7th generation graphics. For me this issue is happening with an HD5500 which only has the 4624 driver.

[DChap3]

I too am experiencing this same issue. With DXVA2 disabled performance takes a hit with HEVC decoding and some videos are not playable. With DXVA2 enabled performance is great but any attempt to resume a video causes a crash. My hardware is a NUC5i3RYH with 8GB ram, Windows 10 x64, HDMI to TV @ 1080p/60hz. Short of my internal nuc specs I've got the same information as posted above.

[RonaldM_Intel]

Hello everyone,

As Ivan mentioned, we reproduced this issue in our test lab, and a bug report has been filed with our development team, bug ID# 1406352370.

The main development work is probably going to be focused on 6th and 7th Generation drivers, but if it is fixed there, we could push for any potential fix to be ported to other driver branches.

As soon as I have an update I'll post it here.

Kindest Regards,

Ronald M.

[GW]

Thanks for the response Ronald.

It seems that there might have been a fix introduced in .4729 but I don't think that version is available for our hardware (currently stuck at .4624). Do you think it would be possible to port the fix over to an updated driver for 5th Generation Intel Graphics?

[RonaldM_Intel]

Hello WiGuy,

I got a reply from our debugging team. Upon reviewing the app crash dump, they think this is actually an issue coming from the Kodi application. I was trying to find a direct way to forward our debug results to the Kodi team, but I think the main contact point is their forums.

Do you know who can I contact from the Kodi dev team that can look at our debug results?

Side Note: I think we are planning to release a new 15.40 driver (4th and 5th Generation) but I do not have an ETA yet.

Kindest Regards,

Ronald M.

[GW]

Thanks for following up Ronald,

Unfortunately I think your right with regards to the forums being the only way to reach out to the Kodi dev team. I think if you post your request in the thread we have on Kodi's forums one would reach out to you.

https://forum.kodi.tv/showthread.php?tid=289533&page=4 https://forum.kodi.tv/showthread.php?tid=289533&page=4

I also noted one of the Team Kodi members "afedchin" seems to understand the underlying issue best, from his post on page 1.

https://forum.kodi.tv/showthread.php?tid=289533 https://forum.kodi.tv/showthread.php?tid=289533

Maybe try creating an account and message him directly?

[GW]

Hi Ronald,

I didn't have any luck with the Kodi devs unfortunately. Do you know if this specific issue was identified inside the driver and subsequently fixed in the later releases for newer hardware? I received a video driver update today via the intel driver update utility but tested for the issue again after a restart and am still crashing.

Just wondering if a fix implemented on next gen drivers might be portable back to the 5th gen.

[RonaldM_Intel]

Hello Wiguy,

The situation hasn't changed from my last update, that is, the bug identified as coming from Kodi application itself. I am adding the debug information below just in case a Kodi developer wishes to analyze it. Furthermore, since I am no developer, I think the fastest way a Kodi dev can work this directly with our development team is to post follow up questions or comments here: https://software.intel.com/en-us/forum https://software.intel.com/en-us/forum

It seems that this time, the stacks of the exception causing thread and call stack are same, i.e. exception has not gone by. And the stack points to the application (Kodi player).

This is not a GFX driver issue since igd10umd32 related tasks were executing properly.

Needs to be checked with Kodi development.

0:030> g

ModLoad: 00000000`6ab40000 00000000`6aba7000 C:\windows\SysWOW64\TextInputFramework.dll

ModLoad: 00000000`6aab0000 00000000`6ab3f000 C:\windows\SysWOW64\CoreMessaging.dll

ModLoad: 00000000`6a880000 00000000`6aaa7000 C:\windows\SysWOW64\CoreUIComponents.dll

ModLoad: 00000000`6a850000 00000000`6a878000 C:\windows\SysWOW64\ntmarta.dll

ModLoad: 00000000`6a770000 00000000`6a841000 C:\windows\SysWOW64\wintypes.dll

ModLoad: 00000000`6a760000 00000000`6a770000 C:\windows\SysWOW64\usermgrcli.dll

ModLoad: 00000000`0d470000 00000000`0d541000 C:\windows\SysWOW64\wintypes.dll

ModLoad: 00000000`0d470000 00000000`0d541000 C:\windows\SysWOW64\wintypes.dll

ModLoad: 00000000`68590000 00000000`6a760000 C:\windows\SysWOW64\igd11dxva32.dll

D3D11: Removing Device.

(cd4.e9c): C++ EH exception - code e06d7363 (first chance)

(cd4.e9c): C++ EH exception - code e06d7363 (first chance)

(cd4.e9c): C++ EH exception - code e06d7363 (first chance)

(cd4.e9c): Access violation - code c0000005 (first chance)

First chance exceptions are reported before any exception handling.

This exception may be expected and handled.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -

*** WARNING: Unable to verify checksum for C:\Program Files (x86)\Kodi\kodi.exe

*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files (x86)\Kodi\kodi.exe

ntdll_76f50000!RtlEnterCriticalSection+0x13:

76f9b263 f00fba3000 lock btr dword ptr [eax],0 ds:002b:00000024=????????

Current thread:

0:033:x86> ~.

. 33 Id: cd4.e9c Suspend: 1 Teb: 0051c000 Unfrozen "VideoPlayerVideo"

Start: *** ERROR: Symbol file could not be found. Defaulted to export symbols for ucrtbase.dll -

ucrtbase!set_app_type+0x10 (7641e840)

Priority: 0 Priority class: 32 Affinity: f

<span style=...

[GW]

Thanks for the quick response Ronald. Are you ok with me copying this over to the Kodi forum thread?

[RonaldM_Intel]

Hi again Wiguy,

Sure, go ahead and share this with Kodi, I think the more devs look at it the faster they can work on a fix within the application code.

If on the other hand, they would like to dispute the debug results, I think the best place would be transferring the conversation to the https://software.intel.com/en-us/forum Intel Developer Forum and reference internal Bug ID 1406352370.

Kindest Regards,

Ronald M.

[GW]

Hi Ronald,

"afedchin" responded with the following:

What you want to know? Intel driver is crashed and causes D3D11 Removing Device in any random place. because decoding video and rendering are parallel. It occurs only on decoding x265, no crashes on other videos, no crashes on other GPUs. You can quote my message on Intel forum.

Edit:

He seems to be pointing out that the crash is being caused by the driver suddenly doing "D3D11: Removing Device."

Please correct me if I'm wrong, you're stating that "D3D11: Removing Device" should be an exception which Kodi should be expecting to handle?

Even if it did, I don't think the kodi player would be able to resume a video if it received this every time it tried. Handling the exception might avoid an application crash but I dont think it solves the underlying issue.

I think the key to this might be hiding under why the driver is triggering a "D3D11: Removing Device"

Your support is appreciated, please let me know if I can do anything else to help this along.

Best Regards,

Greg

[AFedc]

Hi Ronald,

I'm Kodi DirectX developer and I disagree that problem in Kodi's codebase, because the issue is reproducible only on Intel driver and always something goes wrong inside the driver.

1st case:

Sample: Stream # 0:0: Video: hevc (Main), yuv420p(tv), 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 1k tbc (default)

Decoding by using HEVC_VLD_Main decoder.

Rendering with ID3D11VideoProcessor

Start a sample file from beginning and all works fine.

2nd case:

Sample: Stream # 0:0: Video: hevc (Main), yuv420p(tv), 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 1k tbc (default)

Decoding by using HEVC_VLD_Main decoder.

Rendering with ID3D11VideoProcessor

Resume the same sample file from the last stop.

Got an exception:

(91a4.6ab0): Access violation - code c0000005 (first chance)

First chance exceptions are reported before any exception handling.

This exception may be expected and handled.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\SYSTEM32\igd11dxva32.dll -

eax=00000004 ebx=146eb6a8 ecx=00000000 edx=03665000 esi=00000000 edi=13d33830

eip=774fff33 esp=1626fe2c ebp=1626fe30 iopl=0 nv up ei ng nz ac pe cy

cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010297

ntdll!RtlEnterCriticalSection+0x13:

774fff33 f00fba3000 lock btr dword ptr [eax],0 ds:002b:00000004=????????

0:012> ~.

. 12 Id: 91a4.6ab0 Suspend: 1 Teb: 03665000 Unfrozen

Start: igd11dxva32!OpenDxva11+0x10d311 (104b9bb1)

Priority: 0 Priority class: 32 Affinity: f

0:012> ~.k

# ChildEBP RetAddr

00 1626fe30 102e0e8d ntdll!RtlEnterCriticalSection+0x13

WARNING: Stack unwind information not available. Following frames may be wrong.

01 1626fe3c 101fd581 igd11dxva32+0x2e0e8d

02 1626fe58 101fd107 igd11dxva32+0x1fd581

03 1626fe80 104b9ae6 igd11dxva32+0x1fd107

04 1626feb8 104b9c2d igd11dxva32!OpenDxva11+0x10d246

05 1626fec4 740762c4 igd11dxva32!OpenDxva11+0x10d38d

06 1626fed8 77520fd9 KERNEL32!BaseThreadInitThunk+0x24

07 1626ff20 77520fa4 ntdll!__RtlUserThreadStart+0x2f

08 1626ff30 00000000 ntdll!_RtlUserThreadStart+0x1b

Looks like the exception occurs somewhere inside internal driver thread. It reproducible every time

3rd case.

Decoding: Stream # 0:0: Video: hevc (Main), yuv420p(tv), 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 1k tbc (default)

Decoding by using HEVC_VLD_Main decoder.

Rendering with shaders i.e. create two shader views from decoder surface with DXGI_FORMAR_R8_UNORM and DXGI_FORMAR_R8G8_UNORM formats for DXGI_FORMAT_NV12 texture.

Start from beginning or resuming doesn't matter.

Got an exception in absolutely random place inside GPU driver. See an example below:

(4f78.7a10): Access violation - code c0000005 (first chance)

First chance exceptions are reported before any exception handling.

This exception may be expected and handled.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\SYSTEM32\igd10iumd32.dll -

eax=...

[RonaldM_Intel]

Hello nightik,

Thank you for your input. I have forwarded your debug results and findings to our development team.

As soon as I have a reply I'll update this thread.

Kindest Regards,

Ronald M.

[RonaldM_Intel]

Hello everyone,

I'll like to provide an update on this issue.

We can confirm that with our latest internal driver from the 15.47 baseline, the issue is no longer appearing.

I do not have an ETA for the driver release yet, but please look for this to be fixed in any driver from 15.47 baseline and higher.

You can check https://www.intel.com/content/www/us/en/support/graphics-drivers/000005654.html here for more information on Intel driver naming conventions.

Kindest Regards,

Ronald M.