Do some googling on what you find and it may help out. If you do find this, take a look at what your system was doing just BEFORE return value 3 where the error would have occured.
If this isn't an option, review your log files from the Rx report and search for "Return Value 3". If you are on subs, contact your VAR and have them take a look/submit to SolidWorks. I believe you want a new config of the assy with reference parts. Select your file and select to open with Configuration set to Advanced. For now, lets get into SW and open a file from here. Its good to have that record if you need to submit the information later.
Perform step 2, add the files you are working on and package everything into a zip file, preferably on your desktop or you will have to dig for it later.Ĥ. Perform step 1, video capture to record the error that we are seeing. Open this, check to make sure your diagnostics are all good and do a problem capture. Go to Start > All Programs > SW > SW Tools > SW Rx. What version is your friend working with?ģ. What version are you working with, 2013 SP?. Was there any error message that popped up before crash? Generally we are looking for a message and hopefully a code, ie: (125,-20,0). So lets roll through some standard troubleshooting techniques.ġ. Trust me… SolidWorks generally has a lot on its mind.There are a few things that we can try out to resolve your situation. But most times, you just have to give it a little more than 3 seconds before you start clicking the window to get a response.
Unpleasant stop events happen with all software tools.
That means there are 8 million places in the code where it has to decide whether to take a ‘left’ or ‘right’ turn!Īnd the developers are adding nearly 1 million NEW lines with every major release. Today, it has upwards of 12 million lines of code containing over 8 million ‘If/Then’ statements. The reality is that SolidWorks is easily the most sophisticated software tool most of us have ever used. Just look at the ‘Memory’ (column) an application is using and see if the value is still changing. If an operation takes longer than you are expecting and you get this message, you can always open up Task Manager and see if the application still has a ‘pulse’. However, I then had to scramble to take a screen capture because the message closed on its own just a second or so later.
In fact, to generate the screen shot of the message, all I did was open a part with a large pattern, click CTRL-Q (forced full rebuild) and then waited 3 seconds before clicking in the SolidWorks Window. When you are talking about ANY compute intense application, there are bound to be dozens, if not hundreds of operations that are going to take more than 3 seconds to complete calculations and report back to Windows. In Windows 7, it takes a mere 3 seconds before the operating system throws this message… THREE! In Windows Vista, the time for this box to appear was reduced to 10 seconds. In Windows XP, it took 30 seconds of a software application not communicating with the operating system before this message box appeared. This dialog is actually a Windows message indicating that the application listed has stopped responding to “Windows”, but it has not necessarily locked up! Though this box will appear preceding an actual crash, this box does not necessarily indicate that a crash is imminent. The most common misconception here is that SolidWorks has, or is about to crash. You could frankly replace “SolidWorks” with the name of ANY other application loaded on your Windows computer, even Windows Explorer!! Well, NOT REALLY, at least not most of the time.įirst of all, this is a Windows message box, NOT a SolidWorks message box. Take, for instance, a dialog box most every seasoned SolidWorks user has seen at least once…