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]

String value or DWORD value?  Looks like DWORD is already set to 0.

[johnsonshiue]

Hi! Then it means the FIPS related instability does not apply to your machine. I am sorry my suggestion was not helpful.

Many thanks!

[kbear2AYYK]

I can verify this registry value also exists on all our machines set to 0. 

So far, we've spent over $2,800 trying to fix this issue as we (also) went as far as to purchase an Unneeded new PC to prove to Autodesk this was not a machine issue. That is not to mention the literal days (most likely over 60 hours as this has been going on since August 2024) and the down time and lost work because of this issue. 

These are the steps we took (at that point in time)

https://forums.autodesk.com/t5/inventor-forum/microsoft-netcore-app-8-0-8-coreclr-dll-inventor-crash... 

We did see this error on previous versions but maybe once every other month.... but since we've gone to Inventor 2025... it has become a royal pain. 

[dlandisadaptek]

Are you also running in a multi-monitor configuration, possibly with different scaling factors?  We've got new laptops (16") and are using 24" monitors connected through a dock.  The scaling factors are different on ours to keep the larger screens from being clipped.  Several forum posts indicate this can cause issues, but none have really tied random crashes to that from what I can tell.

[kbear2AYYK]

We are running desktops. Our users all have two 24" 4K monitors. Each user seems to run at a different DPIs. Actually, one user uses 100% scaling on one monitor and 150% on another.

But for the user having most of the issues, when we swapped computers for the new one, I simply changed the resolution to 1920x1080 effectively running at 100% scaling but larger text on both monitors as the user has bad eyesight and needed larger text.

Inventor still crashes even at a smaller DPI and Resolution. 

[dlandisadaptek]

Well, I won't waste too much time messing with that then.

I'm using different DPI settings as well as scaling because my laptop with a 16" screen (2560x1600) is my main display (for remote use) and I don't want to use Inventor on it, until I have to when I'm working remote.  The others are 22", 23" and 24", plugged into a dock, and all max out at 1920x1080.

[kbear2AYYK]

I tried a different channel at Autodesk to draw attention to this issue. They simply told me to shut off my auto-renewal feature on my account and closed the case (basically saying, "Go ahead and find a new CAD software").

Charming

[johnsonshiue]

Hi! Do you mind sharing the thread or instruction about shutting off Auto-Renew with me directly (johnson.shiue@autodesk.com)? I am not aware of an instability issue associated with Auto-Renew.

Many thanks!

[kbear2AYYK]

Sorry i was referring to this... We are coming up on our contract renewal.with Autodesk. When i mentioned how much trouble we were having and asked for a discount, i was told that's impossible and the best thing to do was to shut off the auto-renew selection on our contract.  

[b_sh]

Our Autodesk partner has taken the case internally with Autodesk trying to push the issue forward internally, but it's hard when we have told them everything we have done so far, and sent them this forum post but they still send us an email with troubleshooting steps, where all have already been made and documented...

What we have found ourselves is that according to the minidump file there might be an issue with RxAppDocViewUI.dll that is causing the crash. But that's just guessing from what we can see, without seeing the source code we cant do much else...

@johnsonshiue you guys now have three different companies that has pretty much the same issue, can we get some effort from Autodesk where they now can compare these three cases to once and for all get this sorted?

The total cost for us for this one issue is racking up quickly into the 10s of thousands...

[johnsonshiue]

