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?

[ChrisMitchell01]

The information I provided is correct.

• We have fixed some of the issues in 2025.3. Some not all.
• Based on the research done to date, you are more likely to experience these crashes using win11 24H2 than earlier versions of win11 or win10.
• Other Autodesk product teams are also seeing & investigating similar .net based crashes.
• Reducing the number of loaded Inventor add-ins will help to reduce the issue as there is less in process communication with .net.
• The issues are undoubtedly Autodesk specific, but as of now it's unclear if the complete fix will be from Autodesk teams or may also require .net changes from Microsoft.

There are plenty of people working on these issues here & we'll post more info as it becomes available; in the interim, (for anyone else reading this), please send in every single crash report you experience, along with some suitable info about what you were doing prior to the crash, as that will help with further debug efforts.

Thanks,

Chris

[khumphreyYZ3QE]

we've had the same problem with my machine, it just crashes, and I can't repeat it. I've turned off all the add-ins that are 3rd party and some that are Autodesk's. and it started with 2025, now that 2026 is out or soon will be I was told by some developers that it's not fixed in that version either. they are saying that Microsoft changed the .NET between the 2024 and 2025 versions and every programmer is having trouble adapting to the new version. but nothing else crashes like that. I looked up the top 4 people at Autodesk and found their email address, we fired off an email to them and anyone else we had addresses for. we got a lot of attention for the upper people from Autodesk, I was on a Teams call, sharing my screen, for an hour with 2 developers and a customer service guy. and my machine did crash while we were on the call, they said it was because of an add-in I had. the thing is they had me shut it off and unload it, block it right before that. so, I'm not saying that was it. plus, I've had it blocked since Friday of last week, this is Wednesday, and it's crashed every day this week so far. we don't know what to do with this. if anyone finds an answer, please post it! 

thanks!!  

[kbear2AYYK]

This thread is interesting. The user doesn't give details of the crash Inventor is having... only that Inventor is crashing. 

Solved: Inventor 2025 random crashes - Autodesk Community

The last comment mentioned "Efficiency Mode"

Another (solved) comment says by not using Google Chrome, it solved the issue. 

johnsonshiue suggested changing the performance options to the settings below. 

[kbear2AYYK]

I just received a message from Autodesk that gives me some hope of actually getting to the bottom of this. 

Here is the video they linked. 
https://autodesk.my.salesforce.com/sfc/p/#300000008uIL/a/Kf000001HmqX/GxqQXDx7m_nfjJkTaCauwdRSZEOj9Y...

Hello Everyone,

Development has come up with some additional steps we can utilize to better understand what may be happening with these crashes.  I am including the related details below as it requires an additional Windows program to run Inventor so that we can gather details about these crashes through WinDbg.

1. Download WinDbg from https://apps.microsoft.com/detail/9pgjgd53tn86?launch=true&mode=mini&hl=en-US&gl=US
2. Open WinDbg. Launch Inventor from its installation folder.
3. It pauses during the startup. Enter bp /w "m_dwRef > 1" `mfc140u!D:\a\_work\1\s\src\vctools\VC7Libs\Ship\ATLMFC\Src\MFC\cmdtarg.cpp:38` in the command box and press Enter key. This will pause Inventor when the problem happens.
4. Open the Settings dialog.
• Debug settings => Symbol path => remove "srv*"
• Events & exceptions => Access violation => Second Chance Break
5. Click Go to continue to start Inventor.
6. When the problem happens, the item will become bold in the Breakpoints window. Enter .dump C:\dmp\a.dmp or any other place in the command box to dump the current status into a dump file.
7. Send us the generated dmp for debugging.

Attached is a screencast from development that walks through this process, though some of the conditions are different, please follow the instructions above for the correct conditions.  If we can get multiple dump files like this it should help us better understand what is occurring inside the product.

Of note Inventor may run a little bit slower during this process, but it is an important step to help allow us to better understand what is occurring.

Cheers,
Joel Palioca
Customer Technical Success
Autodesk

Autodesk Account (Click to view your Support Cases)
CaseNo:23025286.

[kbear2AYYK]

An update from Autodesk

Use this string instead of the one above to run the debug.  This is much much faster! I am glad we went this route and hopefully it brings results.

bp /w "*(long*)(@rcx+8) > 1" `mfc140u!D:\a\_work\1\s\src\vctools\VC7Libs\Ship\ATLMFC\Src\MFC\cmdtarg.cpp:38` 

[b_sh]

We now have another update to this ongoing issue.

The root cause for the crashes seems to be related to drag and drop actions.

1. Dragging items from the Favorites browser. During the drag, the mouse needs to move on the Ribbon for some time.

2. Dragging between one assembly to another.

3. Dragging files and parts in and out of Inventor, Win Explorer and web browsers.

Notably the drag and drop actions does not always cause the crash to happen immediately. When the drag and drop action is done, the operation does not cause the crash immediately but creates a condition in the system that leads to a crash later. The timing of the crash depends on when the system performs background cleanup operations, which can happen even when the user is not actively interacting with Inventor.

We are now in the process of testing patches to see if these issues can be resolved once and for all.

[kbear2AYYK]

Has anyone else here been running the WinDbg to help diagnose the CoreCLR.dll .NET issue?

Just to update everyone, the developers gave us a patch to try to clear up the CoreCLR crashes seen in the two videos below. (I trimmed them to remove personal info but the end of the video is the crash).

The patch has helped a lot but has not 100% cured our issue. We went several days without a crash which is much better than 1-2 times a day. 

The case is still open and will remain open until it is resolved but I was hoping this would help someone else and possibly get more users to run the WinDBG 

[christian_smith]

I really appreciate you working with us as we work to resolve these issues. While I would hope for 100% resolution of your crashes, I am glad to see that you are in a more stable state now. And thank you for sharing your journey here so that others may also benefit.

Please, let's keep the conversation going if you see additional issues.

[malcolm_smith]

Hi, has there been any further progress on this issue? A few months ago, a colleague and I moved from Inventor 2024 on Widows 10 to Inventor 2025 on Windows 11. Since then, we have been experiencing crashing as described in this thread. This happens every day or so, and sometimes several in one day. I have installed the latest update, but I can't say that there has been any improvement. I did notice that just before my crash this morning I had been dragging the end of file marker in the browser The dragging issue mentioned may be the cause of it. 

[christian_smith]

Hi Malcolm, if your issue is the same that kbear2AYYK reported then the answer is yes, we have made good progress. And you are correct; we have not released the fixes publicly but are evaluating that now. If you want, I would be happy to work with you and our team to see if our planned fixes also resolve your issues. Please reach out to me directly if you would like us to look closer at specific crashes. 

Regards, Christian Smith

[b_sh]

Can confirm that the work we have done with Autodesk has been made good progress on, the user that had the problem at our company has not had any crashes after the test build was installed on his computer. I suggest you to follow up @christian_smith on his offer to test it if you have the same exact issue and entry in Event Viewer.

[kbear2AYYK]

We are still experiencing the crashes with coreclr.dll .NET but it went nearly 3 weeks straight without a crash so I too can also confirm great work has been done to eliminate one source of the crash that was causing us daily issues (dragging objects between split screens caused a majority of these crashes).

This week we saw 2 coreclr.dll .NET crashes. 
One crash Autodesk calls a legacy crash known about since 2012.
The other has to do with a recent Windows update.