XiboClient.exe crashing on launch with Win 10 - Resolved

We’ve been rolling out computer sticks that have been upgraded from Win 8 with Bing to Win 10 Home. Using XiboClient.exe 1.7.5, our content will play for a few days to a week on some of these devices and then, after an out of memory error in the Application Event Log, the program will no longer run.

The faulting module is KERNELBASE.dll

Steps taken to attempt to mitigate:

  • clean Xibo Library folder
  • disable CEF and Frame Buffering for the Display Settings > Windows profile
  • confirm the default.config.xml file has both of these settings (manually entered due to no launch)
  • applied all recent win 10 updates
  • applied most recent Intel HD Graphics driver updates
  • ran chkdisk
  • updated from Xibo Player 1.7.3 to 1.7.5

The only thing that seems to work is a Re-imaging of the device, in this case, an Intel Compute Stick.

Prior to becoming inoperative, we were running the display 24x7 with one web layout region that would refresh every 3 minutes. Eventually, the dreaded memory leak with, apparently, the IE embedded control, would cause a crash. During that time, double buffering was enabled.

It seems like there should be a solution for this - something has been knocked sideways on Windows 10, but I can’t tell what. Windows thinks it is all fine and happy, and we have a fresh Xibo installation.

Any ideas?

Can you also try adding the registry settings which forces the web browser control to use IE11 rendering mode (as it defaults to compatibility)?

I added

HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION

XiboClient.exe = (DWORD) 00011000

from Enabling HTML5 in the Windows .net Player and then restarted the PC, but the problem remains.

The .NET runtime error:
Application: XiboClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Management.ManagementException
at System.Management.ManagementException.ThrowWithExtendedInfo(System.Management.ManagementStatus)
at System.Management.ManagementObject.Initialize(Boolean)
at System.Management.ManagementBaseObject.get_ClassName()
at System.Management.ManagementClass.GetInstances(System.Management.EnumerationOptions)
at System.Management.ManagementClass.GetInstances()
at XiboClient.HardwareKey.GetMACAddress()
at XiboClient.HardwareKey…ctor()
at XiboClient.XiboTraceListener.InitializeListener()
at XiboClient.XiboTraceListener…ctor()
at XiboClient.Program.Main(System.String[])

The application error:
Faulting application name: XiboClient.exe, version:, time stamp: 0x5620b816
Faulting module name: KERNELBASE.dll, version: 10.0.10586.0, time stamp: 0x5632d1bc
Exception code: 0xe0434352
Fault offset: 0x000d2ed2
Faulting process id: 0x14f0
Faulting application start time: 0x01d137452e8cc4fc
Faulting application path: C:\Program Files\Xibo Player\XiboClient.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 8c425070-1a3c-43cd-8cba-ff5f7e1a5042
Faulting package full name:
Faulting package-relative application ID:

Is the problem with the GetMACAddress call?

This is occurring on a second device as well, this one only in service for a day. It seems like it started after the system was rebooted and a slew of WMI errors occurred. Most but not all were a flavor of

Error 0x80041006 encountered when trying to load MOF C:\WINDOWS\SYSTEM32\EN-US\PSMODULEDISCOVERYPROVIDER.MFL while recovering .MOF file marked with autorecover.

Something bad seems to have happened. This technote for Windows Server 2008 seems applicable:

This seems to be the money here: "Note: If the problem MOF file is CIMWIN32.MOF, most WMI functionality will be impaired. "

Running c:\windows\system32\wbem> mofcomp cimwin32.mof resolved the problem. Do this via CMD running as Administrator.

Great, we are glad that you were able to find what was causing this problem and fix it! :smile:

This topic was automatically closed 2 hours after the last reply. New replies are no longer allowed.

The Xibo Community site uses cookies. What are cookies?