Crashing on Startup/File Open

[Lukeofalltrades15]

Getting pretty aggravated especially since I pay every month for this software. I use it for my day job and I build some semi-complex models and drawings of dump truck bodies. Periodically I'l have issues where whenever I try to open a file my client crashes. Sometimes it even just crashes on its own. It's extremely frustrating and I'd love it if this could be resolved. I've sent numerous crash reports in. I'm running a Dell Insperon 3511 with a Intel Core i7-116G7 @ 2.8GHz Processor. 12gb RAM, I should have more than enough computing power to handle Fusion 360.

[Phil.E]

Hi,

Thanks for reporting this and sending in crash reports.

Unfortunately all I see is one crash from today, and it's drawing related. Were you opening a 2D drawing?

Before that your last report is from September 16, 2021, and a handful of reports from September 9. None of these month old crashes are repeated by you after that time frame.

So, from the crash reports it's not showing a clear association with your comments and the crashes. I don't see any crash on open reports. Is it possible you were temporarily using a different login ID recently?

One thing you are missing out on is support. You are a paying customer and entitled to support.

https://knowledge.autodesk.com/contact-support

Please get in touch with them and they can help work through any issues you're having. 

If you could please continue sending in crash reports, and update this thread when you do, I'm happy to follow up. I work mostly on crashing and am glad to help.

[CarlConquilla]

I am having this problem constantly, when I swap from device to device and often with a few days/weeks of usage in between.

I have a workaround and a few suspicions:

To avoid the crash you should go into offline mode immediately after launch - before software update occurs. This will at least allow you to edit and work on your files until the real bug is found.

I suspect for me it might be to do with hardware changes or too many cumulative updates occurring.

Just for the bug record, it always occurs at the same percentage when updating so it is definitely something to do with the automatic update after launching the program.