Hi! This is a struggle we are also facing. There seem to be multiple moving parts here. Inventor 2025.3 update Beta will be available on Inventor Feedback Community (https://autode.sk/InventorBeta) soon. Once it becomes available, please try it and see if it helps.

Many thanks!

[kbear2AYYK]

An update on our end...

I simply asked them to throw us a bone, a discount or refund. The reply was basically, “Just don’t buy our product once your contract is over. Turn off Auto Renew”

At this point the daily crash is easy to deal with compared to the last 7 months.

I never had Siemen’s customer service reps get so laser focused ... so stuck on only our environment that they wouldn’t move on to investigating the actual software. Plus, NX had a log system that made finding issues like this quick. (Autodesk can’t be bothered with extended log files)

Even SolidWorks was very customer focused. We’d get patches on the fly to try if we ever ran in to major issues. Heck… The same with NX. We didn’t have to argue for months to get them to dig deep... and we for sure did not have to wait months for a fix.

It took literally 5 months and several forum posts before Autodesk would even consider it was an issue with Inventor and not just us.

We only heard.... 

Have you reformatted? Have you tried a different user? Its your processor. It’s your RAM. Its your spacemouse. It’s your install. It’s your network. Have you tried disconnecting the mouse, keyboard, network plugs, monitors, and power cords to see if the issue persists? Yeah... That is (somewhat) sarcasm.

In reality, we were actually told “Autodesk does not support files on a network server”. If this was 1995 I would be ok with that… but I think any company would be mortified to say that now.

Not Autodesk.

Heck they couldn’t even be bothered to keep the case fully open and had to put it on hold even after begging to just keep it open to make us feel better.

But really… what is a handful of seats to Autodesk? 

johnsonshiue, you are an asset to Autodesk and this is not to say anything about your performance. It is saying something about Autodesk as a whole. 

[sam]

“Autodesk does not support files on a network server”

But they Will Support Files On A Network Cloud Server ???

And Agressively Push For ALL to Get On Board with Network Cloud Servers.

Very Interesting to say the Least!

What Does This Statement Actually Tell Us All?

What Do You Read Into this Statement?

[sam]

It is kinda Disappointing to read a statement as such from Autodesk.

I have always been an Autodesk Fan. I've been using Autodesk since AutoCAD ver.-6. And have used Inventor since series 6.

But I have always been Skeptical of the Push to the Cloud.

It Is a Shame that Money has to be the Major Driving Force in CAD software development insteed of the users Trust, & Productivity.

Perhaps Trump will help reshape those ideals.

[johnsonshiue]

Hi Folks,

Whoever said "Autodesk does not support files on a network server" is wrong. I would like to see an example or a communication from Autodesk. Please share it with me privately (johnson.shiue@autodesk.com).

I am very sorry that you are experiencing the instability. I am certain that some of them, if not all, are Inventor induced. Inventor should never crash. However, to take any further action, we will need reproducible steps or the crash reports. For the known cases, we are actively investigating and trying to find safe fixes.

Many thanks!

[kbear2AYYK]

So, the crash is the issue but no longer THE ISSUE. 

I don't think any of us are opposed to verifying and possibly eliminating local parameters as a cause of an issue. But what is appalling is, from what I read, at least two companies had to buy a brand-new PC to convince Autodesk to stop blaming our local environment but even that didn't work. The blame still fell solely on the end user. And to add insult to injury, we were asked to repeat the same steps over and over and over... The same steps we went to great lengths to eliminate as the cause of the issue. 

But I digress... you requested info to be emailed to you. I placed that below.

And while digging through to find it... this exact quote from AUTODESK sums up THE ISSUE "These steps are to try to help us confirm that it (the crash) is something unique to the environment.  Troubleshooting the environment itself is typically outside of our support."

While this is possibly a pour choice of words, it does sum up the experience. What we hear Autodesk saying is "The issue cannot be Inventor, it has to be you, so we need to close the ticket."

Close the ticket is the goal.

I am not looking to throw anyone under the bus as I can almost guarantee your department is coldly judged by Autodesk Managment, not by success or user feedback, but by the number of closed tickets. 

My most recent Support Case 23988344 is a perfect example of this goal. In a mere 24 hours, my request was dismissed and closed.  And it is happening again. Not even a small acknowledgment of Autodesk telling us to, "get lost loser"... Autodesk truly does not need the smaller companies and its clear. 



The info you requested: 
CaseNo:23025286 1/24/25

Autodesk: "as has been mentioned before we do not recommend the files being on a network for accessing anymore. The recommendation is to have the files locally on the machine."

Me: Question… When you say, “we do not recommend the files being on a network for accessing anymore. The recommendation is to have the files locally on the machine.” Is that in reference to this ticket or a blanket statement to all Autodesk users?

Autodesk: "Regarding the not recommending files on a network location, that is a general recommendation and not specific to this case."

[b_sh]

Well the user who has issues just swapped computers with another coworker that have NOT had any similar crashes.

To keep it short, the coworker who have been having this issue crashed within the first day at least two times.

This is a several year old computer with components we know work with all versions of Inventor... What is the next step then?? We have still had NO answer from Autodesk or hint to what can be causing this issue and we are left in the dust trying to figure it out ourselves, which at this point is pretty hard... We can't keep waiting for "The next update" since we have been doing that and dealing with this issue for several months, if you think the issue will be fixed in a coming update then you should also be able to tell us what was causing it in the first place...

[johnsonshiue]

Hi! A Beta version of the coming 2025.3 update is available on Inventor Feedback Community (https://autode.sk/InventorBeta). Please sign up the community and download the update. It contains quite a few fixes addressing the instability issues.

Please note that the Beta version isn't the final version. When the official update is released, the Beta update will need to be uninstalled before the official update can be installed.

Many thanks!

[b_sh]

Harald from our company has now applied, does each user that want to try the version have to apply or can one user apply and distribute the version to the rest?

[b_sh]

@dlandisadaptek @kbear2AYYK 

Are the users that are having these issues in a local domain for the company, have it been tried to run the user on only a local account with no connection to the domain at all? Our next troubleshooting steps are
- New domainuser is created in AD.

If this does not help we are trying

- New user that is only local, full setup without any connection to the domain to see if the issue is fixed somehow.
- Running WinDgb, ProcDump and WireShark and pointing these towards coreclr.dll and Inventor.exe