Frequent Crashes At 4K With Subtitles

  Thread Rating:
  • 2 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
DJ_Izumi Offline
Posting Freak
Posts: 1,265
Joined: Jul 2007
Reputation: 19
Post: #31
(2017-07-10 21:38)Kib Wrote:  I was expecting that, but it is always best to test with a nightly because that is where development happens thx for testing

Anything I can do to help facilitate a fix. Smile
find quote
Paxxi Offline
Team-Kodi Member
Posts: 248
Joined: May 2009
Reputation: 9
Location: Sweden
Post: #32
It's likely not a hardware issue with AMD cards but a driver issue and those are the same or pretty much the same for all recent models.
Now I haven't been able to find something from the crashes yet so I'm trying to figure out the next step here in how to get more info.

Sent from my SM-G900F (typie typie)

The janitor, cleaner of cruft, defender of style. Also known as the unfunny guy that doesn't understand signatures.
find quote
cosmo321 Offline
Junior Member
Posts: 42
Joined: Nov 2013
Reputation: 0
Post: #33
Crossing my fingers you're able to solve it. Let us know if we can test anything for you. Big Grin
find quote
Paxxi Offline
Team-Kodi Member
Posts: 248
Joined: May 2009
Reputation: 9
Location: Sweden
Post: #34
So far haven't been able to find any useful information in the dump files you've provided.

If you'd be able to test the following and send me the generated dump file after. These will be larger and can contain things like passwords so either send me an email paxxi at kodi dot tv or a PM.

Launch Kodi as normal, 17.3 ( not a nightly)
download procdump from https://technet.microsoft.com/en-us/sysi...s/dd996900
open cmd/powershell as admin (can be done through right click on windows button)
navigate to where you downloaded procdump
run the command "procdump -e 1 -f "Access Violation" -ma kodi.exe" it'll print out some stats.
Switch to kodi and play the sample movie and wait for the crash.
go back to cmd/powershell, procdump should now have written a new dmp file, zip it and send it to me somehow Smile

Hopefully this can give better information to track down the crash.

The janitor, cleaner of cruft, defender of style. Also known as the unfunny guy that doesn't understand signatures.
(This post was last modified: 2017-07-14 18:55 by Paxxi.)
find quote
DJ_Izumi Offline
Posting Freak
Posts: 1,265
Joined: Jul 2007
Reputation: 19
Post: #35
(2017-07-14 18:55)Paxxi Wrote:  So far haven't been able to find any useful information in the dump files you've provided.

If you'd be able to test the following and send me the generated dump file after. These will be larger and can contain things like passwords so either send me an email paxxi at kodi dot tv or a PM.

Launch Kodi as normal, 17.3 ( not a nightly)
download procdump from https://technet.microsoft.com/en-us/sysi...s/dd996900
open cmd/powershell as admin (can be done through right click on windows button)
navigate to where you downloaded procdump
run the command "procdump -e 1 -f "Access Violation" -ma kodi.exe" it'll print out some stats.
Switch to kodi and play the sample movie and wait for the crash.
go back to cmd/powershell, procdump should now have written a new dmp file, zip it and send it to me somehow Smile

Hopefully this can give better information to track down the crash.

