I would like to share with a nice method securing our work environment against sudden crash of OS.
Of course we should do backups both our work and OS but restoring take a time and can be tedious (in case of OS).
But there is other way on many PC (I'm not sure if it is also related to MACs).
It is surprisingly for me very underestimated and probably also missed. Probably because its name and associations. But in fact the idea behind it is taken from world of servers and virtualization environments.
It is related to feature in BIOS of many 'modern' (I guess not older than 5-6 years) motherboards.
It is named often as 'overclock profile' or 'game profile' etc...
While PC motherboard manufacturers probably created it for reason suggested by its name in fact it offers much more... It lets to define different hardware profiles for the machine. What means you could have on the same computer 2 different OSes (2 separate disks needed) with different hardware configurations : daily used and standby OS which can be started just by switching profile in BIOS. They cannot see each other so standby OS is not sensitive to any daily OS crash or virus infection. The secondary disk from profile 2 is not even seen in profile 1 (if it is intention and properly defined of course).
The most important advantages here is you can in case OS crash just reboot to BIOS, switch profile and got in minutes working machine again. Also you can use the secondary profile for less serious applications or for sharing the same machine with other person (2 different engineers can have 2 different setups on the same machine), etc...
Preparation is simple. Need second disk (size must match at least size overall used by OS (usually 2 partitions). Next clone OS disk to new disk. Then in BIOS define 2 profiles where 1st cannot see disk 2 and 2nd cannot see disk 1, rest disks would be shared (of course sharing disks gives way for viruses). Or any other combinations proper for an application as needed without shared disk, etc What ever hardware can be disabled in BIOS...