>>35
If you had studied a bit of the NT kernel, you'd known its not a micro kernel design, but something of hybrid design. Driver modules, subsystems and the kernel itself run within the same memory space, there is no real separation, a driver could easily crash the entire system if it were buggy, however there design methodologies which can be used to construct stable drivers, and the kernel provides the needed APIs to build such drivers reliably ( yes, you can do it without them if you really wanted, nobody is forcing you to use anything ). The Windows kernel is much more complex in its entirety than the linux kernel, due to the large amount of extra functionality they need to support. Drivers are usually loaded dynamically, and could be seen similar to linux's LKM's.
Windows' services are not related to the kernel directly, they're merely usermode applications running with elevanted priviledges, providing various system services, not much different from *nix daemons.