Hi,
My other half said she was scrolling down the G-EPG (using arrow key) and box BSOD.
My setup....
VU Solo2 using fresh usb install of Hades 010 (with no restore of settings). Fixed dish at 28.2 using ABM (custom area selected), and CrossEPG/OpenTV with EPG data stored on internal HDD.
Attached is the crash log
View attachment enigma2_crash_1432385086.txt
Trying to decipher the log few things stood out so hoping if someone could confirm if these are things to look into further...
Could anyone of these be reason for the BSOD or maybe something else in the log that I didn't notice!
Thanks in advance.
My other half said she was scrolling down the G-EPG (using arrow key) and box BSOD.
My setup....
VU Solo2 using fresh usb install of Hades 010 (with no restore of settings). Fixed dish at 28.2 using ABM (custom area selected), and CrossEPG/OpenTV with EPG data stored on internal HDD.
Attached is the crash log
View attachment enigma2_crash_1432385086.txt
Trying to decipher the log few things stood out so hoping if someone could confirm if these are things to look into further...
- A few missing skin elements
- <143067.456337> [gAccel] alloc failed
- <143067.456414> [gSurface] ERROR: accelAlloc failed
- Traceback (most recent call last):
File "/usr/lib/enigma2/python/Components/EpgList.py", line 395, in serviceChanged
File "/usr/lib/enigma2/python/Components/EpgList.py", line 404, in findBestEvent - IndexError: list index out of range
- <143951.273764> [ePyObject] (CallObject(<bound method EPGList.serviceChanged of <Components.EpgList.EPGList object at 0x6286a110>>,()) failed)
Could anyone of these be reason for the BSOD or maybe something else in the log that I didn't notice!
Thanks in advance.
