For the last few days, Solidworks has just been crashing all day. I get either "Solidworks is out of memory" (task manager saying 30%) or "Solidworks is running a command" (I wait, it crashes) and now I can't even open some files at all. I just get an unexpected error message and of course, CRASH. This computer is brand new and I've run diagnostics to no avail. Is this the norm? Does inventor crash like this? Somebody please help!!
I'm trying to work on a drawing of a very simple assembly. Specs below.
Your system looks good. Better than mine at least. And I can often go days without crashing so that should not be the problem.
Try a repair, see if that improves things. Also, make sure that your RAM chips are fine. Run a RAM hardware diagnostic test.
Well, it appears I may have bigger issues. Even the repair was a bust.
Sounds like you may need to do a clean uninstall and reinstall. If you are on subscription contact your VAR to have them walk you through it. Here's a link UPDATED TECH TIP: Clean Uninstall of SOLIDWORKS | DASI Solutions Blog
I'm curious what version of solidworks you are using. I have never had a problem with crashes until I installed solidworks 2019. Why? Why? Why?
2019. Why, indeed?
Greg Kuhn wrote:
I'm curious what version of solidworks you are using. I have never had a problem with crashes until I installed solidworks 2019. Why? Why? Why?
Just curious. What steps have you or your VAR taken to troubleshoot the crashes?
I will say that the problem seems to be related to working off the network. The same thing started happening to 4 of my co-workers as soon as they installed solidworks 2019. So far the only thing that seem to help is copying my design to my hard drive and avoid the network here at work. I have contacted our IT company and have no concrete solutions. I have installed the new service park 01 hoping that would help. I really wish I could go back to solidworks 2018 but with the fact there is no backwards compatibility causes major problem with our shared hardware.
Alin Vargatu do you have any other suggestions?
Gerhard Hieronymus if you are working on a network, could you try working off your harddrive?
Greg Kuhn wrote:
I will say that the problem seems to be related to working off the network. The same thing started happening to 4 of my co-workers as soon as they installed solidworks 2019. So far the only thing that seem to help is copying my design to my hard drive and avoid the network here at work. I have contacted our IT company and have no concrete solutions. I have installed the new service park 01 hoping that would help. I really wish I could go back to solidworks 2018 but with the fact there is no backwards compatibility causes major problem with our shared hardware.
Alin Vargatu do you have any other suggestions?
Gerhard Hieronymus if you are working on a network, could you try working off your harddrive?
Absolutely. Use PDM Standard (if you cannot afford PDM Pro). Is the simplest way to ensure all files are being opened from the local drive (hopefully a fast NVME2 SSD), but stored on the network.
As a side effect, you will notice the elimination of fights over file ownership (Hey, Greg would you please close your assembly? I need to open file A12345.sldprt first, for editing).
I will look into this. Although this decision is not mine to make.
Do you have any insight as to why we have not encountered this problem until now? We were previously running 2015, then 2016, then 2017, then 2018 with out a problem. If I can understand why we need this now and not before it will help me get this implemented
Greg Kuhn wrote:
I will look into this. Although this decision is not mine to make.
Do you have any insight as to why we have not encountered this problem until now? We were previously running 2015, then 2016, then 2017, then 2018 with out a problem. If I can understand why we need this now and not before it will help me get this implemented
There can be many factors, some of them involving software, many of them involving the hardware. Get you VAR involved. Also, to make the troubleshooting easier, make sure all users have this option checked:
Greg Kuhn wrote:
I will look into this. Although this decision is not mine to make.
Do you have any insight as to why we have not encountered this problem until now? We were previously running 2015, then 2016, then 2017, then 2018 with out a problem. If I can understand why we need this now and not before it will help me get this implemented
For every seat of SW Professional or Premium you have, you get a license of PDM Standard. So, if you've got SW Pro or Premium, you don't have to spend any money implementing it, just time (which does equal money, but sometimes that's easier to justify to the bean counters). That may make it an easier sell.
Alin Vargatu wrote:
Absolutely. Use PDM Standard (if you cannot afford PDM Pro). Is the simplest way to ensure all files are being opened from the local drive (hopefully a fast NVME2 SSD), but stored on the network.
As a side effect, you will notice the elimination of fights over file ownership (Hey, Greg would you please close your assembly? I need to open file A12345.sldprt first, for editing).
I have been fighting for that ever since we got the PDM standard bundled. The company is unwilling to pay for having the VAR set it up. And the ownership fights are only the tip of the iceburg that PDM will solve.
Jim Steinmeyer wrote:
Alin Vargatu wrote:
Absolutely. Use PDM Standard (if you cannot afford PDM Pro). Is the simplest way to ensure all files are being opened from the local drive (hopefully a fast NVME2 SSD), but stored on the network.
As a side effect, you will notice the elimination of fights over file ownership (Hey, Greg would you please close your assembly? I need to open file A12345.sldprt first, for editing).
I have been fighting for that ever since we got the PDM standard bundled. The company is unwilling to pay for having the VAR set it up. And the ownership fights are only the tip of the iceburg that PDM will solve.
Do an ROI study. When they will see how much money the company is wasting, they might change their mind.
Alin Vargatu wrote:
Do an ROI study. When they will see how much money the company is wasting, they might change their mind.
We did, they didn't
Jim Steinmeyer wrote:
Alin Vargatu wrote:
Absolutely. Use PDM Standard (if you cannot afford PDM Pro). Is the simplest way to ensure all files are being opened from the local drive (hopefully a fast NVME2 SSD), but stored on the network.
As a side effect, you will notice the elimination of fights over file ownership (Hey, Greg would you please close your assembly? I need to open file A12345.sldprt first, for editing).
I have been fighting for that ever since we got the PDM standard bundled. The company is unwilling to pay for having the VAR set it up. And the ownership fights are only the tip of the iceburg that PDM will solve.
If all you need it for is file management, you can set it up yourself. There are some great instructions over at Alin's employer's website https://www.javelin-tech.com/blog/2015/11/solidworks-pdm-standard-getting-started-guide/ . That's definitely one area that Alin's VAR does a better job than my VAR. My VAR is great, but they don't publish nearly as much free howto information as Javelin.
It looks like those instructions are even more comprehensive than they were when I set it up here.
Since you're using 2019. Turn off Enchanced Graphic:
If you still get low memory after that, set Windows page file size min and max to at least 3x RAM.
from my 10 years of experience I noticed that slower the computer, better it will work.
The problem is when you work too fast and you start adding news stuff to 3D model while solidworks is still processing previous command in the background. For every action you need to AFK for few seconds until solidworks catches up. If you got really fast PC you will have a bit more of a problem to determine if solidworks is still processing something in the background.
No this is not normal however when I was running Pro-E I called it my Pro-Exit mode. And yes I had crashes with Inventor too.
The Out of Memory error has to do with the amount of room set in your cache if I remember correctly, I will have to search for that but it is an easy fix. It would help if we knew what type of work you are seeing the crashes with. Common smaller models, Large assemblies, rendering? What are the specs of your new computer? My machine was "custom built" new when I got it but it was a boat anchor even then. So build of machine is more important than "new".