eMClient crashes after starting

Problem signature:  Problem Event Name: APPCRASH
  Application Name: MailClient.exe
  Application Version: 6.0.22625.0
  Application Timestamp: 5575a926
  Fault Module Name: KERNEL32.dll
  Fault Module Version: 6.3.9600.17415
  Fault Module Timestamp: 545049be
  Exception Code: c00000fd
  Exception Offset: 00018416
  OS Version: 6.3.9600.2.0.0.256.49
  Locale ID: 1033
  Additional Information 1: 2b44
  Additional Information 2: 2b44a0467eb51d7c5c4d290568949fe5
  Additional Information 3: 7df3
  Additional Information 4: 7df32a2773342645ea003a5819024779

Hello Doron, I’m not quite sure what error is this referring to, is there an error report displayed after the application crashes? If there is, can you please click on the “Show error” button, copy the whole content of the log and submit it to us here on the forum?

When exactly does the application crash? What mail service are you using with eM Client?

Regards,

It crashing, so obviously there is no show error from emclient. the only error details I have is the windows show error details which I have attached.

Even if the application crashes there should be an error report window showing the details of the error that occurred before the application crash. Based on your reaction I understand this doesn’t occur, can you please submit a screenshot of the error you’re seeing then?

Thank you,

Here is the screenshot, and attaching also the text I already posted on the original gmail re-sign-in thread:

Problem signature:  Problem Event Name: APPCRASH
  Application Name: MailClient.exe
  Application Version: 6.0.22625.0
  Application Timestamp: 5575a926
  Fault Module Name: clr.dll
  Fault Module Version: 4.0.30319.34014
  Fault Module Timestamp: 52e0b784
  Exception Code: c00000fd
  Exception Offset: 0008b990
  OS Version: 6.3.9600.2.0.0.256.49
  Locale ID: 1033
  Additional Information 1: 6d2a
  Additional Information 2: 6d2acc6d878fa25cf6ba65181ce6df27
  Additional Information 3: 653c
  Additional Information 4: 653c2da327340c14fb35161011480b94

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Hello again, sorry for the belated reply, can you please download this utility, www.emclient.com/tools/procdump_unhandled.zip and open extract the utility from the archive?

Close eM Client and run the .bat file which should load eM Client, if the application crashes immediately please check the procdump folder for a generated .DMP file, please upload this file to a common file sharing service and share it for download with us. Submit a link for download to my email [email protected] and please include a reference link to this forum topic for more information about this issue.

Thank you,

Ran it. Applications does not crash on load, it starts, works for about 30 seconds, then crashes. There is not dump file generated (I looked both in the directory the procdump is supposed to put the file in, and search my entire hard drive for it).

However I did my own procdump on your client (without the bat file), and did generate a full DMP file. See attached (the problem is in the CLR as expected). I sent it to you via mail as it is small. Added a link to this message in the mail.

Cutting to the chase, here is also the error dump from WinDbg:

FAULTING_IP: +0
00000000 ??              ???

