Inventor random crashes due to Microsoft.NETCore.App\8.0.12\coreclr.dll

[b_sh]

Hello,

For months not a co-worker has had issues with Inventor crashing without warning. There are no popups of crash reports or anything anywhere when Inventor crashes. The only signs of the crash is found in Event viewer it has this logged:

Feil i programnavn: Inventor.exe, versjon: 29.20.29300.0, tidsangivelse: 0x671b9728
Feil i objektnavn: coreclr.dll, versjon: 8.0.1224.60305, tidsangivelse: 0x674f3d10
Unntakskode: 0xc0000005
Feilforskyvning: 0x00000000000fd390
Feilaktig prosess-ID: 0xBAD98
Tidspunkt for start av feilaktig program: 0x1DB73A21C17AF92
Feilaktig programbane: C:\Program Files\Autodesk\Inventor 2025\Bin\Inventor.exe
Feilaktig modulbane: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.12\coreclr.dll
Rapport-ID: 0e3c4cfb-065a-4342-9d46-5bf810605267
Fullt navn på feilaktig pakke: 
Feilaktig pakkerelativt program-ID:

Application: Inventor.exe
CoreCLR Version: 8.0.1224.60305
.NET Version: 8.0.12
Description: The process was terminated due to an internal error in the .NET Runtime at IP 0x00007FF82867D390 (0x00007FF828580000) with exit code 0x80131506.

I've lost track of things we have tried but now we have:

- Replaced the 3dX mouse he was using.

- Replaced the entire computer after trying different troubleshooting steps on his other computer.

- Updated and rolled back .Net versions and graphic drivers.

There are probably many more things I've forgotten over the months, but does anyone have any ideas as to what can be causing this?

[dlandisadaptek]

Sorry, I won't be of much help when it comes to IT and networking... those are above my paygrade, I'm only a user with slightly more than typical user access to the server and network environment.  I can offer that we are all on a single network domain and can't access any of the files on our servers if we're not connected to the domain.

[b_sh]

Saw this post today on a popular site.

Didn't have to look far down before we found Autodesk in between Broadcom and other vendors. Maybe it's time for Autodesk to take some time and reflect on what direction they are going. Companies like Broadcom (VMWare vendor) are losing major customers because they are going in the wrong direction.

[kbear2AYYK]

Obviously it's not just us dealing with the AutoCrash establishment.

I've had many dealing with SolidWorks and NX (Dassault & Siemens) 

Siemens is a similar company to what is spoken about in your screenshots but somehow, their CAD division is still able to maintain a level of care for their smaller customers. (Offering license packages that fit well for all sizes of needs, supporting issues no one else has, etc.)

Dassault is big enough to give you the support you need but small enough they still are able to work with you on many levels. 

While neither of them are perfect... long story short, neither of them ever told us what Autodesk (essentially) did... "Take your silly handful of licenses and shove off peasant." 

I hate switching CAD software... I've done it three times in my career now. But SolidWorks and NX are close enough to Inventor that the learning curve required may be worth the trouble and surprisingly, NX has come down in price since 2019. Crazy talk.  

[b_sh]

As expected did the new version not help at all with the crashes, user crashed two times today already. Same error message

[johnsonshiue]

Hi! I assume 2025.3 Beta1 was installed. Please share the crash report IDs or the user email address privately with me (johnson.shiue@autodesk.com). I would like to understand the crash better.

Many thanks!

[b_sh]

He is not getting any crash error reports again after installing 2025.3 Beta1, but the reason for the crash is exactly the same as with the other versions of AutoDesk, so the error report will say exactly the same as before.

[kbear2AYYK]

9 months later we are still having this same issue. I've looked at all our machines event viewers. They all have this same error... about every other week (which is tolerable but still unacceptable.) 

Going out on a limb here to say... we are not the only ones with this issue

[kbear2AYYK]

Now... I'll admit... These errors are our fault. We had the systems plugged in and turned on. 

At any rate, I thought I'd show what our system is doing to cause Inventurd.exe to crash. Each division represents a different machine. 

(Newest PC) 


---------

---------

---------
(Replacement PC)

---------

(Original PC - Picture too big for forum)

[dlandisadaptek]

I've been waiting a while to post to see if there has been any improvement and, it "seems" my problem related to the .NET crashes has gotten a bit better.  On 3/13, there was an update to .NET to version 8.0.14 and I applied it since my Inventor crashes seemed related to ".NETCore.App\8.0.13\coreclr.dll".  Since then, I've had no Inventor sudden exits with no warning or reporting dialog popups.  That said, Inventor did freeze 2 days ago, and I had to use task manager to get out and restart it.  But that's the only crash I've noticed since the .NET update, and it was different than before.  Event Viewer hasn't shown an Inventor error related to .NET since then either.

