If you could post the error from the session that crashed, this could point to a clue as to why it crashes.
The command below will print the errors from the previous session so has to be run after you experience issues after rebooting.
journalctl --boot -1 --priority=err
A safe way to reboot when experiencing issues if you are not allready doing this 
It is possible to switch to other drivers, @jim1112 pointed to the settings manager, there is a option to change drivers in hardware detection to .