MCE Buddy 2.13.12 was working OK on my system but then I disabled it, along with a bunch of other stuff, to diagnose my slow boot times. Now, when I try and start it I get these errors:
Application: MCEBuddy.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEECD9D08D (000007FEECD90000) with exit code 80131506.
Faulting application name: MCEBuddy.Service.exe, version: 2.3.12.1, time stamp: 0x51620371
Faulting module name: clr.dll, version: 4.0.30319.1008, time stamp: 0x517a18ff
Exception code: 0xc0000005
Fault offset: 0x000000000000d08d
Faulting process id: 0x1210
Faulting application start time: 0x01ce8e21a5aae212
Faulting application path: C:\Program Files\MCEBuddy2x\MCEBuddy.Service.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: e4c6a25b-fa14-11e2-91ce-bc5ff40da1b3
I also just fixed a problem with Windows\Fonts which was causing BSOD, as described here but I doubt that's related to MCEBuddy problem https://support.mozilla.org/en-US/questions/674779
Comments: ** Comment from web user: doveman **
Application: MCEBuddy.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEECD9D08D (000007FEECD90000) with exit code 80131506.
Faulting application name: MCEBuddy.Service.exe, version: 2.3.12.1, time stamp: 0x51620371
Faulting module name: clr.dll, version: 4.0.30319.1008, time stamp: 0x517a18ff
Exception code: 0xc0000005
Fault offset: 0x000000000000d08d
Faulting process id: 0x1210
Faulting application start time: 0x01ce8e21a5aae212
Faulting application path: C:\Program Files\MCEBuddy2x\MCEBuddy.Service.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: e4c6a25b-fa14-11e2-91ce-bc5ff40da1b3
I also just fixed a problem with Windows\Fonts which was causing BSOD, as described here but I doubt that's related to MCEBuddy problem https://support.mozilla.org/en-US/questions/674779
Comments: ** Comment from web user: doveman **
Thanks. I ran this installer and did a repair and rebooted but I'm still getting the same errors
http://www.microsoft.com/en-us/download/details.aspx?id=17851
I'd already done a sfc /scannow and chkdsk C: /F /R and they didn't show any problems, so if there's no way to check for problems and we just have to wait until a program uses each file before it tells us it's corrupt, it makes it rather hard to test a system for problems.