+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Windows (https://forum.kodi.tv/forumdisplay.php?fid=59)
+---- Thread: Bug Exception caught on main loop. Exiting. (/showthread.php?tid=258972)
RE: Exception caught on main loop. Exiting. - afedchin - 2016-04-29
(2016-04-29, 14:51)donbrew Wrote: I believe my problem is my outdated and unsupported ATI Radeon HD4350 video card. Maybe a Windows 10 update.I've marked key sentences.
RE: Exception caught on main loop. Exiting. - donbrew - 2016-04-29
Yep, that's why I'm not particularly anxious about it.
I have now set acceleration from "auto" to "software", it has not crashed in a few hours now.
RE: Exception caught on main loop. Exiting. - scorpius.milo - 2016-04-29
(2016-04-29, 01:34)PatK Wrote: We have very similar systems... AMD 5770 HD i7.win7/64 SSD 1080p 12 gig, local storage, mostly. I'm running Jarvis 16.1 without issue, so something is different.
What version of gfx driver and version of DX11 do you have? It's possible you don't have some MS direct X path or fix.. try manually installing it https://support.microsoft.com/en-ca/kb/179113
Driver c:\windows\system32\drivers\atikmpag.sys (8.14.1.6463, 649.50 KB (665,088 bytes), 8/3/2015 9:42 PM)
Driver Version 15.200.1062.1004
Hi, and thanks for the answer
I have the same Driver : 8.14.1.6463, 649.50 KB 4/08/2015 / Driver Version 15.20.1062.1004 ( I thing you wrote 200 but it is 20 )
The Microsoft Link for DirectX 11 is installed but I have direct9c too and in my Catalyst Menu Direct3D version is 9.14.10.01128
I tried to turn DXVA2 off but Kodi still crash, the things I not understand is Kodi 16.0 ( I don't know what version is just kodi-16.0.exe ) working good for about 3weeks and since 16.1 I have this problem with both Kodi 16.0 and 16.1
My Windows7 System is the same since Kodi 15.2 no microsoft update, no directX update
My directX with dxdiag is DirectX11
At the moment a stay with Kodi 15.2
RE: Exception caught on main loop. Exiting. - donbrew - 2016-04-29
My update is: it just crashed with the error after 3-4 hours.
I had the same experience: 16.0 several RCs no problem now after 16.1 problem with both 16.0 and 16.1. Does 16.1 change some Windows system setting maybe?
RE: Exception caught on main loop. Exiting. - cubei - 2016-04-29
(2016-04-29, 20:28)donbrew Wrote: 16.0 several RCs no problem now after 16.1 problem with both 16.0 and 16.1. Does 16.1 change some Windows system setting maybe?
Since I and other people here had this problem since 16.0, I don't think 16.1 changes are related.
RE: Exception caught on main loop. Exiting. - donbrew - 2016-04-29
If I remember correctly, mine was fine with 16.0 RCs but started being funny with the 16.0 Official. My memory is getting mouldy, though.
I'm just wondering if a registry entry gets changed by the installer.
RE: Exception caught on main loop. Exiting. - cubei - 2016-04-29
(2016-04-29, 21:33)donbrew Wrote: I'm just wondering if a registry entry gets changed by the installer.
If the 16.1 installer made changes that cause this crashes, then why did I (and others) have this with 16.0?
RE: Exception caught on main loop. Exiting. - PatK - 2016-04-29
(2016-04-29, 19:08)scorpius.milo Wrote:(2016-04-29, 01:34)PatK Wrote: We have very similar systems... AMD 5770 HD i7.win7/64 SSD 1080p 12 gig, local storage, mostly. I'm running Jarvis 16.1 without issue, so something is different.
What version of gfx driver and version of DX11 do you have? It's possible you don't have some MS direct X path or fix.. try manually installing it https://support.microsoft.com/en-ca/kb/179113
Driver c:\windows\system32\drivers\atikmpag.sys (8.14.1.6463, 649.50 KB (665,088 bytes), 8/3/2015 9:42 PM)
Driver Version 15.200.1062.1004
Hi, and thanks for the answer
I have the same Driver : 8.14.1.6463, 649.50 KB 4/08/2015 / Driver Version 15.20.1062.1004 ( I thing you wrote 200 but it is 20 )
The Microsoft Link for DirectX 11 is installed but I have direct9c too and in my Catalyst Menu Direct3D version is 9.14.10.01128
I tried to turn DXVA2 off but Kodi still crash, the things I not understand is Kodi 16.0 ( I don't know what version is just kodi-16.0.exe ) working good for about 3weeks and since 16.1 I have this problem with both Kodi 16.0 and 16.1
My Windows7 System is the same since Kodi 15.2 no microsoft update, no directX update
My directX with dxdiag is DirectX11
At the moment a stay with Kodi 15.2
The driver number was cut & paste... from the sysinfo page, so we don't have the same driver then.
Catalyst version is 2015.0804.21.41908 Driver packaging version is 15.20.1062.1004-150803a1-187669C
Here's a link to the full system spec. http://xbmclogs.com/pr2qxa5s3
You may have some other issue, debug log (wiki) requested. Windows 7 must have the second update... service pack 1
RE: Exception caught on main loop. Exiting. - robert1901 - 2016-04-30
iv been having this error for days so annoying
but now its stopped suddenly and the only thing i changed was my skin i had the aeonMQ6 mod master skin on my kodi everytime i exited or shutdown with that skin i was getting this problem
when i switched to aeon NOX its not happened now for 2 days straight so weird
RE: Exception caught on main loop. Exiting. - donbrew - 2016-04-30
(2016-04-29, 21:38)cubei Wrote:(2016-04-29, 21:33)donbrew Wrote: I'm just wondering if a registry entry gets changed by the installer.
If the 16.1 installer made changes that cause this crashes, then why did I (and others) have this with 16.0?
16.0 RC1, RC2, RC3 or 16.0 Stable? My errors seemed to start with 16.0 Stable, that's why I wondered.
I am using Confluence.
RE: Exception caught on main loop. Exiting. - robert1901 - 2016-04-30
strange i tried the little test again
i exited kodi with aeon nox and it was fine
so i reentered kodi changed the skin to aeon MQ6 mod and it poped up again so in my case it must be something to do with the skin some setting is activating the error message
RE: Exception caught on main loop. Exiting. - KangarooJack - 2016-04-30
Hello guys,
i had this problem too - and it took me a very long time to track it down in my case.
Kodi always crash with "ERROR : exception caught on main loop exiting" - but only on the very first start of kodi after start/reboot of the computer.
If i close the errormessage and start kodi again it comes up without that errormessage...
It makes no different if i choose Software rendering and disable dxva2 support...
My movies are on a NAS. I map a networkdrive on the pc - and enter the network drive as location for the movies/series in kodi.
But the network connection its definitly not the problem.
I had this problem on 2 different HTPC´s with different network cables.
And i can connect to the NAS with Windows Explorer or DVBViewer without having any problem.
I have a job in the windows scheduler that starts kodi after autologin - with a manually command to map the network drive correctly and with a 30 second delay before kodi starts. Works fine, but kodi always comes up with that errormessage.
I found out that the error is gone if i deactivate the automatic update for the (movie/series) library. After disabling this feature i did about 30 tests with rebooting the machine - works fine, no more error! Standby works too. Works on both machines.
(Windows 10x64, Kodi16.1 with DVBViewer Plugin, DVBviewer 5,6,2 with RecordingService 1.32, Mainboard Asrock Q1900 with 8GB RAM, Digital Devices Cine S2 TV card)
RE: Exception caught on main loop. Exiting. - donbrew - 2016-05-01
" if i deactivate the automatic update for the (movie/series) library"
How did you do that? I don't see that option.
I don't have any network shares, I don't have any library updater addons installed. No stored videos/movies, I stream from the internets only. The only home networked thing is NextPVR for broadcast TV that I don't use much.
I don't get the error or crash at start up, it seems to be random. The other day I was taking a nap when the video stream froze but the audio continued. I had to use task manager to close Kodi. I don't know if that is related, but I'll call it a "crash". It has happened while I was not even watching anything, just adjusting the Kodi system settings.
RE: Exception caught on main loop. Exiting. - donbrew - 2016-05-01
I just installed 15.2 on a very similar machine with an identical ATI HD3450 video card and Windows 10. So far, I'm trying to remember why I upgraded to 16.0 and beyond. It runs much better! So far, no crashing no errors.
RE: Exception caught on main loop. Exiting. - PatK - 2016-05-01
(2016-05-01, 00:39)donbrew Wrote: I just installed 15.2 on a very similar machine with an identical ATI HD3450 video card and Windows 10. So far, I'm trying to remember why I upgraded to 16.0 and beyond. It runs much better! So far, no crashing no errors.+1 sounds like that gfx card has decided what's best for you