I will find time to do this Sunday. Sorry for the wait but I'm busy juggling HDDs and cloning things and other stuff this weekend.
find quote
cosmo321 Offline
Junior Member
Posts: 42
Joined: Nov 2013
Reputation: 0
Post: #36
I've PM'd you the dump.
find quote
Paxxi Offline
Team-Kodi Member
Posts: 248
Joined: May 2009
Reputation: 9
Location: Sweden
Post: #37
Quote: # ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be wrong.
00 00afdb50 6f1d57bd atidxx32!AmdLiquidVrD3D11WrapDeviceContext+0x1328e <----- CRASH HERE
01 00afdbd4 6f1d53be atidxx32!AmdDxGsaFreeCompiledShader+0x2019d
02 00afdce8 6f1d5a4d atidxx32!AmdDxGsaFreeCompiledShader+0x1fd9e
03 00afdd64 6f18405c atidxx32!AmdDxGsaFreeCompiledShader+0x2042d
04 00afdda4 6f1839a8 atidxx32!XdxInitXopAdapterServices+0x1a00c
05 00afddcc 6f16cc1c atidxx32!XdxInitXopAdapterServices+0x19958
06 00afdde0 6f68c00b atidxx32!XdxInitXopAdapterServices+0x2bcc
07 00afddf4 6f6bcfbd atidxx32!AmdDxGsaFreeCompiledShader+0x4d69eb
08 00afde0c 6f1798be atidxx32!AmdDxGsaFreeCompiledShader+0x50799d
*** ERROR: Symbol file could not be found. Defaulted to export symbols for atiuxpag.dll -
09 00afdec8 72908700 atidxx32!XdxInitXopAdapterServices+0xf86e
*** WARNING: Unable to verify checksum for kodi.exe
0a 00afdee8 01674aa1 atiuxpag!OpenAdapter10_2+0x1bc
0b 00afdf04 6b4294e1 kodi!HookCreateResource+0x31 [c:\jenkins_slave\workspace\win-32\xbmc\rendering\dx\rendersystemdx.cpp @ 1970]
0c 00afe144 6b432fd6 d3d11!CResource<ID3D11Texture2D1>::CLS::FinalConstruct+0x331
0d 00afebf0 6b42a02f d3d11!CDevice::CreateLayeredChild+0x726
0e 00afec30 6b426b52 d3d11!NDXGI::CDeviceChild<IDXGIResource1,IDXGISwapChainInternal>::FinalConstruct+0x49
0f 00afecf0 6b424185 d3d11!NDXGI::CDevice::CreateLayeredChild+0x182
10 00afedf4 6b42eee3 d3d11!NOutermost::CDevice::CreateLayeredChild+0x215
11 00aff108 6b43bd37 d3d11!CDevice::CreateTexture2D_Worker+0x3b3
12 00aff170 016e1d7f d3d11!CDevice::CreateTexture2D+0xb7
13 00aff1ec 016e1415 kodi!CD3DTexture::CreateInternal+0x14f [c:\jenkins_slave\workspace\win-32\xbmc\guilib\d3dresource.cpp @ 246]
14 00aff214 0180ac4b kodi!CD3DTexture::Create+0x165 [c:\jenkins_slave\workspace\win-32\xbmc\guilib\d3dresource.cpp @ 215]
15 00aff274 0180a326 kodi!LoadTexture+0x3b [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videorenderers\overlayrendererdx.cpp @ 52]
16 00aff2dc 017dd1a6 kodi!OVERLAY::COverlayQuadsDX::COverlayQuadsDX+0xf6 [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videorenderers\overlayrendererdx.cpp @ 88]
17 00aff464 017dcd57 kodi!OVERLAY::CRenderer::Convert+0x336 [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videorenderers\overlayrenderer.cpp @ 375]
18 00aff498 017dd9cd kodi!OVERLAY::CRenderer::Convert+0x47 [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videorenderers\overlayrenderer.cpp @ 397]
19 00aff514 0175660e kodi!OVERLAY::CRenderer::Render+0x9d [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videorenderers\overlayrenderer.cpp @ 165]
1a 00aff608 0161e409 kodi!CRenderManager::Render+0x26e [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videorenderers\rendermanager.cpp @ 929]
1b 00aff620 0142dc0f kodi!CVideoPlayer::Render+0x19 [c:\jenkins_slave\workspace\win-32\xbmc\cores\videoplayer\videoplayer.cpp @ 5113]
1c 00aff654 014ddc68 kodi!CApplicationPlayer::Render+0x4f [c:\jenkins_slave\workspace\win-32\xbmc\applicationplayer.cpp @ 749]
1d 00aff720 01438652 kodi!CGUIWindowFullScreen::Render+0x188 [c:\jenkins_slave\workspace\win-32\xbmc\video\windows\guiwindowfullscreen.cpp @ 407]
1e 00aff758 01315dd8 kodi!CGUIControl::DoRender+0x1b2 [c:\jenkins_slave\workspace\win-32\xbmc\guilib\guicontrol.cpp @ 200]
1f 00aff780 012a62a1 kodi!CGUIWindow::DoRender+0x108 [c:\jenkins_slave\workspace\win-32\xbmc\guilib\guiwindow.cpp @ 351]
20 00aff7c0 012a5f43 kodi!CGUIWindowManager::RenderPass+0x91 [c:\jenkins_slave\workspace\win-32\xbmc\guilib\guiwindowmanager.cpp @ 1036]
21 00aff894 0128f196 kodi!CGUIWindowManager::Render+0x223 [c:\jenkins_slave\workspace\win-32\xbmc\guilib\guiwindowmanager.cpp @ 1076]
22 00aff8d8 012b1349 kodi!CApplication::Render+0x176 [c:\jenkins_slave\workspace\win-32\xbmc\application.cpp @ 1935]
23 00aff90c 011bca49 kodi!CXBApplicationEx::Run+0xd9 [c:\jenkins_slave\workspace\win-32\xbmc\xbapplicationex.cpp @ 16707566]
24 00aff984 01197868 kodi!XBMC_Run+0x289 [c:\jenkins_slave\workspace\win-32\xbmc\platform\xbmc.cpp @ 89]
25 00affbf4 0199e45b kodi!main+0x128 [c:\jenkins_slave\workspace\win-32\xbmc\platform\posix\main.cpp @ 79]
26 00affe5c 018d53cd kodi!WinMain+0x36b [c:\jenkins_slave\workspace\win-32\xbmc\platform\win32\winmain.cpp @ 123]
27 (Inline) -------- kodi!invoke_main+0x1a [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 94]
28 00affea8 748e8744 kodi!__scrt_common_main_seh+0xf6 [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 253]
29 00affebc 77e4582d kernel32!BaseThreadInitThunk+0x24

