Learning Forum

[Simon Haberl]

Hi all,

I am having problems with performing static simulations using ANSYS Mechanical (ANSYS 2022 R2) on my laptop (Windows 11, 64 GB RAM). In Workbench, I initially conduct hydrodynamic diffraction simulations to obtain a time signal of hydrodynamic pressure on a floating structure. Afterward, I transfer the hydrodynamic pressure to an FE model in Mechanical. Once the time series is successfully transferred, Mechanical crashes when performing additional steps (mostly, using right click ?!?!). Only when I wait for a very long time after the load mapping, there is no application hang. I also checked windows event viewer, but i can not find helpfull information. Additionally, I have tried reinstalling ANSYS and testing other versions, but the same error persists. Now, here's the twist: on my workstation (Windows 10, 32 GB RAM), the error does not occur. Therefore, the simulation file itself may not be error-free. Has anyone experienced similar issues or can assist me?

 appreciate any hints or suggestions

[Aniket]

Firstly, thanks for your thorough testing and explanation, this seems to be machine machine-specific issue.

Does the project that was worked on the 32 GB RAM machine, when bought to the 64 GB RAM machine work, (also, vice versa)?

If yes, which license is being used on both machines? Are those the same? Are there other differences in hardware? such as HDD vs SSD, available storage space etc?

-Aniket

Forum Rules & Guidelines

[Simon Haberl]

HI Aniket,

thanks for your reply. 

The project created on the 32 GB machine works on the 32 GB machine but not on the 64 GB machine. After realizing this, I created a new (identical) project on the 64 GB machine to test if there is an issue with the initial project. The new project encounters the exact same error on the 64 GB machine and only works on the 32 GB machine.

There are no other significant differences in hardware. The projects are stored on an SSD on both machines. The available disk space is sufficient on both machines.

I obtain the licenses from a license server. The connection to this server works well on both machines.

best Simon

[Aniket]

So this is very strange, and can't be pinned on the database, or hardware. As the project created on a 32 GB machine works on 64 GB, that rules out hardware issues for this specific case, and as a new project created on a 64 GB machine gives issues only on that machine, and not on other, that rules out database (project file related) issues. I am sorry, but it would be difficult to comment further unless we can pin some differences but as a customary check, try changing the temporary directory to the SSD, if default in C: does not have enough space.

-Aniket

Forum Rules & Guidelines

[Simon Haberl]

Hi Aniket,

still encountering the problem. The computer just have one SSD, which is C:. I just moved the project to another directory and the very first simulation worked perfectly. However, the error occurs again when the process is started a second time... 
Very strange...

best Simon

[Aniket]

If it worked for the first and then gave issues for the second, and if nothing else is changed, could it be storage is full? What is the temporary directory location in the workbench?

-Aniket

Forum Rules & Guidelines

[Simon Haberl]

I found something else:  my new system works with a onboard gpu and in addition a dedicated GPU(nvidia) , while the old system just have the onboard GPU. So i tried to disable the onboard GPU at the new system, and the error no longer occures. There must be something wrong with working with two GPU enabled. 
Is there a way to run ansys with both GPU enabled? 

[Simon Haberl]

Update from my end: I have found that the error does not occur when I deactivate the iGPU or work on a external display (while the internal display is disabled). However, since both options are not optimal for my workflow, I would like to avoid this. I have already tried assigning Ansys Workbench and mechanical exclusively to the dGPU in the Nvidia Control Panel and Windows graphics settings, but unfortunately, the error persists. Furthermore i found another thread describing a similar problem. (/forum/forums/topic/ansys-mechanical-crashes-2/). Unfortunaltely there war also no solution found in this thread