EXCEPTION_RECORD:  ffffffff – (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  00000000 – (.cxr 0x0;r)
eax=022f0dd8 ebx=00000000 ecx=0000000c edx=00000000 esi=022f0dd8 edi=0219a2e8
eip=67477283 esp=01f4efe4 ebp=01f4f018 iopl=0         nv up ei ng nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
clr!MethodTable::GetMethodDataHelper+0x14b:
67477283 837d0800        cmp     dword ptr [ebp+8],0  ss:002b:01f4f020=00000000

FAULTING_THREAD:  00000f70

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

PROCESS_NAME:  MailClient.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

APP:  mailclient.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

MANAGED_STACK: !dumpstack -EE
No export dumpstack found

MANAGED_BITNESS_MISMATCH: 
Managed code needs matching platform of sos.dll for proper analysis. Use ‘x86’ debugger.

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS

LAST_CONTROL_TRANSFER:  from 674772d1 to 67477283

STACK_TEXT:  
01f4f018 674772d1 00000000 fa6b4e41 00000064 clr!MethodTable::GetMethodDataHelper+0x14b
01f4f040 6742ffa5 00000000 fa6b4ee5 0219a2e8 clr!MethodTable::GetMethodData+0x31
01f4f08c 674d04c9 0219a2e8 0219d400 fa6b4eb9 clr!MethodTable::GetMethodDataHelper+0x1f
01f4f0d0 674772d1 00000000 fa6b4e89 01f4f0f0 clr!MethodTable::GetMethodDataHelper+0x149
01f4f0f8 675482e4 00000000 fa6b4fcd 0219d400 clr!MethodTable::GetMethodData+0x31
01f4f1a4 67423f43 fa6b4c11 022f0548 021a76ec clr!MethodTableBuilder::VerifyInheritanceSecurity+0x25a
01f4f278 674243b4 679b8488 02044010 02044010 clr!MethodTableBuilder::BuildMethodTableThrowing+0xa65
01f4f44c 67421977 02000185 01f4f4c8 00000000 clr!ClassLoader::CreateTypeHandleForTypeDefThrowing+0x7ec
01f4f4a8 67421fc1 01f4f4c8 fa6b4ad1 00000001 clr!ClassLoader::CreateTypeHandleForTypeKey+0xad
01f4f5e4 6740cbba 00000000 00000000 fa6b48fd clr!ClassLoader::DoIncrementalLoad+0xe9
01f4f694 6740c918 01f4f6e4 01f4f754 00000000 clr!ClassLoader::LoadTypeHandleForTypeKey_Body+0x392
01f4f6d8 6742bb16 01f4f71c 01f4f754 00000000 clr!ClassLoader::LoadTypeHandleForTypeKey+0x90
01f4f778 6742e736 02000185 00000001 00000001 clr!ClassLoader::LoadTypeDefThrowing+0x2ce
01f4f7c0 67420fbb 01f4f848 01f4f804 00000003 clr!ClassLoader::LoadTypeHandleThrowing+0x176
01f4f7e8 676b9859 01f4f848 01f4f804 00000003 clr!ClassLoader::LoadTypeHandleThrowIfFailed+0x1f
01f4f824 67505cbf 67382e94 67383028 00000000 clr!ClassLoader::LoadTypeByNameThrowing+0x51
01f4f84c 673f528a fa6b46cd 679b8170 679b86a0 clr!MscorlibBinder::LoadPrimitiveType+0x35
01f4f8a4 673f97f5 fa6b46bd 673ed5b8 01000000 clr!SystemDomain::LoadBaseSystemClasses+0x24c
01f4f8d4 673ed49a fa6b442d 00000000 00000000 clr!SystemDomain::Init+0x6f
01f4fa44 673ed616 fa6b44e5 00000000 00000000 clr!EEStartupHelper+0x880
01f4fa8c 673ed712 fa6b44f1 00000000 00000000 clr!EEStartup+0x1e
01f4fad0 67478681 fa6b4579 00000000 00000000 clr!EnsureEEStarted+0xea
01f4fb10 6740a2f9 fa6b4525 00000000 00000000 clr!_CorExeMainInternal+0x8f
01f4fb4c 6ef726f4 f30d4bfa 74837b50 6ef60000 clr!_CorExeMain+0x4d
01f4fb88 6efebbcc 6efebb40 6efebb40 01f4fbac mscoreei!_CorExeMain+0x10a
01f4fb98 74837c04 7ebeb000 74837be0 e963163e mscoree!_CorExeMain_Exported+0x8c
01f4fbac 7705ad1f 7ebeb000 eae12883 00000000 kernel32!BaseThreadInitThunk+0x24
01f4fbf4 7705acea ffffffff 7704024e 00000000 ntdll!__RtlUserThreadStart+0x2f
01f4fc04 00000000 6efebb40 7ebeb000 00000000 ntdll!_RtlUserThreadStart+0x1b

STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP: 
clr!MethodTable::GetMethodDataHelper+14b
67477283 837d0800        cmp     dword ptr [ebp+8],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  clr!MethodTable::GetMethodDataHelper+14b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: clr

IMAGE_NAME:  clr.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  545ca678

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_80000003_clr.dll!MethodTable::GetMethodDataHelper

BUCKET_ID:  APPLICATION_FAULT_WRONG_SYMBOLS_clr!MethodTable::GetMethodDataHelper+14b

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:wrong_symbols_80000003_clr.dll!methodtable::getmethoddatahelper

FAILURE_ID_HASH:  {ff66fecf-5472-645a-2951-332ac4435926}

Followup: MachineOwner

Hello, thank you for the received data, I’ve submitted an issue report to the developers for more information about this issue. I’ll keep you posted as soon as I get more insight into what might be going on with the application. Also let me know if you find any more details.

Thank you,

Paul, is there any solution in sight? I would really like to go Pro, but the series of bugs you introduced in the last versions (Google logins, crashes - now one week old bug after I sent you the crash report, not to mention your Pro purchase web page that is not even working showing your DB schema at the bottom when you click to order) are unacceptable.

I really like emClient, and it’s the best client for working with Gmail based mails, but I find myself customizing Outlook with some additional external plugins to get the same experience. I don’t want to, but you are leaving me no choice.

I find it ironic that a person needs to beg to pay you. Truly.