[b_sh]

I will try this if it comes to it now, the user is now on a completely new Domain account in hopes of that fixing our ongoing problems with it, but I will have to check also if he got the new .NET version after we reset his computer (again for the 9th time) yesterday.

[dlandisadaptek]

Good luck!

[kbear2AYYK]

Thanks for the update and suggestion. 

I have a big but though....

Application: Inventor.exe
CoreCLR Version: 8.0.1425.11118
.NET Version: 8.0.14
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFAE61F3534
Stack: The handle is invalid

[dlandisadaptek]

Oh well, so much for that theory.  I haven't seen it yet and it's been a week since applying that update, so I was starting to get my hopes up.

[kbear2AYYK]

Well it couldn't hurt so I am just making sure we keep .NET up to date. 

[b_sh]

We are on day two and the user has not crashed YET after:

1. PC reformatted and updated.
2. New user created in AD.
3. User signed into new AD account.
4. Installed Inventor and Vault w/ newest service-packs.
5. note: We DID NOT import the user profile for the user into Inventor, we will have to troubleshoot further to see if this can be related if the user experience not crashing next week.

If the users having issues have OLD domain / AD accounts (we are hybrid) this MIGHT be related without knowing 100% yet. Since it was only one user having the issue we are at least trying to rule out the user itself at this point since hardware issues have been fully out ruled. I am just a bit sad that we are helping autodesk here figure out this issue more than they are themselves, but happy to be helping the community. Should send an invoice for work done to Autodesk

[b_sh]

Send you an email now with a crash report ID he was able to submit.

[b_sh]

Bad news... the user is still experiencing crashes after setting up the computer in a new AD account and not bringing over the userprofile in Inventor...

[ChrisMitchell01]

Johnson is on vacation this week....

A few more issues have been resolved in the 2025.3 Release Candidate build which was posted to the Inventor Feedback/Beta Community last Friday. (https://Autode.sk/InventorBeta).

Several of the different product teams are investigating this .net issue; it's not unique to Inventor. Currently Inventor stability may be improved by unloading any unused addins, (Autodesk or 3rd party). Current indications are that it's more of an issue on windows 11 24H2, so if you have the ability to "downgrade" windows then that may help.

-Chris

[t.schuettNQQNS]

Hi All,

we are currently having the same issue with Inventor crashes and the .NET Core Error in the logs.

This occurs on more than 15 Machines with Win10. So its not only Windows 11 related as mentioned above.

The newed offically released servicepacks are installed.

Is there an estimated time until a working fix?

Best regards,
Timo

[kbear2AYYK]

---

@ChrisMitchell01 wrote:

A few more issues have been resolved in the 2025.3 Release Candidate build which was posted to the Inventor Feedback/Beta Community last Friday. 

We have installed the newest BETA version and the crash still happens. 

Several of the different product teams are investigating this .net issue; it's not unique to Inventor.

Fun fact, if you Google "coreclr crash" Autodesk pops up first and then several times after... (that with not even searching Inventor or Autodesk)

Currently Inventor stability may be improved by unloading any unused addins, (Autodesk or 3rd party).

We had developers on call investigating this crash. They unloaded any unused addins (they wanted to unload Frame Generator but we use that) and the crash still occurred.

Current indications are that it's more of an issue on windows 11 24H2, so if you have the ability to "downgrade" windows then that may help.

We were having this issue as far back as July 2024 (actually when we switched to 2025). 24H2 did not get released until October 2024. Also, another post indicates they have Windows 10 machines also having this same issue. 

@t.schuettNQQNS wrote: we are currently having the same issue with Inventor crashes and the .NET Core Error in the logs.

This occurs on more than 15 Machines with Win10. So its not only Windows 11 related as mentioned above.

-Chris

---

I know I sound like a complete $%@! and I am not trying to $%@! on your efforts but for nearly a year now we have had Autodesk

• Avoid taking any blame which again is here when you say "it's not unique to Inventor" 
• Blaming the customer... We've reformatted and even purchased a brand-new machine so telling us to downgrade to windows 11 24H2 is just proof Autodesk doesn't listen to the steps the clients have already taken.
• All these steps have been completed, documented, and most importantly, reported as not solving the issue and yet...  

How about instead of grasping at straws, Autodesk could do something like create a deep encrypted debugger as outlined here:
.NET debugger extensions - .NET | Microsoft Learn
Encrypting data - .NET | Microsoft Learn