Help !!! error access violation - code c0000005

[stipsrl]

Hello,
I am having some issues with PMill - ERROR: Access Violation - code c0000005 (first/second chance not available). Not all my projects crash, but most of them do. I am attaching a pic regarding the error I get along with the error log, if anyone has ever had this issue and knows a fix, please let me know. 

 

Greetings

[lokesh.kalia]

Hello @stipsrl 

I'm sorry you are seeing these errors. From the information provided I cannot tell what the problem might be. If you could you give me the error report number from one of the crashes I'll be able to investigate further.

Thanks.

[stipsrl]

hello, thank you for the answer, this is the report number: 335940326.
if you can give me an answer because the situation is becoming more and more critical

[lokesh.kalia]

Hello @stipsrl .

Thanks for the report number. Are you interacting with fields on the Start Point and/or End Point pages of a toolpath strategy form? - We are aware of an issue when interacting with these fields directly (i.e. by clicking in a field and setting a value) having re-raised the form. This can result in a crash.

Is this your experience too?

If so, I think you could avoid the crash by setting Start Point and/or End Point values via commands instead.

Alternatively, you might prefer to roll-back (uninstall) the  latest update and revert to PM 2023.0.3 instead.

A fix for this problem has been implemented and is intended for PM 2023.1.1.

[stipsrl]

hello mr.Lokesh,
thanks for the solution you recommend, I assume it refers to version 2023.1 because we have that version, we have seen that the problem occurs with projects created with CATIA, I don't know if it could depend on this, now we are working with projects created with CREO and the problem hasn't recurred so far.
thanks for your time .

[lokesh.kalia]

Thanks @stipsrl . You are quite right, my comments were with regards to PM 2023.1 . I have amended my post accordingly.

I'm surprised that the occurrence of the crash would depend in that way, but I'm glad to hear you have found a way to  overcome this problem. 🙂

[stipsrl]

Abbiamo eseguito roll-back alla versione 2023.0.3 e per ora il problema non si sta presentando.

Grazie