Kodi BSOD

TerraHawk · 10 Mar 2015

Hi guys got a problem.
Please help.

Thanks in advance!
TerraHawk

usasma · 10 Mar 2015

You state that this is a Kodi BSOD - does it only occur when using Kodi?
The BSOD's seem to point to video problems.

From a search of the Kodi website, wiki, and forums - there doesn't seem to be much (if any) testing on Windows 10.
I did see previous BSOD issues when using the Kodi webserver.
Also, most of the releases seem to be beta versions - so you're using a beta player on a beta OS. IMO that's not a good recipe for a stable platform.

Ensure that you have ALL available Windows Updates.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD
(in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Please uninstall PowerDVD as it's driver dates from 2011 (ntk_PowerDVD12_64.sys).
Please uninstall Cyberlink software - as the 000.fcl driver dates from 2008 (also the CLBStor.sys and CLBUDF.SYS drivers date from 2008).

You may also want to remove the Gigabyte On/Off Charger (AppleCharger.sys) as it previously had BSOD issues (though I haven't seen any from it in a long time).

We have seen BSOD problems with older drivers for the USB modem (tap0901.sys) in Windows 8/8.1. I'd suggest physically removing the device and uninstalling it's software in order to test this.

I'd also update your bluetooth drivers. Older bluetooth drivers (from Win8) caused BSOD issues in Win8.1 Your drivers date from 17 Oct 2013 (the date that Win8.1 was released), so they may/may not be compatible.

Finally, I'd continue to update your video drivers. AMD states that Win10 specific drivers aren't needed - but it can't hurt to update to the latest version in case bug fixes have been released.

Analysis:
The following is for informational purposes only.

Code:

**************************Mon Mar  9 15:18:07.096 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\030915-17203-01.dmp]
Windows 8 Kernel Version 9926 MP (2 procs) Free x64
Built by: 9926.0.amd64fre.fbl_awesome1501.150119-1648
System Uptime:0 days 0:13:34.795
*** WARNING: Unable to verify timestamp for dxgmms2.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms2.sys
Probably caused by :dxgmms2.sys ( dxgmms2+3e215 )
BugCheck 10E, {33, ffffc000cfe83160, 75000, 0}
BugCheck Info: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
Arguments: 
Arg1: 0000000000000033, The subtype of the bugcheck:
Arg2: ffffc000cfe83160
Arg3: 0000000000075000
Arg4: 0000000000000000
BUGCHECK_STR:  0x10e_33
PROCESS_NAME:  Kodi.exe
FAILURE_BUCKET_ID: 0x10e_33_dxgmms2+3e215
  BIOS Version                  F6
  BIOS Release Date             05/28/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Mar  7 15:36:15.070 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\030715-16968-01.dmp]
Windows 8 Kernel Version 9926 MP (2 procs) Free x64
Built by: 9926.0.amd64fre.fbl_awesome1501.150119-1648
System Uptime:0 days 7:09:36.767
*** WARNING: Unable to verify timestamp for dxgmms2.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms2.sys
Probably caused by :dxgmms2.sys ( dxgmms2+3e215 )
BugCheck 10E, {33, ffffc001ee6caa70, 75000, 0}
BugCheck Info: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
Arguments: 
Arg1: 0000000000000033, The subtype of the bugcheck:
Arg2: ffffc001ee6caa70
Arg3: 0000000000075000
Arg4: 0000000000000000
BUGCHECK_STR:  0x10e_33
PROCESS_NAME:  Kodi.exe
FAILURE_BUCKET_ID: 0x10e_33_dxgmms2+3e215
  BIOS Version                  F6
  BIOS Release Date             05/28/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Mar  7 08:26:05.950 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\030715-14218-01.dmp]
