+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Skins Support (https://forum.kodi.tv/forumdisplay.php?fid=67)
+---- Forum: Aeon MQ (https://forum.kodi.tv/forumdisplay.php?fid=68)
+---- Thread: [MOD] Aeon65 1.0 (based on Hitched Mod) (/showthread.php?tid=55600)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
- MoldySpore - 2010-01-19
Has been happening on several different systems since I updated to this version of Aeon and latest build.
Memory is solid checked with memtest.
Cpu is not overclocked, Phenom II X4 955 @ 3.2Ghz running @ 29 C idle 38 under load. around 32 in xbmc. Safe temp is 65 C or so for this proc
Videocard drivers up to date, running XFX GeForce 260 GTX @ 1920 x 1080p.
Everything runs fine. If I switch back to old Auriga or Stark build, runs fine no issues. Same with default skin on latest build 26973.
This happens on another machine with similar specs, different processor and motherboard. Also an old AMD Athlon 64 X2 machine I have has the same problems. Completely different chipset in that one.
I don't think this is a hardware issue. This seems to be a really nice build of Aeon. Very complete and polished. I'd hate for me, and potentially others, to miss out cause of this. I don't think I've had a single BSOD on my quad box detailed above since it was built 6 months ago. Just seems odd that this specific build and skin and running and I start having issues. I just want to be able to use the sweet skin Phil has made.
- stoli - 2010-01-19
@MoldySpore - have you deleted the guisettings.xml and started fresh?
- MoldySpore - 2010-01-19
stoli Wrote:@MoldySpore - have you deleted the guisettings.xml and started fresh?
I have been using a fresh copy of the latest version of XBMC, with the most recent version of Aeon65 loaded on top of it. In fact, 2 hours ago, I uninstalled and cleaned out XBMC (including any profile information stored in app data\xbmc) and reinstalled it with the newest revision and started rescanning all my content. I am getting the same BSODs, and I haven't even customized anything yet like backdrops and shortcuts. Just started scanning stuff in immediately and went to play something at the same time. Only took a few minutes and it BSOD'd. Myself I've gotten at least a dozen or 2 of the same BSOD since first installing this skin last night on my main HTPC/Media PC. Since then I've confirmed it on several more of my own, as well as with 2 other people who run XBMC and Aeon in a setup similar to mine (PC is connected to HDTV and used as a media center/gaming machine).
1 of the systems I confirmed this issue on has a fresh copy of Windows XP Pro SP3 on it as well. That's the only reason I bothered posting about it, since I have been able to reproduce the same BSOD on multiple machines. All the machines in question have minimal apps installed because most act as some kind of media center or hub. XBMC is one of maybe a half-dozen apps installed on most aside from drivers. The only common element between them is that in all cases they are using an ASUS motherboard. Beyond there, the similarities stop in terms of hardware, because even the motherboard are totally different in terms of revision, hardware support, and in some cases even have a completely different chipset altogether (NVIDIA vs. AMD)
After updating the 26973 the GUI menu and the crashing issues seemed to have gone away, but now there seems to be a new issue. If XBMC is left running with this skin enabled, it eventually begins performing poorly. HD content playback becomes jumpy (video speeds up a bit, then slows, over and over. Audio is unaffected). The BSOD's aren't stopping either. They seem to exclusively happen when multi-tasking inside XBMC (Watching + browsing library or scanning new content +browsing library or scanning new content + watching something). Something will be playing, and I'll start scrolling through episodes of a show and itll freeze for a split second, then itll give me a BSOD. Always the same one (DRIVER_IRQL_NOT_LESS_OR_EQUAL) which unfortunately is very unspecific in terms of what could be at fault. Reverting back to 26880 stops the slow/fast video issue and just goes back to the menu errors. Again, I have no issues switching back to Auriga or Stark, especially on an earlier build of XBMC.
I've kinda hit a wall in terms of what I can do differently to try and remedy these issues. I appreciate anyone's 2 cents on this stuff, as I would really like to switch over to Aeon65 as my main skin, but right now it's looking like a switch back to Auriga might be in my and a few other's future.
- phil65 - 2010-01-19
MoldySpore Wrote:I have been using a fresh copy of the latest version of XBMC, with the most recent version of Aeon65 loaded on top of it. In fact, 2 hours ago, I uninstalled and cleaned out XBMC (including any profile information stored in app data\xbmc) and reinstalled it with the newest revision and started rescanning all my content. I am getting the same BSODs, and I haven't even customized anything yet like backdrops and shortcuts. Just started scanning stuff in immediately and went to play something at the same time. Only took a few minutes and it BSOD'd. Myself I've gotten at least a dozen or 2 of the same BSOD since first installing this skin last night on my main HTPC/Media PC. Since then I've confirmed it on several more of my own, as well as with 2 other people who run XBMC and Aeon in a setup similar to mine (PC is connected to HDTV and used as a media center/gaming machine).
1 of the systems I confirmed this issue on has a fresh copy of Windows XP Pro SP3 on it as well. That's the only reason I bothered posting about it, since I have been able to reproduce the same BSOD on multiple machines. All the machines in question have minimal apps installed because most act as some kind of media center or hub. XBMC is one of maybe a half-dozen apps installed on most aside from drivers. The only common element between them is that in all cases they are using an ASUS motherboard. Beyond there, the similarities stop in terms of hardware, because even the motherboard are totally different in terms of revision, hardware support, and in some cases even have a completely different chipset altogether (NVIDIA vs. AMD)
After updating the 26973 the GUI menu and the crashing issues seemed to have gone away, but now there seems to be a new issue. If XBMC is left running with this skin enabled, it eventually begins performing poorly. HD content playback becomes jumpy (video speeds up a bit, then slows, over and over. Audio is unaffected). The BSOD's aren't stopping either. They seem to exclusively happen when multi-tasking inside XBMC (Watching + browsing library or scanning new content +browsing library or scanning new content + watching something). Something will be playing, and I'll start scrolling through episodes of a show and itll freeze for a split second, then itll give me a BSOD. Always the same one (DRIVER_IRQL_NOT_LESS_OR_EQUAL) which unfortunately is very unspecific in terms of what could be at fault. Reverting back to 26880 stops the slow/fast video issue and just goes back to the menu errors. Again, I have no issues switching back to Auriga or Stark, especially on an earlier build of XBMC.
I've kinda hit a wall in terms of what I can do differently to try and remedy these issues. I appreciate anyone's 2 cents on this stuff, as I would really like to switch over to Aeon65 as my main skin, but right now it's looking like a switch back to Auriga might be in my and a few other's future.
Does the debug log show anything? I don´t believe this is skin-related since you´re the only one till now who has these problems. Did you try older SVN builds?
- MoldySpore - 2010-01-19
phil65 Wrote:Does the debug log show anything? I don´t believe this is skin-related since you´re the only one till now who has these problems. Did you try older SVN builds?
Right, until now. But I'm saying not only have I confirmed it on several of my own systems, but friends of mine have been having the same exact issue. Even my girlfriend is having this issue. I loaded the latest version of this skin and XBMC on her machine for her last night. She called me today saying she was getting BSOD's. She has uninstalled and reinstalled several times now with the same results.
As for the logs...the end of the log, right before any crash. Here is from a crash that happened 2 hours ago:
18:44:00 T:3748 M:2808221696 WARNING: Skin has invalid include: textcolorwhite
18:44:00 T:3748 M:2808213504 WARNING: Skin has invalid include: textcolorwhite
18:44:01 T:4044 M:2829967360 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:01 T:4044 M:2830585856 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:02 T:4044 M:2831589376 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:05 T:4044 M:2835038208 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:05 T:2032 M:2835038208 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
18:44:09 T:4044 M:2834890752 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:10 T:4044 M:2833760256 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:11 T:4044 M:2833211392 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:11 T:4044 M:2834034688 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:17 T:4044 M:2833260544 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:44:29 T:4044 M:2832531456 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:45:00 T:4044 M:2833551360 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:45:00 T:4044 M:2832875520 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:45:02 T:4044 M:2833281024 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED18:45:03 T:4044 M:2833145856 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZEDand here is from a BSOD that happened not even 30 mins ago:
23:00:44 T:828 M:2790744064 WARNING: Skin has invalid include: textcolorwhite
23:00:44 T:828 M:2790727680 WARNING: Skin has invalid include: textcolorwhite
23:00:51 T:1336 M:2801377280 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED23:00:55 T:2380 M:2794004480 WARNING: CDVDVideoCodecFFmpeg:
ecode - avcodec_decode_video didn't consume the full packet. size: 12145, consumed: 023:00:57 T:2380 M:2791673856 WARNING: CDVDVideoCodecFFmpeg:
ecode - avcodec_decode_video didn't consume the full packet. size: 14434, consumed: 023:00:57 T:2380 M:2791673856 WARNING: CDVDVideoCodecFFmpeg:
ecode - avcodec_decode_video didn't consume the full packet. size: 13526, consumed: 023:00:58 T:2380 M:2794094592 WARNING: CDVDVideoCodecFFmpeg:
ecode - avcodec_decode_video didn't consume the full packet. size: 12414, consumed: 023:01:01 T:1336 M:2797355008 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED23:01:02 T:2312 M:2795634688 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
23:01:03 T:1336 M:2792837120 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZEDEdit: Just happened again. Seems this "Put MSGQ_NOT_INITIALIZED" is the common message rigtht before the BSOD in most cases. Not sure if that means anything...
02:04:24 T:1552 M:2766024704 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:25 T:1552 M:2770407424 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:29 T:1552 M:2769620992 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:30 T:1552 M:2769375232 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:31 T:1552 M:2769121280 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:32 T:1552 M:2768371712 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:46 T:1552 M:2770235392 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:49 T:1552 M:2769534976 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:50 T:1552 M:2768953344 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:51 T:1552 M:2768625664 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:52 T:1552 M:2768166912 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:52 T:1552 M:2768125952 WARNING: CDVDPlayer::CheckContinuity - wrapback of stream:1, prev:357196000.000000, curr:357193312.500000, diff:-2687.500000
02:04:52 T:1552 M:2767716352 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:53 T:1552 M:2767192064 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:53 T:1552 M:2767917056 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:54 T:1552 M:2767433728 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:55 T:1552 M:2766950400 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:55 T:1552 M:2766491648 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:56 T:1552 M:2766090240 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:56 T:1552 M:2765836288 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:57 T:1552 M:2765426688 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:04:59 T:1552 M:2764808192 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:05:01 T:1552 M:2764050432 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZED02:05:03 T:1552 M:2763780096 WARNING: CDVDMessageQueue(teletext):
ut MSGQ_NOT_INITIALIZEDAgain, I appreciate your time.
- sialivi - 2010-01-19
MoldySpore,
Have you checked which driver the crash occur in? Try runningWhoCrashed if you don't know how to do it manually with mircrosofts debug tools.
- phil65 - 2010-01-19
MoldySpore Wrote:Right, until now. But I'm saying not only have I confirmed it on several of my own systems, but friends of mine have been having the same exact issue. Even my girlfriend is having this issue. I loaded the latest version of this skin and XBMC on her machine for her last night. She called me today saying she was getting BSOD's. She has uninstalled and reinstalled several times now with the same results.
As for the logs...the end of the log, right before any crash. Here is from a crash that happened 2 hours ago:
18:44:00 T:3748 M:2808221696 WARNING: Skin has invalid include: textcolorwhite
18:44:00 T:3748 M:2808213504 WARNING: Skin has invalid include: textcolorwhite
18:44:01 T:4044 M:2829967360 WARNING: CDVDMessageQueue(teletext):
18:44:01 T:4044 M:2830585856 WARNING: CDVDMessageQueue(teletext):
18:44:02 T:4044 M:2831589376 WARNING: CDVDMessageQueue(teletext):
18:44:05 T:4044 M:2835038208 WARNING: CDVDMessageQueue(teletext):
18:44:05 T:2032 M:2835038208 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
18:44:09 T:4044 M:2834890752 WARNING: CDVDMessageQueue(teletext):
18:44:10 T:4044 M:2833760256 WARNING: CDVDMessageQueue(teletext):
18:44:11 T:4044 M:2833211392 WARNING: CDVDMessageQueue(teletext):
18:44:11 T:4044 M:2834034688 WARNING: CDVDMessageQueue(teletext):
18:44:17 T:4044 M:2833260544 WARNING: CDVDMessageQueue(teletext):
18:44:29 T:4044 M:2832531456 WARNING: CDVDMessageQueue(teletext):
18:45:00 T:4044 M:2833551360 WARNING: CDVDMessageQueue(teletext):
18:45:00 T:4044 M:2832875520 WARNING: CDVDMessageQueue(teletext):
18:45:02 T:4044 M:2833281024 WARNING: CDVDMessageQueue(teletext):
18:45:03 T:4044 M:2833145856 WARNING: CDVDMessageQueue(teletext):
and here is from a BSOD that happened not even 30 mins ago:
23:00:44 T:828 M:2790744064 WARNING: Skin has invalid include: textcolorwhite
23:00:44 T:828 M:2790727680 WARNING: Skin has invalid include: textcolorwhite
23:00:51 T:1336 M:2801377280 WARNING: CDVDMessageQueue(teletext):
23:00:55 T:2380 M:2794004480 WARNING: CDVDVideoCodecFFmpeg:
23:00:57 T:2380 M:2791673856 WARNING: CDVDVideoCodecFFmpeg:
23:00:57 T:2380 M:2791673856 WARNING: CDVDVideoCodecFFmpeg:
23:00:58 T:2380 M:2794094592 WARNING: CDVDVideoCodecFFmpeg:
23:01:01 T:1336 M:2797355008 WARNING: CDVDMessageQueue(teletext):
23:01:02 T:2312 M:2795634688 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
23:01:03 T:1336 M:2792837120 WARNING: CDVDMessageQueue(teletext):
Edit: Just happened again. Seems this "Put MSGQ_NOT_INITIALIZED" is the common message rigtht before the BSOD in most cases. Not sure if that means anything...
02:04:24 T:1552 M:2766024704 WARNING: CDVDMessageQueue(teletext):
02:04:25 T:1552 M:2770407424 WARNING: CDVDMessageQueue(teletext):
02:04:29 T:1552 M:2769620992 WARNING: CDVDMessageQueue(teletext):
02:04:30 T:1552 M:2769375232 WARNING: CDVDMessageQueue(teletext):
02:04:31 T:1552 M:2769121280 WARNING: CDVDMessageQueue(teletext):
02:04:32 T:1552 M:2768371712 WARNING: CDVDMessageQueue(teletext):
02:04:46 T:1552 M:2770235392 WARNING: CDVDMessageQueue(teletext):
02:04:49 T:1552 M:2769534976 WARNING: CDVDMessageQueue(teletext):
02:04:50 T:1552 M:2768953344 WARNING: CDVDMessageQueue(teletext):
02:04:51 T:1552 M:2768625664 WARNING: CDVDMessageQueue(teletext):
02:04:52 T:1552 M:2768166912 WARNING: CDVDMessageQueue(teletext):
02:04:52 T:1552 M:2768125952 WARNING: CDVDPlayer::CheckContinuity - wrapback of stream:1, prev:357196000.000000, curr:357193312.500000, diff:-2687.500000
02:04:52 T:1552 M:2767716352 WARNING: CDVDMessageQueue(teletext):
02:04:53 T:1552 M:2767192064 WARNING: CDVDMessageQueue(teletext):
02:04:53 T:1552 M:2767917056 WARNING: CDVDMessageQueue(teletext):
02:04:54 T:1552 M:2767433728 WARNING: CDVDMessageQueue(teletext):
02:04:55 T:1552 M:2766950400 WARNING: CDVDMessageQueue(teletext):
02:04:55 T:1552 M:2766491648 WARNING: CDVDMessageQueue(teletext):
02:04:56 T:1552 M:2766090240 WARNING: CDVDMessageQueue(teletext):
02:04:56 T:1552 M:2765836288 WARNING: CDVDMessageQueue(teletext):
02:04:57 T:1552 M:2765426688 WARNING: CDVDMessageQueue(teletext):
02:04:59 T:1552 M:2764808192 WARNING: CDVDMessageQueue(teletext):
02:05:01 T:1552 M:2764050432 WARNING: CDVDMessageQueue(teletext):
02:05:03 T:1552 M:2763780096 WARNING: CDVDMessageQueue(teletext):
Again, I appreciate your time.
Hmm, perhaps it would be best to post that in the general xbmc for windows forum.
- tetodbs - 2010-01-19
Hi, I'm new and I'm trying to translate your skin in italian.
I'm at 99% because I cant find the english strings to translate indicated in the attacched images.
Could you please give me that strings for finishing the translation?
When I'll finish it, if you want, I'll send you it.
Thanks and excuse me for my poor english.
Teto
- tetodbs - 2010-01-19
... and the last image:
- Batemann - 2010-01-19
HI! I'm SO glad Aeon is back! More stable than ever. Glad to see development back up again.
Found on VERY small thing. :-)
In showcase view in the seasons screen, on the info panel, the fanart is displayed twice.
Ow, when I think of it, I use the Cinema Xperience script a lot. Aeon has the button for it in the info screen. When I use it: I select a movie, press info, press the "cinema" button and then the scripts kicks in. But it doesn't start the movie I selected. It starts the movie next to it. I dunno if it is an Aeon thing, but I think it is...
- phil65 - 2010-01-19
tetodbs Wrote:... and the last image:
thx, will change them to be customisable.
- MoldySpore - 2010-01-19
sialivi Wrote:MoldySpore,
Have you checked which driver the crash occur in? Try runningWhoCrashed if you don't know how to do it manually with mircrosofts debug tools.
As I stated, I am getting a BSOD:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
This BSOD is commonly caused by faulty hardware or by a software conflict. Sounds vague? That's cause it is. The DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD is a very general BSOD that can mean a lot of different things. And since I am reproducing this on multiple machines, hardware issue seems much less likely.
- MoldySpore - 2010-01-19
phil65 Wrote:Hmm, perhaps it would be best to post that in the general xbmc for windows forum.
Really? I am not sure it is an XBMC issue, as I can use many other skins without incident. But with this skin, I get BSOD eventually every time. It is ONLY with this skin enabled that I have issues.
- SteveZissou - 2010-01-20
phil65 Wrote:yes, an icon for subtitles is possible. would look at it perhaps if someone´s got a fitting icon for that.
hi,
here is a first go at an icon for subtitle indication which would really come in handy for tv series: subs_white
I only did it in white and reused the closed captioning one. could you indicate me the font for the text used in the other icons as well as where the black icons are located so I can refine this
thx -steve
- stoli - 2010-01-20
MoldySpore Wrote:As I stated, I am getting a BSOD:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
This BSOD is commonly caused by faulty hardware or by a software conflict. Sounds vague? That's cause it is. The DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD is a very general BSOD that can mean a lot of different things. And since I am reproducing this on multiple machines, hardware issue seems much less likely.
MoldySpore Wrote:Really? I am not sure it is an XBMC issue, as I can use many other skins without incident. But with this skin, I get BSOD eventually every time. It is ONLY with this skin enabled that I have issues.
Ok, and everyone has been trying to help you. It was suggested you use a tool that will tell you specifically what driver/app is crashing/causing conflict. What was the result? You've mentioned "friends" having the same crash, yet in 100,000 reads of this thread and over 1,000 posts, you are the only one mentioning a BSOD. It's an issue vs. problem management; 1 out of 1,000 is an issue for you and not a problem for anyone.
The idea of taking the debug log to a general windows xbmc forum may well be helpful. It certainly can't hurt at this point. If your logs show the same error each time the crash occurs, some dev may be able to steer you in the right direction.
Also (I may have missed it), where is a complete debug log?