[i0zjh02]

I've got a very odd problem on one of my PCs (unfortunately the main one in the lounge)

Been running the latest nightly v18 release for a while. This morning I quit Kodi and installed todays release as usual. 

As soon as I launch Kodi it crashes. I've tried reverting to earlier nightlies that ran quite happily and they crash immediately too.

I've renamed the program file...\Kodi and user profile....\roaming\Kodi folders (to in effect do a clean install) but again any version of v18 (64bit or 32bit) I install, crashes immediately I run it.

The only way I've managed to get Kodi running again is to return to V17.6 

The same nightly release works OK on 3 other clients in other rooms with no problem whatsoever,

Does anybody have any idea what else I can try (short of rebuilding the PC from scratch) in order to get Kodi 18 64 running again, clients are all Windows 10 64bit ??

Cheers

[Klojum]

Does anybody have any idea what else I can try

Kodi does create log files and crash logs for a reason.
They can sum up interesting information.
You ever took a look at those?

[i0zjh02]

Does anybody have any idea what else I can try

Kodi does create log files and crash logs for a reason.
They can sum up interesting information.
You ever took a look at those? 

:-) Thanks yes I did think to check but it seems to crash immediately it launches, there dont appear to be any new log files written. I'll try again later this evening when I get home, only had limited time this morning

[tehax]

I have simliar issue with mounted iso files reprorted here.
Link

[i0zjh02]

OK I connected remotely to my PC at home, renamed my profile..\Kodi folder so a new one gets created and again updated to the latest 64bit nightly

It immediately crashes on launch but now there is a log file and crash dmp file created 

Here's the log file
http://paste.kodi.tv/roperaqafu.sql

I'm not sure how to upload the dmp file?

Thanks

[Anonyneko]

Same problem here. Kodi (latest 12.04.2018 nightly) worked fine for a few hours, and then started crashing on boot (showing the BG and a default Windows "Kodi stopped working" message) or not even opening a window at all (happens often when using 970M). No 32-bit or 64-bit V18 works now, only reverting to V17 (I'm using V18 for plugins that specifically require it).

Intel HD 4600:
Log: http://paste.kodi.tv/enujohosen.sql
Dump: https://my.mixtape.moe/chveut.dmp

Geforce 970M:
Log: http://paste.kodi.tv/agesuxocip.sql
Dump: https://my.mixtape.moe/zeiear.dmp

[i0zjh02]

Same problem here. Kodi (latest 12.04.2018 nightly) worked fine for a few hours, and then started crashing on boot (showing the BG and a default Windows "Kodi stopped working" message) or not even opening a window at all (happens often when using 970M). No 32-bit or 64-bit V18 works now, only reverting to V17 (I'm using V18 for plugins that specifically require it).

Intel HD 4600:
Log: http://paste.kodi.tv/enujohosen.sql
Dump: https://my.mixtape.moe/chveut.dmp

Geforce 970M:
Log: http://paste.kodi.tv/agesuxocip.sql
Dump: https://my.mixtape.moe/zeiear.dmp

As mentioned in my case it works on all my clients except one (have updated 4 others without issue) The only difference is my main client is running a higher resolution (4k @ 60hz) whereas all the others are 1080p. I'll force that to 1080p later and see if that makes any difference at all
I notice in your logs that your 2 clients are also running at 4k resolution, so I wonder if thats the common theme

[komplex]

I have simliar issue with mounted iso files reprorted here.
Link

I think your one is related to his https://forum.kodi.tv/showthread.php?tid=330681

[i0zjh02]

I have simliar issue with mounted iso files reprorted here.
Link

I think your one is related to his https://forum.kodi.tv/showthread.php?tid=330681 

 Thanks, hmm I dont have any iso's mounted in my system, so not sure it its exactly the same issue

[Anonyneko]

As mentioned in my case it works on all my clients except one (have updated 4 others without issue) The only difference is my main client is running a higher resolution (4k @ 60hz) whereas all the others are 1080p. I'll force that to 1080p later and see if that makes any difference at all
I notice in your logs that your 2 clients are also running at 4k resolution, so I wonder if thats the common theme 

My screen is indeed 4k @ 60hz, but I've already tried setting it to 1080p and it didn't help. Plus, it was running quite fine for a while, but after starting it for like the third or fourth time this began to happen.

[komplex]

Thanks, hmm I dont have any iso's mounted in my system, so not sure it its exactly the same issue

I was replying to the guy i quoted

[Anonyneko]

Don't know if that helps but here's something I got from the dump (using the freshest build with pdb available) with what looks like a stack trace

http://paste.kodi.tv/qipekiwezo.makefile

Points to xbmc\guilib\guicomponent.cpp CGUIComponent::GetWindowManager perhaps dereferencing a null pointer in `return *m_pWindowManager;`, but that tells me nothing since I've never looked at Kodi code before.

[i0zjh02]

Any idea how to completely remove todays alpha version so that at least I can revert successfully to yesterdays again?

I've tried removing the "Program file..\Kodi" and the "Roaming\kodi" folders and even uninstalled the C++ library that is installed by the kodi install but still the previous daily installs (that ran quite happily until todays was installed over the top) wont run now.

I'd always assumed that I could revert to my previous version by restoring the backup of these two folders (which I back up on a daily basis). For future reference is there something else I need to backup to ensure I can always get back fully to a previous version?

I should have known it was a bad idea to install the update on Friday 13th !!

[Anonyneko]

So my problem was probably not caused by the latest nightly specifically, but by the fact that I had a few phones connected to my computer (some of them may have been also creating virtual drives with drivers and whatnot), which is another bug that seems to come up often. My particular problem is solved, fresh install and no phones. Sorry for the confusion, but the problem did look similar to me at first.

[i0zjh02]

So my problem was probably not caused by the latest nightly specifically, but by the fact that I had a few phones connected to my computer (some of them may have been also creating virtual drives with drivers and whatnot), which is another bug that seems to come up often. My particular problem is solved, fresh install and no phones. Sorry for the confusion, but the problem did look similar to me at first.

Thanks your post got me thinking. I've solved my issue too now - by removing the CD/R disk containing a user manual for an ODB diagnostics meter that I'd left in the DVD drive yesterday!! Coincidentally this is the only PC i have with an optical drive (rest are micro PCs) hence the only one effected

Once I removed this and reinstalled today's daily again it launches without problem !!!

What a way to waste a few hours, guess that's a consequence of using Alpha version :-)