Posts: 8
Joined: Nov 2017
Reputation:
0
Hi,
after trying to update my KODi Alpha "Leia" (x64-version) yesterday to a newer build, I had to realize that obviously all newer builds since beginning of February are not working. The Program starts with a dark blue screen and then closes immediately. First I thought that this would maybe coursed by the use of the old skin "Confluence" - though Confluence runs without any problems with Leia - but this is not the reason. Also the actual skin "Estuary" doesn't work. Whatever happened in the development of KODI V18 - it must have been between February 1st (still working) and February 7th (not working). My system: Windows 10 Pro (Insider Preview) Development Build 17074.1000 (x64).
Posts: 8
Joined: Nov 2017
Reputation:
0
If there would be no driver, I wouldn't see anything on my monitor. By the way, in my AppData-Folder there is also a file called "kodi_crashlog-18.0-ALPHA1 Git_20180225-e871d73db8-20180226-180325.dmp". Would be this helpfull? But than I would need an Emailadress to send it to your team.
Posts: 13,684
Joined: Mar 2010
Reputation:
507
PatK
Team-Kodi Member
Posts: 13,684
Although your MS driver is sufficient for windows, it's not enough for Kodi to launch. If there is a hardware specific driver available, by all means, install that. A Crash log is useful to a developer, and you would be provided with instructions; but in this case, it's obviously a video driver issue. Suggestion, revert to a Kodi iteration that does work for your set-up until we have ironed out the new Alpha and as suggested a portable install will make experimentation so much easier.
Posts: 8
Joined: Nov 2017
Reputation:
0
By the way, there is a problem with my graphics. H265-codec is not supported by my graphics, the only way to play this is using the new VLC 3.0. The new VLC plays those videos inside the player.
But this means that the developers of KODI changed someting in the recent past to adress the graphics. Though I am using the insider preview of Windows 10, there was no new version since the beginning of february. The change must have been in KODI.
Posts: 8
Joined: Nov 2017
Reputation:
0
There is no way to get another driver for Windows 10. Because both graphic vendors - NVIDIA and AMD - don't make own drivers available on their websites since Windows 8, those are only delivered with windows update. And Windows of course says that my driver is actual.
Posts: 8
Joined: Nov 2017
Reputation:
0
I have installed the actual version of catalyst control center (AMD graphics). After setup and trying to update the Windows device manager shows still the old details: Date of driver Aug.08, 2015, version 15.200.1062.1004, signature Microsoft Windows Hardware Compatibility.
Posts: 8
Joined: Nov 2017
Reputation:
0
I suppose following: I am working with a build which is fine, although it is not the newest one. Because the elder builds are working and the newer not - which is still a little bit strange to me - I will wait until perhaps there is another future build working with my windows. I am expecting a new Windows 10 insider preview build coming soon, perhaps this solves the problem.
Posts: 10,530
Joined: Oct 2011
Reputation:
640
jjd-uk
Team-Kodi Member
Posts: 10,530
Perhaps you should consider not running Windows 10 Preview builds on 5 year old hardware, as that could be a cause of the issue.
Posts: 8
Joined: Nov 2017
Reputation:
0
No, my hardware is not so old - 3 1/4 years. But the problem has solved. I just installed the new Alpha1 - and this build is running perfect.
Posts: 10,530
Joined: Oct 2011
Reputation:
640
jjd-uk
Team-Kodi Member
Posts: 10,530
What I meant before was that running alpha software on a beta OS version with hardware that no longer gets driver updates may increase the risk of a problem being encountered, anyway it's great it got sorted for you by a newer Kodi build.
