Any way to find the reason SW crashed? 2

[MDGroup]

When SW crashes you get the screen 'An error has occured and SW needs to restart'.

Is there any way to determine the basic reason why SW crashed? Can you get a report telling you it ran out of memory, or ran into a corrupt file, or the server crashed, or impatient user, or Windows 7 disagreed with something, ....

It asks if you want to send a Performance Log to SW for analysis; can we access that log and decipher the root cause of the problem.

One of the users here said that SW crashed 4 times this morning and 9 times yesterday. It would be nice to find out why.

I deal with most of the same files, and crash very rarely only when working on really large files and I do something stupid.

Thanks.

 

[CADFlyer]

Use the SolidWorks Rx in the Start, Programs directory

It has many useful tools & information, including a 'Problem Capture' feature that may get what you are looking for.

 

[JMirisola]

While you can access a crash log via SolidWorks Rx, deciphering it is another thing. Your best bet is to have the user pay attention to what s/he is doing so that common denominators can be captured.
With regards to Rx, run it after a crash to gather data from said crash. If crashes are happening frequently, get your VAR involved. That's what you pay them thousands of dollars a year for.

Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog

 

[MDGroup]

I will try to have them pull the logs from SWRx for the next several crashes. Then send them over to our VAR and see what they can tell us.

Thanks.