AnsweredAssumed Answered

Flow simulation 2012 SP5.0 batch simulation crash on x2+ simultaneous runs

Question asked by Dragos Ciordas on Sep 17, 2013
Latest reply on Sep 30, 2013 by Jared Conway

Hello,

 

I have a rather big issue with Solidworks Flow Simulation, namely the fact that I am unable to run a batch analysis with 2 or more simultaneous runs. Solidworks stops responding and completely crashes whenever I try this as you can see below.

 

vlcsnap-2013-09-16-13h16m00s171.png

 

In detail:

- x2, x4, x6 simultaneous batch simulation attempted, all crashing after various times

- plain and x1 batch simulation runs without any issues

- issue present on another similar computer as well

- Solidworks 2012 SP5.0, Flow simulation 2012 SP5.0 build 2142

- Windows 7 SP1 x64 machine, 2x Xeon E5-2620 CPUs, 24GB RAM, Quadro 2000 video card

- all relevant files are saved locally (not on network)

 

Fixes attempted:

- disable all non-essential windows processes (such as explorer.exe)

- disable multi-threading

- Solidworks reinstall

- Office (2007) repair

- Full CPU allowance for all instances (12/24 on all of them)

 

VAR response, suggestions attempted without success:

"I know you are using 2012 however I was checking in SolidWorks 2013 and noticed that there is a change in behaviour.  The “Maximum simultaneous run at this computer” option from the Batch Run command is limited to 2 simultaneous runs. This change is intentional as it apparently offers the best balance of performance and flexibility.  Previously, the  option from the Batch Run command was only limited to the number of cores on the computer – hence why you can do so many.  After discussion with the guys here we also think that perhaps SolidWorks limited the number of simulations to make it more stable and make it so that everything is handled a lot better.  I appreciate you are trying to do so many at once for convenience sake but I would ask that you try 4, or, since it is the only option in 2013, 2 studies at a time and see if it completes."

 

Windows crash log error:

Faulting application name: sldworks.exe, version: 20.5.0.80, time stamp: 0x506ff2af

Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e

Exception code: 0xc0000374

Fault offset: 0x00000000000c40f2

Faulting process id: 0x1474

Faulting application start time: 0x01ceb2d2a3b8bc00

Faulting application path: C:\Program Files\SolidWorks Corp\SolidWorks\sldworks.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 360f7dde-1ec7-11e3-bc31-0015833d0a57

 

Can anyone help me with this issue? I know x1 simulations run fine, however that only uses around 15% of the CPU and basically means 85% of the machine is wasted. We are in a rush at the moment and being able to finish the simulations quicker is critical. I do not believe this to be a Solidworks limitation as it would not make sense. Simultaneous batch runs are not complicated to implement and are a great efficiency booster so I do not understand why this would not be working. This is not a new feature either, and the lack of information on this problem makes me think this generally works for most people.

 

Thanks,

Dragos Ciordas

 

 


Outcomes