Verify: Fatal User Error 1002

[Jobnt]

Deadlock due to omp_set_lock being called on lock already owned by thread

Been getting errors in verify that didn't happen before. Specifically when I turn off Stop Conditions "collision" I get the bottom error, then today I got the top error with it. 

2020.

[byte]

1 hour ago, Jobnt said:

Deadlock due to omp_set_lock being called on lock already owned by thread

Been getting errors in verify that didn't happen before. Specifically when I turn off Stop Conditions "collision" I get the bottom error, then today I got the top error with it. 

2020.

It's a caught exception or error related to OpenMp which is a commonly used library for multi-threading & loop based parallelism,this information won't really help you...

 

maybe check for recent windows/.net framework updates, I remember Simulation for 2020 going on the fritz after updates often

[Jobnt]

8 minutes ago, byte said:

It's a caught exception or error related to OpenMp which is a commonly used library for multi-threading & loop based parallelism,this information won't really help you...

 

maybe check for recent windows/.net framework updates, I remember Simulation for 2020 going on the fritz after updates often

I updated .net framework a few months ago and haven't done any updates since. I started noticing the bottom error when I turn collisions off in verify.

[byte]

Disabling collision checking doesn't create the same error for me

[Jobnt]

10 minutes ago, byte said:

Disabling collision checking doesn't create the same error for me

It never did for me either until this week.