Random BSOD's with either 156 or 292 as BugCheckCode

Thanks, I will try. Do you recommend using the computer as normal or can it sit idle and still get the same effects?

The computer can be used as typically used while testing with the understanding that there will be unexpected shutdowns and restarts.

I'm still not sure how to change the log language - I suspect a full reinstall of Windows might be necessary if the language pack doesn't cover it?

If the problem is related to software and drivers that should fix BSOD too.
If the problem is related to hardware BSOD should reoccur.
Testing hardware including stress testing can be performed to find malfunctioning hardware.

I understand. I was merely asking if, to be able to change the language of the logs, it will be necessary to reinstall Windows as it seems that the language pack did not change this to English, thus rendering the logs unscannable to English language tools.

If Windows is reinstalled:
a) it requires new drivers and applications > this may fix BSOD related to software drivers and hardware drivers
b) it typically rules out problems related to drivers (software and hardware)
c) if BSOD reoccur then hardware can be worked up
d) allows logs to be in English so scanning can be performed

Okay. I've resolved to do a complete reinstall of Windows in English (US) to be able to better troubleshoot. Interestingly, I spent around 6 hours on WoW today with no crashes, but within 15 minutes of loading up GTA V there is one. I took a new log on it just to be safe, as I'm not sure if any of it carries over if I reinstall, and here's the link (still in Swedish probably but still). DESKTOP-E6C97SD-(2020-06-06_17-17-22).zip - Google Drive I will then try to increase the stress testing and see if it still crashes.

The last dump file was from 5/16.
So there were no new files to debug.
The logs were not yet in English and could not be scanned.

It's now been more than a month without a single crash, after I did a full reinstall of Windows. I'm sure I could trigger various BSOD's with the suggested methods, but as of right now the computer is running almost perfectly, so I don't really see the need. For now I consider the issue solved. Thanks for all the helpful suggestions!

I'm glad to read the progress.
You're welcome.