Not quite, containers will still share your core resources so I don’t think they’d help much here. You can limit them, but given we don’t know what the problem is there’s not much to limit.
Personally, I use this GNOME extension to keep track of my system resources. I’d advise to try something similar, or even just leave System Monitor running in the background but take careful note of CPU/RAM usage and most notably disk I/O usage (which can often be ignored but can cause problems).
Also, after a force reset, try journalctl -b-1 -e to see the last things that were logged before the poweroff.