Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
48 Views

Internal error when running application

I get the following error when trying to run my app. Any pointers on how to fix this? Running from command line using -collect mi1 works but using -collect mi2 or -collect mi3 causes an identical error. Interestingly this happens rather quickly when running the app. This is on windows with the latest Inspector. Interestingly Vtune gives me an identical error running this app. 

Analysis started for C:\Windows\SysWOW64\cmd.exe (pid = 12404)
Loaded module: C:\Windows\SysWOW64\btpload32.dll, address range [0x02720000-0x0273CFFF]
Loaded module: C:\Windows\SysWOW64\cmd.exe, address range [0x4A140000-0x4A18BFFF]
Loaded module: C:\Program Files (x86)\Intel\Inspector XE 2013\bin32\ccrt12.dll, address range [0x56000000-0x56120FFF], minimal analysis
Loaded module: C:\Windows\syswow64\CRYPTBASE.dll, address range [0x74C30000-0x74C3BFFF]
Loaded module: C:\Windows\syswow64\SspiCli.dll, address range [0x74C40000-0x74C9FFFF]
Loaded module: C:\Windows\syswow64\USER32.dll, address range [0x74E80000-0x74F7FFFF]
Loaded module: C:\Windows\syswow64\ADVAPI32.dll, address range [0x75D30000-0x75DCFFFF]
Loaded module: C:\Windows\syswow64\RPCRT4.dll, address range [0x75FB0000-0x7609FFFF]
Loaded module: C:\Windows\syswow64\GDI32.dll, address range [0x762A0000-0x7632FFFF]
Loaded module: C:\Windows\syswow64\msvcrt.dll, address range [0x76430000-0x764DBFFF]
Loaded module: C:\Windows\syswow64\PSAPI.DLL, address range [0x764E0000-0x764E4FFF]
Loaded module: C:\Windows\syswow64\KERNELBASE.dll, address range [0x76580000-0x765C6FFF]
Loaded module: C:\Windows\syswow64\USP10.dll, address range [0x76680000-0x7671CFFF]
Loaded module: C:\Windows\system32\IMM32.DLL, address range [0x767B0000-0x7680FFFF]
Loaded module: C:\Windows\SysWOW64\sechost.dll, address range [0x768C0000-0x768D8FFF]
Loaded module: C:\Windows\syswow64\MSCTF.dll, address range [0x76B00000-0x76BCBFFF]
Loaded module: C:\Windows\syswow64\kernel32.dll, address range [0x76BD0000-0x76CDFFFF]
Loaded module: C:\Windows\syswow64\LPK.dll, address range [0x770B0000-0x770B9FFF]
Loaded module: C:\Windows\SysWOW64\ntdll.dll, address range [0x770E0000-0x7725FFFF]
Loaded module: C:\Windows\SysWOW64\SYSFER.DLL, address range [0x738D0000-0x7393CFFF]
Loaded module: C:\Windows\system32\WINBRAND.dll, address range [0x70E00000-0x70E06FFF], minimal analysis
Error: Internal error. Please contact Intel customer support team.
Application exit code: -529697949

0 Kudos
5 Replies
Highlighted
Employee
48 Views

The problem appears to be an unhandled C++ exception (error code 0xE06D7363).   Could send me the result directory in a private message?

What analysis type on VTune analysis are you running that triggers the problem?  (The user-mode stack sampling analysis types use the same instrumentation technique as mi1, so it is a little odd that is crashes with VTune, but not with IXE at mi1)

Mark

0 Kudos
Highlighted
48 Views

Actually hold off on investigating this. I ran the app under Application Verifier from Microsoft and there appears to be an issue with sysfer.dll (Some Symantec Endpoint Security dll) raising an unhandled exception. Once I can get the app running cleanly under Application Verifier I will  run it under Inspector / Amplifier. 

0 Kudos
Highlighted
Black Belt
48 Views

You can run Application Verifier with windbg so you will be able to catch and reconstruct the call stack.By looking  at KeUnhandledExceptionFilter or other exception handling function usually first parameter will point to saved exception context.Next you can dump that context with .cxr command and inspect the context during the crash.

0 Kudos
Highlighted
48 Views

Thanks for the helpful comment iliyapolak. Btw disabled Symantec Protection and both Vtune Amplifier and Inspector work beautifully.

0 Kudos
Highlighted
Black Belt
48 Views

You are welcome.Glad that you found the culprit.
0 Kudos