Earlier quoted context omitted.
No it's rock solid underneath. The TCP stack hasn't been a 32-bit driver since XP. NTFS has been modernised already: http://en.wikipedia.org/wiki/ReFS The registry is fine - it's people pissing around in it that break it. Win32 - haven't touched it for years. Driver model: not my problem. Mavericks is a crime compared to windows 8.1. I use both, regularly. It's virtually impossible to use efficiently with a keyboard…
I should've been way more clear about my gripe with the Windows TCP/IP stack. Why the hell does the TCP/IP stack eat itself? No other OS I've ever used has the nuttiness that is netsh winsock reset as a regular troubleshooting step when diagnosing network connectivity issues. I was long under the impression that the reason why that kept happening was that the NT kernel didn't have a robust TCP/IP stack of its own and…
USB drivers, sound drivers, printer drivers, web cam drivers, etc etc, are all using user-mode drivers since Vista. They cannot crash your system. Similarly, graphics card drivers use a special model that means they can auto-restart if they were to crash; which as it happens is exceptionally rare and often resolved by upgrading the driver.
I've used Windows ever since it first got a Registry (95) and it's never corrupted on me, ever.
I lol'd at the "or improving the driver model?", as though there is ANY mainstream OS out there with a better more flexible and stable driver model than Windows has today.
You've basically dug up a load of non-issues, fictional issues and historical issues and portrayed them as relevant issues in the world of Windows today. They aren't.