What is the actual panic? Can you recover/get a stack trace? You should for sure try to troubleshoot the error. It is extremely unlikely that more hardware would fix a concurrency problem. Here’s a relevant Stack Overflow question:
You could try a sync.Map (depending on your use case):
Indicates that some map reads and writes are not guarded by a mutex.
You may want to try replacing the map with the updated concurrent map in 1.24rc2 or check all of your map access and ensure that it is guarded with a rw mutex.