I've used c4d as my main tool for 25 years now and have been using octane as my primary engine for the last 6 years. I can tell you that I've had more crashes because of octane in my first year of use than I'd had from c4d (including betas, alphas and other plugins) for the first 20 years. But we've stuck with it because the productivity gain, render speed gain and image quality gain over standard render was exceptional.
There are certain actions and areas you learn to save before doing because you know they have a high chance of a crash (delete unused materials whilst the asset manager is open, pressing undo before the last undo has finished when live view is enabled), But Smolak is right, it can and absolutely will shit in your bowl of cornflakes whenever it feels like it. You can change the diffuse colour a thousand times, but the next colour change will crash it. You can kill it applying materials, navigating, animating. Heck Ive had octane crash whilst my computer sat idle and I went for a piss.
The wrong drivers will crash octane
The wrong windows update
The wrong pcie slot
the wrong pcie riser cable
The wrong gpu clock speed (we had a 1080 that when the OC edition cards added that extra 50mhz, they would all die)
Now for redshift, I honestly haven't put enough hours into it, but even if its way more stable than octane, that still leaves it as potentially causing loads of crashes.