Excel 2019 crashes, .NET Runtime version 2.0.50727.9151 - Fatal Execution Engine Error (00007FFB8AC56D4E) (80131506)

astera123 6 Reputation points
2020-12-04T07:02:28.443+00:00

Hello,

I have Windows 10 64-bit, 20H2 build: 19042.662 and Microsoft Office Pro plus 2019 Version 2011 (Build: 13426.20294) also 64-bit.

I'm trying to run my project c#, VSTO, Excel COM-AddIn created with .NET Framework 3.5, Excel crashes(closes) without any visible error. Even in project try, catch does not help. In Event Viewer i see these 2 error lines:

Faulting application name: EXCEL.EXE, version: 16.0.13426.20294, time stamp: 0x5fbc5677
Faulting module name: VCRUNTIME140_1.dll, version: 14.24.28127.4, time stamp: 0x5d8e68d6
Exception code: 0xc0000005
Fault offset: 0x0000000000003a53
Faulting process id: 0x4260
Faulting application start time: 0x01d6ca036a960ada
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE
Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\VCRUNTIME140_1.dll
Report Id: 13be35db-399c-4bab-ade2-dcc465ef126b
Faulting package full name:

.NET Runtime version 2.0.50727.9151 - Fatal Execution Engine Error (00007FFB8AC56D4E) (80131506)

I checked Control Panel\All Control Panel Items\Programs and Features I have:

"Microsoft Visual C++ 2005..
"Microsoft Visual C++ 2008.. x64 and x86
"Microsoft Visual C++ 2010.. x64 and x86
"Microsoft Visual C++ 2012.. x64 and x86
"Microsoft Visual C++ 2013.. x64 and x86
"Microsoft Visual C++ 2015-2019 Restributable (x64) 14.27.29016"
"Microsoft Visual C++ 2015-2019 Restributable (x86) 14.27.29016"

So it's strange that I receive error for: "VCRUNTIME140_1.dll, version: 14.24.28127.4". Any help?

.NET Runtime
.NET Runtime
.NET: Microsoft Technologies based on the .NET software framework.Runtime: An environment required to run apps that aren't compiled to machine language.
1,125 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Cheong00 3,471 Reputation points
    2020-12-04T08:27:53.797+00:00

    The system found Excel have "Access Violation"(0xc0000005) in the VC runtime and forced it to terminate.

    If you think this might be cause by your code, you should check whether all data structures you pass across the boundary is properly pinned (so the address won't move after you pass a block of memory to Excel, and found the resolved memory address is now invalid for read/write)