Learning Forum

[Filip Parol]

latly when i'm using my gpu (rtx quadro 6000) to accelerate my calculation using ansys mechanical WB, between substeps i offen geting errors like this:

 *** ERROR ***                           CP =     789.812   TIME= 14:10:30
 A generic error has occurred when using the GPU accelerator capability.
  Error code = 700 which translates to: an illegal memory access was    
 encountered.  Please rerun without using the GPU accelerator           
 capability.  Please send the data leading to this operation to your    
 technical support provider, as this will allow ANSYS, Inc to improve   
 the program.                                                           

 *** ERROR ***                           CP =     789.812   TIME= 14:10:30
 An error has occurred in the Sparse Matrix Solver while factoring the  
 matrix.  Error code = 215.  Please send the data leading to this       
 operation to your technical support provider, as this will allow       
 ANSYS, Inc to improve the program.   

 

sometimes i'm getting ( SIG$SEGV ) error aswell.
usualy i'm working with fracture or contact analisys.
when turning off gpu acceleration, case is solved without problems.

has anyone idee what can be wrong?

[Aniket Chavan]

So does this analysis run ok if you turn off GPU acceleration as shown in image below:

 

Mechanical>File>Solve Process settings>My Computer>Advanced

\You mentioned Lately, so was this GPU with acceleration working before?

I don't think the GPU you are using, is on the supported GPUs list for 2022R2 for Mechanical APDL: https://www.ansys.com/content/dam/it-solutions/platform-support/2022-r2-gpu-accelerator-capabilities.pdf

-Aniket

How to access Ansys help links

Guidelines for Posting on Ansys Learning Forum

 

[Filip Parol]

thx for your reply.
yes, without acceleration it's working fine, yes i turn it of as you showen on the prtsc.
maybe the problem is the version of ansys, before i was using 2019R2 and it was working rly well, now i recive a lot of errors using gpu accel. when i will have time i will instal wb 2019r2 and see if it works well.

[Ashish Khemka]

Hi Filip,

 

SIG$SEGV is short for signal segment violation. Technically, it is described as an incorrect use of pointer or a buffer overflow (memory problems). It is a bug, whenever it happens, but it is difficult to relate the cause to any one particular issue. Based on previous call records, it has happened in the past with distributed solver and rezoning, but is not limited to these applications. Using GPU may be causing it. The two errors indicated apart from segment violation are also related to GPU.

 

Regards,

Ashish Khemka