Worthless post, very poorly researched and poorly written. I have checked your tasks, you haven't cheated anything - you received zero credits for those failed tasks which your faulty machine thrashed.
On the other hand, you managed to compute 24 valid CUDA PPS Sieve tasks and your RAC climbed a little because of that. PPS Sieve tasks are short but yield most credits (proportional to average runtimes) because you cannot discover a new prime number by crunching Sieve tasks, you are just doing 'preparation work' for LLR applications (which are more demanding and which can indeed uncover a new prime).
Posting poorly researched articles like this is usually the quickest way to get flagged. Join our Slack, we have a channel there called 'crunch-tinkering' (dealing only with BOINC crunching), you would get plenty of info there for a quality Steemit post.
SO if i keep crunching through prime grid with all these computation errors it will not be a peoblem right.
It is a problem, you are thrashing good tasks which have to be resent then, wasting resources. In your Primegrid account, choose to receive only PPS Sieve tasks and you'll be fine.
And change the title of this post, if it's not too much inconvenience, because cheating is an ugly word, usually associated with FUD and everything is working as it should in this case.
You should look for answers / ask on PrimeGrid forums. It's better not to get errors.