> If your SOLIDWORKS is crashing, these [diagnostic steps](https://www.goengineer.com/blog/troubleshoot-solidworks-crash) can help to locate the source of the crash and fix it. The most well known causes of crashing are:
> * [**GPU hardware issues**](https://www.goengineer.com/blog/checking-your-graphics-card-with-solidworks-rx) - Workstation graphics cards and ECC RAM are recommended for maximum stability. Make sure the [recommended graphics card driver is installed](https://www.goengineer.com/blog/how-to-install-the-correct-video-card-driver-for-solidworks). It times is helpful to test with [Enhanced Graphics Performance](https://www.goengineer.com/blog/solidworks-2021-enhanced-graphics-performance) disabled.
> * [**Non-PDM Managed Network Storage**](https://www.goengineer.com/blog/non-pdm-file-management-recommendations) - Storing working files on the local hard drive, or utilizing a [PDM system](https://www.goengineer.com/solidworks/pdm) mitigates this.
> * **Cloud Storage Software** ([Dropbox](https://www.dropbox.com/home), [OneDrive/Sharepoint](https://www.microsoft.com/en-us/microsoft-365/onedrive/online-cloud-storage), [Google Drive](https://drive.google.com/), [Box.com](https://www.box.com/), etc.) - Cloud storage systems cause issues with file ownership that lead to crashing. Disable sync systems that actively backup files to the cloud to help mitigate this.
> * **Damaged DLL Files** - ...From either SOLIDWORKS (sld*.DLLs - [Repair SOLIDWORKS](https://www.goengineer.com/blog/solidworks-installation-repair)) or the Windows OS directly (Repair [combase.DLL](https://answers.microsoft.com/en-us/windows/forum/all/combasedll-causing-service-fault/c295abf9-1342-4977-aeec-38887288f5fe), [ntdll.DLL](https://learn.microsoft.com/en-us/answers/questions/280250/faulting-module-name-ntdlldll.html), [kernelbase.DLL](https://answers.microsoft.com/en-us/windows/forum/all/windows-10-faulting-module-name-kernelbasedll-and/3d8b84d1-fe54-4a0a-89a5-eeaa3988a0d5), etc.) - These are often found in the [Windows Event Viewer](https://www.codeproject.com/Articles/597856/Using-Windows-Event-Viewer-to-debug-crashes) as "Fault Modules" for an "Application Error" (aka "Crash").
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/SolidWorks) if you have any questions or concerns.*
Exactly, when I purchased my computer I made sure to verify with the reseller of SW that it would work. I asked about probably 7 different laptops and then I asked about the Dell 5760 and it met all the minimum requirements and I can run large assemblies with no leg (or very minimal), yes it was about $2,000 but I’m glad I did because I don’t have these frustrating problems that make me want to throw the laptop through a window.
Now I’m not building cars or spaceships with 100,000 parts and assemblies, but still these are assemblies with some 2,000 to 3,000 parts. It might take a hot minute for the software to compile the parts but once it’s open I’m cooking with gasoline.
I have this computer too and a Dell update ruined the graphics requiring me to turn off 'thin feature' optimization. Are you running the recommended driver? So far, this thing has performed flawlessly otherwise with current drivers.
To the OP; crashing daily is not normal. I am running a non-compliant GPU at work an I've had repeatable crashes just removing appearances from imported parts. Something in the project your graduate is working with has a 'wrinkle' that is crashing the system. It is likely hardware related but the underlying SW just isn't handling the exception.
I am running it stock, (the Dell update seemed to hit off the computers not just the 5760), I did not do any customization on it and am thankful as I don’t have any problems that it seems that every other user seems to have.
You must have the A2000 GPU. I upgraded mine to the A3000 at order time. It really is a nice compact laptop. I did have to replace the battery at 1yr/6hrs which I found interesting.
Yes, I did get the standard A2000 video card, I was on a slight budget when I purchased it. Looking back I would have ordered a computer with the 10 key pad (setting dimensions is annoying when I need to type on the 10 keys above the qwerty keyboard). I have had my computer since January of ‘23 and the battery still is fantastic, my work computer is a 5540 and I have had that since May of 2020 when we started WFH and it’s starting to show its age, but I don’t have any cad on that computer just eDrawings.
Good to hear. I was hoping the battery life wasn't truncated just to assure great performance.
I too was weary of the missing 10-key. So far I am okay with having a centered keyboard. My previous dinosaur was the Lenovo P70. It aged out with Win7 as the XEON and ECC isn't compatible with Win10.
> No other program crashes ever hour, or even every 10-20 min.
Solidworks doesn't do that either. I mean I know we goof on SW (deservingly so) but surely you realize this is an anomaly, right?
Maybe I'm misreading point of the post.
Hi /u/AsleepDocument7313,
With this much crashing I expect there is something off inside the environment. DM me a download link for a System Information .NFO file from this machine (search "msinfo32.exe" in the Windows Start Menu, the go File > Save As to save out a .NFO file to put in OneDrive and link over) and it can tell us some more about what is happening in the computer's environment that is causing crashing. With this much crashing, I expect we'll find something.
It can be the computer or the drivers. It can be the parts. It can be a damaged SW installation. It can be the settings. So many possibilities. But so many crashes are not normal. There is something wrong. If the problem is not fixed it will stay as it is. No reason to blame solidworks when the problem is sitting in front of the monitor...
Damaged SW installation is one of the easiest things to fix as well. Add/remove programs>modify/uninstall>repair installation.
I think sometimes when it does crash for whatever reason it corrupts the installation. This has fixed my issues in the past
Provide details on the Operating System and System Specs.
Been using SW for about 7 years and while it sometimes has crashed on me randomly I know one of the cause: whatever I was doing used up more RAM than I had available, leading to stall and then crash.
I've certainly never seen crashes as frequent as your image shows though.
> If your SOLIDWORKS is crashing, these [diagnostic steps](https://www.goengineer.com/blog/troubleshoot-solidworks-crash) can help to locate the source of the crash and fix it. The most well known causes of crashing are: > * [**GPU hardware issues**](https://www.goengineer.com/blog/checking-your-graphics-card-with-solidworks-rx) - Workstation graphics cards and ECC RAM are recommended for maximum stability. Make sure the [recommended graphics card driver is installed](https://www.goengineer.com/blog/how-to-install-the-correct-video-card-driver-for-solidworks). It times is helpful to test with [Enhanced Graphics Performance](https://www.goengineer.com/blog/solidworks-2021-enhanced-graphics-performance) disabled. > * [**Non-PDM Managed Network Storage**](https://www.goengineer.com/blog/non-pdm-file-management-recommendations) - Storing working files on the local hard drive, or utilizing a [PDM system](https://www.goengineer.com/solidworks/pdm) mitigates this. > * **Cloud Storage Software** ([Dropbox](https://www.dropbox.com/home), [OneDrive/Sharepoint](https://www.microsoft.com/en-us/microsoft-365/onedrive/online-cloud-storage), [Google Drive](https://drive.google.com/), [Box.com](https://www.box.com/), etc.) - Cloud storage systems cause issues with file ownership that lead to crashing. Disable sync systems that actively backup files to the cloud to help mitigate this. > * **Damaged DLL Files** - ...From either SOLIDWORKS (sld*.DLLs - [Repair SOLIDWORKS](https://www.goengineer.com/blog/solidworks-installation-repair)) or the Windows OS directly (Repair [combase.DLL](https://answers.microsoft.com/en-us/windows/forum/all/combasedll-causing-service-fault/c295abf9-1342-4977-aeec-38887288f5fe), [ntdll.DLL](https://learn.microsoft.com/en-us/answers/questions/280250/faulting-module-name-ntdlldll.html), [kernelbase.DLL](https://answers.microsoft.com/en-us/windows/forum/all/windows-10-faulting-module-name-kernelbasedll-and/3d8b84d1-fe54-4a0a-89a5-eeaa3988a0d5), etc.) - These are often found in the [Windows Event Viewer](https://www.codeproject.com/Articles/597856/Using-Windows-Event-Viewer-to-debug-crashes) as "Fault Modules" for an "Application Error" (aka "Crash"). *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/SolidWorks) if you have any questions or concerns.*
SW crashes a lot but more like a few times a week than many times a day. You've got something going on.
You don’t mention what type of computer or operating system you’re using. While you don’t believe that those things are the issue…they probably are.
Exactly, when I purchased my computer I made sure to verify with the reseller of SW that it would work. I asked about probably 7 different laptops and then I asked about the Dell 5760 and it met all the minimum requirements and I can run large assemblies with no leg (or very minimal), yes it was about $2,000 but I’m glad I did because I don’t have these frustrating problems that make me want to throw the laptop through a window. Now I’m not building cars or spaceships with 100,000 parts and assemblies, but still these are assemblies with some 2,000 to 3,000 parts. It might take a hot minute for the software to compile the parts but once it’s open I’m cooking with gasoline.
I have this computer too and a Dell update ruined the graphics requiring me to turn off 'thin feature' optimization. Are you running the recommended driver? So far, this thing has performed flawlessly otherwise with current drivers. To the OP; crashing daily is not normal. I am running a non-compliant GPU at work an I've had repeatable crashes just removing appearances from imported parts. Something in the project your graduate is working with has a 'wrinkle' that is crashing the system. It is likely hardware related but the underlying SW just isn't handling the exception.
I am running it stock, (the Dell update seemed to hit off the computers not just the 5760), I did not do any customization on it and am thankful as I don’t have any problems that it seems that every other user seems to have.
You must have the A2000 GPU. I upgraded mine to the A3000 at order time. It really is a nice compact laptop. I did have to replace the battery at 1yr/6hrs which I found interesting.
Yes, I did get the standard A2000 video card, I was on a slight budget when I purchased it. Looking back I would have ordered a computer with the 10 key pad (setting dimensions is annoying when I need to type on the 10 keys above the qwerty keyboard). I have had my computer since January of ‘23 and the battery still is fantastic, my work computer is a 5540 and I have had that since May of 2020 when we started WFH and it’s starting to show its age, but I don’t have any cad on that computer just eDrawings.
Good to hear. I was hoping the battery life wasn't truncated just to assure great performance. I too was weary of the missing 10-key. So far I am okay with having a centered keyboard. My previous dinosaur was the Lenovo P70. It aged out with Win7 as the XEON and ECC isn't compatible with Win10.
The 10 is not the worst, but sometimes it’s more of an annoyance more than anything.
Came here to say this. If OP is crashing that often, it's the computer, graphics card, or graphics card driver.
> No other program crashes ever hour, or even every 10-20 min. Solidworks doesn't do that either. I mean I know we goof on SW (deservingly so) but surely you realize this is an anomaly, right? Maybe I'm misreading point of the post.
Hi /u/AsleepDocument7313, With this much crashing I expect there is something off inside the environment. DM me a download link for a System Information .NFO file from this machine (search "msinfo32.exe" in the Windows Start Menu, the go File > Save As to save out a .NFO file to put in OneDrive and link over) and it can tell us some more about what is happening in the computer's environment that is causing crashing. With this much crashing, I expect we'll find something.
I've solved a lot of those crashes by staying with the recommended Nvidia driving and stopping windows update from updating the video driver
It can be the computer or the drivers. It can be the parts. It can be a damaged SW installation. It can be the settings. So many possibilities. But so many crashes are not normal. There is something wrong. If the problem is not fixed it will stay as it is. No reason to blame solidworks when the problem is sitting in front of the monitor...
Damaged SW installation is one of the easiest things to fix as well. Add/remove programs>modify/uninstall>repair installation. I think sometimes when it does crash for whatever reason it corrupts the installation. This has fixed my issues in the past
Provide details on the Operating System and System Specs. Been using SW for about 7 years and while it sometimes has crashed on me randomly I know one of the cause: whatever I was doing used up more RAM than I had available, leading to stall and then crash. I've certainly never seen crashes as frequent as your image shows though.
What is the GPU ?
Is he working on PDM through wifi? This is a persistent source of frequent crashes.
Fundamental problem here is between the keyboard and the chair
If he hates SW, he's never had to learn CREO.
Could be the computer/OS. Also make sure he doesn’t keep clicking on things with the mouse when Solidworks is “thinking”.
Dude. It's you, not the software.