2016-09-30, 02:05
The paste was short "ERROR: DXGI_ERROR_DEVICE_REMOVED" but indicated a direct X issue which usually points back at the graphics. Looking a little deeper and came up with http://www.notebookcheck.net/ATI-Radeon-...775.0.html and I'm surprised that "had no issues on windows 7 running Kodi 16.1 Jarvis" and would have said 'if it's not broke don't fix it'. But I guess we can't put the gene back in the bottle.
At this point I'm wondering if a bog stock Kodi 16.1 install on a USB stick and run in portable mode would fly? http://kodi.wiki/view/Windows_FAQ#Portable Bascially all you need to do is have a spare USB stick with ~4 gigs, when it asks you to install to a different place, pick the USB, but don't run it.. In the shortcut's properties there will be a box called Target field, add the switch -p after kodi.exe i.e. P:\Kodi\kodi.exe -p
At this point I'm wondering if a bog stock Kodi 16.1 install on a USB stick and run in portable mode would fly? http://kodi.wiki/view/Windows_FAQ#Portable Bascially all you need to do is have a spare USB stick with ~4 gigs, when it asks you to install to a different place, pick the USB, but don't run it.. In the shortcut's properties there will be a box called Target field, add the switch -p after kodi.exe i.e. P:\Kodi\kodi.exe -p
and created the kodi.exe in task bar and went to properties ect. ect I then ran kodi as administrator and just regular from portable Gig stick and received the same as always, so I assume I am back to square one with dealing with GPX/DirectX/ graphics ect. UUHHGG Been looking at maybe trying to re clock GPU in which I find in googling the DXGI Error.
Just curious