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.
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.
Maintaining and growing any kind of platform becomes a whole new ball game when "what are its specs" is replaced by "will it run my apps?"
In many respects maybe, but which aspects matter for success is highly contextual, and some just didn't really matter for the general public. Is the system in protected mode? Does not really matter during that era. What did matter however, was resource consumption. Maybe for speed of legacy programs OS/2 1.x targeting only 286 was not good, compared to even Windows 2.1x which had Windows/386.
On the memory front, OS/2 1.1 requested 3MB of RAM. Windows 2.x/386 requested 640kB. Windows 3.1 requested 2MB (or even just 1MB in standard mode). OS.2 2.0 requested 4MB (release date 92). Windows 95 requested 4MB too...
So OS/2 was arguably kind of technically inferior to Windows on many other points, and that was the points that were actually important for most people at the time.
Windows NT was "far better" (abstracting away e.g. the resources required) than both, but was out of reach of consumer system for years...
On the other hand, Mac OS on 68k was quite problematic until its end but it was not what made successes and failures of Mac during that era.
The success of Windows was certainly not only about backward compat. It was also about requirements. And price. And add to that, of course, about what was provided by default by nearly all OEMs...
Sure OS/2 was with a certain modernist view of things "technically better" than some Windows, but you know what else was even better in 92? A SPARCstation 10 :D
Microsoft had a far better developer roadmap with "32 bit protected mode with just a recompile." They sandwiched OS/2 v2/3 from the bottom and top. When memory prices dropped, the period when OS/2 had a significant hardware cost advantage over NT was rather short.