Thank you! Opening up the dump there's plenty of info to go on.
First thing is that this confirm our suspicions that it's an AMD specific issue as the crash happens in their code.

Now the question is, what have changed on our end to trigger this? Will get back to you with more information when I have something.[/quote]

The janitor, cleaner of cruft, defender of style. Also known as the unfunny guy that doesn't understand signatures.
find quote
cosmo321 Offline
Junior Member
Posts: 42
Joined: Nov 2013
Reputation: 0
Post: #38
It might be that the problem always was there and no one encountered it frequently until 4K became more common? The combination of anime and 4K-TVs is probably not the biggest segment of your users. Tongue
find quote
Paxxi Offline
Team-Kodi Member
Posts: 248
Joined: May 2009
Reputation: 9
Location: Sweden
Post: #39
can you test this build? http://mirrors.kodi.tv/test-builds/windo...x3-x86.exe

The janitor, cleaner of cruft, defender of style. Also known as the unfunny guy that doesn't understand signatures.
find quote
cosmo321 Offline
Junior Member
Posts: 42
Joined: Nov 2013
Reputation: 0
Post: #40
I still get the crash. You want a new dump?
find quote
Paxxi Offline
Team-Kodi Member
Posts: 248
Joined: May 2009
Reputation: 9
Location: Sweden
Post: #41
that would be great Smile

The janitor, cleaner of cruft, defender of style. Also known as the unfunny guy that doesn't understand signatures.
find quote
cosmo321 Offline
Junior Member
Posts: 42
Joined: Nov 2013
Reputation: 0
Post: #42
I've sent it to you.
find quote
DJ_Izumi Offline
Posting Freak
Posts: 1,265
Joined: Jul 2007
Reputation: 19
Post: #43
(2017-07-16 16:22)cosmo321 Wrote:  It might be that the problem always was there and no one encountered it frequently until 4K became more common? The combination of anime and 4K-TVs is probably not the biggest segment of your users. Tongue

I don't think so. I got a 4K TV on Black Friday and immediately put my HD 7950 to work on it without any issues with any content but I didn't notice any issues until I moved from 16 to 17, and 17.0 came out in Feb, nearly 3-4 months after I started using 4K with the HD 7950.
find quote
cosmo321 Offline
Junior Member
Posts: 42
Joined: Nov 2013
Reputation: 0
Post: #44
I had the problem with 16 as well. I got my 4K TV back in May 2016. I've had this problem ever since.
(This post was last modified: 2017-07-16 19:45 by cosmo321.)
find quote
Paxxi Offline
Team-Kodi Member
Posts: 248
Joined: May 2009
Reputation: 9
Location: Sweden
Post: #45
new test built http://mirrors.kodi.tv/test-builds/windo...x3-x86.exe

The janitor, cleaner of cruft, defender of style. Also known as the unfunny guy that doesn't understand signatures.
find quote