Windows 8 Kernel Version 9926 MP (2 procs) Free x64
Built by: 9926.0.amd64fre.fbl_awesome1501.150119-1648
System Uptime:0 days 0:46:57.649
*** WARNING: Unable to verify timestamp for dxgmms2.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms2.sys
Probably caused by :dxgmms2.sys ( dxgmms2+3e215 )
BugCheck 10E, {33, ffffc000d96d5ae0, 6c000, 0}
BugCheck Info: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
Arguments: 
Arg1: 0000000000000033, The subtype of the bugcheck:
Arg2: ffffc000d96d5ae0
Arg3: 000000000006c000
Arg4: 0000000000000000
BUGCHECK_STR:  0x10e_33
PROCESS_NAME:  Kodi.exe
FAILURE_BUCKET_ID: 0x10e_33_dxgmms2+3e215
  BIOS Version                  F6
  BIOS Release Date             05/28/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar  6 18:39:06.032 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\030615-14062-01.dmp]
Windows 8 Kernel Version 9926 MP (2 procs) Free x64
Built by: 9926.0.amd64fre.fbl_awesome1501.150119-1648
System Uptime:0 days 15:35:06.729
*** WARNING: Unable to verify timestamp for dxgmms2.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms2.sys
Probably caused by :dxgmms2.sys ( dxgmms2+3e215 )
BugCheck 10E, {33, ffffc000e3bd1b40, 159000, 0}
BugCheck Info: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
Arguments: 
Arg1: 0000000000000033, The subtype of the bugcheck:
Arg2: ffffc000e3bd1b40
Arg3: 0000000000159000
Arg4: 0000000000000000
BUGCHECK_STR:  0x10e_33
PROCESS_NAME:  Kodi.exe
FAILURE_BUCKET_ID: 0x10e_33_dxgmms2+3e215
  BIOS Version                  F6
  BIOS Release Date             05/28/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  3 20:07:38.218 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\030415-16203-01.dmp]
Windows 8 Kernel Version 9926 MP (2 procs) Free x64
Built by: 9926.0.amd64fre.fbl_awesome1501.150119-1648
System Uptime:0 days 8:59:22.916
Probably caused by :dxgmms2.sys ( dxgmms2!VidMmInterface+371c6 )
BugCheck 3B, {c0000005, fffff80068bd32e6, ffffd001a46222e0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80068bd32e6, Address of the instruction which caused the bugcheck
Arg3: ffffd001a46222e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: 0x3B_dxgmms2!VidMmInterface
  BIOS Version                  F6
  BIOS Release Date             05/28/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             F2A88XM-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

**************************Mon Mar  9 15:18:07.096 2015 (UTC - 4:00)**************************
000.fcl                     Fri Sep 26 09:11:22 2008 (48DCDF7A)
CLBUDF.SYS                  Wed Dec 31 05:02:30 2008 (495B4336)
CLBStor.sys                 Wed Dec 31 05:02:34 2008 (495B433A)
ntk_PowerDVD12_64.sys       Thu May 12 08:30:24 2011 (4DCBD2E0)
Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
bcbtums.sys                 Thu Oct 17 16:45:30 2013 (52604C6A)
AppleCharger.sys            Sun Oct 27 21:59:21 2013 (526DC4F9)
amd_sata.sys                Wed Nov  6 01:10:20 2013 (5279DD4C)
amd_xata.sys                Wed Nov  6 01:10:23 2013 (5279DD4F)
AODDriver2.sys              Tue Feb 11 06:06:52 2014 (52FA044C)
AMDACPKSL.SYS               Sat Jun 21 22:31:43 2014 (53A6400F)
AtihdWB6.sys                Sat Jun 21 22:32:00 2014 (53A64020)
appexDrv.sys                Mon Oct 13 01:43:47 2014 (543B6693)
amdacpksd.sys               Thu Nov 20 21:18:16 2014 (546EA0E8)
RTKVHD64.sys                Fri Feb  6 04:47:44 2015 (54D48DC0)
atikmpag.sys                Fri Feb  6 16:51:29 2015 (54D53761)
atikmdag.sys                Fri Feb  6 17:14:59 2015 (54D53CE3)

usasma · 10 Mar 2015

PS - you may want to test your video card (on the off chance that it may be a hardware/video memory problem).
Try these free diagnostics: Hardware Diagnostics