Windows 9x had very similar issues, and even early versions in the Windows NT series weren't altogether free of them. The viable fix was to hit CTRL+ALT+DEL and force close the misbehaving application.
Wasnt Windows famous for BSOD?
Hence why nowadays all drivers have to be certified, and graphics drivers are again in userspace.
You have to remember the barrier between kernel and userspace was very porous, applications had their own address space but e.g. DLLs were projected at identical addresses and shared some resources. Kernel memory was mapped in userspace, if I'm remembering it right. Basically, apps had their own cubicle, not their own apartment.
Eventually NT 4.0 became a better option, if you could get all the required software and weren't doing DOS games.
The main selling point of OS/2 was supposed to be that it had preemptive multitasking and protected memory, which was supposed to make it much more stable compared to the (constantly crashing) Windows 3.0/3.1.
The problem was that the Workplace Shell (the GUI) had some sort of single message queue that could be blocked by a misbehaving program. This would cause the GUI to hang. While it was true that the system would continue to task switch, and you could even telnet into the machine after this happened, from the console, the system was completely unresponsive, so it was functionally equivalent to the OS crashing.
IBM as an organization didn't seem to understand what features were actually relevant to normal users and prioritize them. It could do a bunch of things like smoothly multitasking multiple DOS apps, that were technically impressive but not that important to users.