@sergeewish thanks for getting in touch with us. I understand you are frustrated.
Yet still, first off, it is normal for any development team to prioritise issues that they can actually reproduce and issues that have sufficient proliferation within a Community - there’s nothing strange or peculiar about this.
Do not take this personally. As far as we can tell - this happened only to you within of our Discord Community server.
Now with the above aside.
- The initial error you’ve been facing suggests it may be a hardware/platform specific issue indeed given the software worked fine once you moved your HDD to another computer.
- the
CRITICAL ERROR. Please report to Wizardsthing. If you know the error might happen again (as it seems to be happening within of a boostrap sequence so likely it’s to happen again) - make the window wider - you should see the axact place in code where this is happening. It might help us investigate this further. - I’ve noticed that the openCL kernel you’ve been using does not match the expected fingerprint. This might be causing some binary issues at GPU->CPU data exchange levels
Also. @sergeewish you seem to be quite tech savvy so I let me invite you to this: https://talk.gridnet.org/t/how-to-prepare-gridnet-core-crash-reports/
Once you submit a crash report we would have a precise outlook on what’s happening under the hood.
There are hundreds of live nodes at any given moment, including ours running 24/7 which is all verifiable and as you’'ve probably noticed - nobody else has been facing this.
Keep us posted. And yet again remember - if you are the only person facing a certain issue you cannot expect the entire development team to focus on this within 24 hours.