SW Crashing While Making Exploded View Using "From Part"

[u/MissCeeLee]

My coworker is having an issue, and I've never used this particular path so I'm not sure how to help them troubleshoot.

They make a multi-body part and add an exploded view of the bodies in the part. Then they add two multi-body parts into an assembly to make a combined exploded view of those two parts. They use the "from part" button and, in theory, it should show the same exploded view that was in the part. However, it doesn't always work correctly. Sometimes bodies are left behind. They were moved in the part's exploded view, but show up somewhere else entirely in the assembly. Sometimes SW crashes entirely when trying to edit the exploded view in the assembly.

For example, they moved 3 rectangular bodies in a part, all in one step. When the exploded view was pulled "from part" into the assembly, each of those 3 rectangular bodies were somewhere else in the assembly.

This feels like a SW bug, but I wanted to see if anyone else has experience with this happening, and what they did to fix it (other than not using "from part")

[u/AutoModerator]

If your SOLIDWORKS is crashing, these diagnostic steps can help to locate the source of the crash and fix it. The most well known causes of crashing are:

• GPU hardware issues - Workstation graphics cards and ECC RAM are recommended for maximum stability. Make sure the recommended graphics card driver is installed. It times is helpful to test with Enhanced Graphics Performance disabled.

• Non-PDM Managed Network Storage - Storing working files on the local hard drive, or utilizing a PDM system mitigates this.

• Cloud Storage Software (Dropbox, OneDrive/Sharepoint, Google Drive, Box.com) - 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) or the Windows OS directly (Repair combase.DLL, ntdll.DLL, kernelbase.DLL, etc.) - These are often found in the Windows Event Viewer 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 if you have any questions or concerns.

[u/experienced3Dguy]

You didn't share any info about your computer hardware specs, GPU, OS version,etc.

Also, I'd recommend using SOLIDWORKS Rx to run a Problem Capture session and send the log files and video to your VAR/reseller Technical Support team.

[u/MissCeeLee → u/experienced3Dguy]

I don't have all that info, it's not my computer but I didn't think it would have a difference if it's a known bug. Windows 11, SW 2025.

I will when we have time. We're in chaotic project mode and I wanted to see if anyone else experienced this.

[u/experienced3Dguy → u/MissCeeLee]

If it's something that is easy to reproduce consistently, then don't sit on it. Get that Rx session to your VAR pronto so it can be analyzed and escalated to SOLIDWORKS R&D, if necessary.

[u/MissCeeLee → u/experienced3Dguy]

Like I said, we will when we have time. This week isn't the week for troubleshooting.