Potentially Serious bug with RPCS3

I've encountered a very strange and worrying bug with RPCS3 itself that might actually do harm to someone's computer.

I was in the middle of compiling an SPU cache for a game, when it crashed due to a game-specific compatibility error.  All of a sudden, my screen went black for a good 30 seconds, displayed some random corrupted-looking colors, then both my onboard Intel Graphics and my NVIDIA GTX 1080 got disabled and were giving Error 43.

I've never seen RPCS3 do this before, and I found out that disabling and re-enabling the GPU's in Device Manager fixes the problem.

I don't think any logs were saved from this, and I don't feel safe trying to re-create the issue.  But given that I hadn't seen this happen before, I don't know if it has the potential to actually ruin computers.  I was worried it fried my NVIDIA card or something, because a quick Google search said that Error 43 can be caused by broken or damaged hardware.

Just wanted to report this.  I wish there was a way to provide more information.

Well just be careful man. If you fry your stuff that's on you. Say you have a $2400 computer and something fries, you got no legal recourse (like, you can't sue the dev team, especially since it's open source). You'd be up shit creek without a paddle (or a PC).

Stay safe.

Never seen or heard about such issue, no idea how to reproduce this

If it helps, the game was Grand Theft Auto V. I wanted to, as hard as it may seem, complete an SPU cache for the loading screens and the intro level, or as far as I could get. I wanted to see how it was affected by the new FIFO optimizations.

The error that RPCS3 gave was something like "Error: could not create function" or "Error: could not compile function". That error made the computer lock up, and attempting to close the emulator caused the problem. I hope that makes it easier to try an reproduce.

I won't launch Grand Theft Auto V again until I know that it can't cause physical harm to computers.