[yodawg]

Kodi 17.4 Krypton x86 crashes immeditely when trying to start
To reproduce it: Try to start, immediate crash: "Kodi has stopped working, a problem has caused the program to stop working"

1. Version: KODI 17.4 Krypton x86
2. Windows 7 Pro 32-bit on Lenovo ThinkPad T430 laptop
3. CPU/Arch - Intel® Core™ i5-3320M CPU @ 2.60GHz Quad-core
4. Graphics - Intel HD Grapbhics 4000 (everything I've read says this should be ok)
5. Audio - Intel Display Audio & Realtek HD Audio (tried disabling all but Realtek, tried disabling all but Intel, no good)
6. RAM: 4 GB

All Windows patches up to date
No problems with Plex or any other similar stuff on this same system - Plex runs like a champ!

Tried killing the db27 thing
Tried uninstall / rename old folders / then install Krypton fresh - same prob
Tried isolating to RealTek HD audio; and then to Intel Audio - did not make a difference
Tried running the app in Win 7 compatibility - no difference
Did NOT try the "WASAP" or whatever audio trick - if someone can give details which file to change, the setting etc, I can try that

Debug log: It has bunch of AUDIO errors (cwin32 buffer underrun)
I trimmed out the 3,000 lines of duplicate buffer underrun messages - last line of log was a buffer underrun
Log is here: https://pastebin.com/yiXv9VeW

Any help would be greatly appreciated - would LOVE to run Kodi! Always been an XBMC fan from day 1!
Thanks, (please let me know if you need more info)
yodawg

[PatK]

It's an integrated GPU, so its memory depends on how much memory you give it from your system memory. and Kodi is graphics. Registry-related malfunctions are typically caused by invalid or corrupt registry entries that get left over by various applications or appear due to software or system malfunctions, and from your log CRenderSystemDX::InitHooks: error open regystry key with error 2. (curious that registry is spelt this way, lang?) Ensure you have the latest drivers https://www.intel.com/content/www/us/en/...-4000.html in opening up the graphics driver functions I see ' the previous line repeats 10 times', so there is some difficulty here.

CRenderSystemDX::SetMonitor - Selected \\.\DISPLAY1 output
Found screen: Dummy Monitor on RDPDD Chained DD, adapter 0.
CWinSystemWin32::SetFullScreenEx (true fullscreen) on screen 0 with size 1600x900, refresh 60.000000

Found screen: Dummy Monitor on RDPDD Chained DD, is this a remote desktop? DirectX doesn't pass through remote desktop. Looks like you've chosen to open on screen 1, but Kodi is output in screen 0 https://forum.kodi.tv/showthread.php?tid=78990

[yodawg]

Ensure you have the latest drivers https://www.intel.com/content/www/us/en/...-4000.html in opening up the graphics driver functions I see ' the previous line repeats 10 times', so there is some difficulty here.

CRenderSystemDX::SetMonitor - Selected \\.\DISPLAY1 output
Found screen: Dummy Monitor on RDPDD Chained DD, adapter 0.
CWinSystemWin32::SetFullScreenEx (true fullscreen) on screen 0 with size 1600x900, refresh 60.000000

Found screen: Dummy Monitor on RDPDD Chained DD, is this a remote desktop? DirectX doesn't pass through remote desktop. Looks like you've chosen to open on screen 1, but Kodi is output in screen 0 https://forum.kodi.tv/showthread.php?tid=78990

Thanks. I will pull the latest vendor drivers vs. relying on base MS drivers.
And, while you were checking, I also researched and noticed that both audio and video are befuddled (confused) when on an RDP session.
So yes, I am on RDP, so that's another problem - audio & video do not pass through when on RDP - or not in the way that we desire/think they might.
Was trying to just configure this remotely, but may need to access it directly.

So... did not really want or care about displaying audio/sound locally - was hoping this could be more like my Plex server - i.e., setup Kodi, then use it as a remote XBMC server - so maybe I did misunderstand - sounds like this is really setting up Kodi more as a "local client," so thanks for clarifying - your reply was/is helpful.

So... I would be better served to go into TeamViewer, which is more of a "layer on top of the direct console" - and then video out will go directly to "display 0."

[yodawg]

Confirmed! Thank you PatK. When I am NOT on RDP, Kodi runs just fine. Much appreciated.
Blessings upon your camels, and upon your camels' camels.

yodawg

[PatK]

Thread marked solved.