"Your PC encountered a problem and needs to restart." - Round 2.

Glad you explained it :)


Another 'going back to', this time because I'm having some issues with gathering information about the crashes to find some patterns.

No. I entirely restored my system to its pre-crash state using Macrium system image backups after each crash. I always saved the crash data (dump files, etc) before restoring my system, though. As I restored my system to its pre-crash state each time, I eliminated any possible operating system damage caused by the crashes themselves.

What you're trying to do is exactly what the BSOD is meant to do, preventing OS corruption and/or personal data corruption.
The BSOD occurs when it sees that something is breaking rules in the kernel, it saves the data in the RAM so others can have a look at it and safely shuts down the system to prevent (further) corruption. In certain crashes there is already corruption, it is only caught when the corruption is being accessed, but userdata corruption and OS corruption is rare to occur.
The crashes do not cause any damage to the system, if they somehow do then there is an entirely different problem with the OS since the crashes are meant to protect your system.

The risk of important data being removed when restoring to a date before the system crashes is quite high, I ask you to not do this anymore while troubleshooting.

I noticed 0x124 crashes, they are mostly solved by patterns. The 0x124 minidumps mainly save the reason why a BSOD was called but not the cause. With patterns we can identify possibilities for causes and solutions to resolve the crashes.

I've been unable to find proper onces, I need more data from around the time of the crashes.

Mainly the data from event logs

The event logs you still have is collected by the DM Log Collector, I've already gone through it.