"... the techniques that George used to prove that his computer based proof was correct happens to have direct application to a set of tools that we give to people that build PC peripherals..."
I know MS uses Prefast (http://msdn.microsoft.com/en-us/library/ms933794.aspx) to improve driver quality. I'm not sure what other verification/analysis techniques they use, but it's not too surprising that a technique developed for efficient automated theorem proving would be applicable to efficient software verification.
To say that doing this is solely responsible for "banishing the BSOD" is irresponsible and misinformed in a few different ways, of course.
SDV began its life as a project called SLAM. This page has documentation on SLAM, academic papers, etc. http://research.microsoft.com/en-us/projects/slam/
I'm not sure of the exact connection highlighted in the article, but this work builds on decades of work in automated theorem proving. It's exciting that now these techniques are used on real code.
(Disclosure: the SLAM & SDV authors are colleagues of mine at Microsoft.)
It isn't because of merely better testing that Windows 7 / Vista are much more stable than previous versions of Windows, there are fundamental architectural changes. On modern versions of Windows if even your video driver crashes it will be restarted and instead of a BSOD you'll just get a system tray notification.