This might be redundant, but have you checked your event viewer logs?

If it takes down the whole machine, there's no amount of logging in blender that could help, best to follow @Asher (ThatAsherGuy) 's advise and check the system logs

I checked multiple times, but there are no application hangs or errors in the event viewer. Even after system freeze. The only thing I now have is an error, that I caught using OBS. The system console closes after displaying the error a millisecond later :-)

Launch Blender from the system console to keep the console open after it crashes. Use something like Cmder if you want to manage multiple consoles simultaneously.

This might be a Boxcutter-specific issue, and/or there are multiple bugs at play.

Edit: Verify that you're running the latest version of Boxcutter (714.14). This is a known issue with earlier versions, and I can recreate the crash you've described with 714.8.

Thanks Asher, it seems to be the debug command (-d or --debug) that causes the crash with Boxcutter. Funny that some of the nightly builds seem to work with the debug command :)
When I don´t use the commandline arguments, Boxcutter works as expected.