Vista Blue Screen after Successful Boot Camp installation (32 and 64 bit)

Question

OK so there are a number of people with issues relating to the BSoD after a successful (or not) implemetation of Bot Camp and Windows XP and/or Vista. One of the identified problems relates to the NVIDIA GEforce 9600m GT display driver which crashes out AFTER windows performs its update routine.
Having removed and installed the partition (to ensure a clean install each time), the inescapable conclusion is that the NVIDIA driver is to blame for the crash dump, but it is one of the many MS updates that is the root cause of the failure. If you do a clean install of Vista 32 or 64 Ultimate and install the Boot Camp 2.1 (build 1256) and DO NOT allow updates, the system is not only stable, it runs like a train!
I have Contacted AppleCare about this (as my new MBP is only a few days old) and they have not even heard of the problems. NVIDIA have obviously got issues with something as the driver has been updated to a BETA on their web site, but this will not work on a Mac as it cannot seem to find the hardware to allow the update to complete.
If (like me) you have bought an MBP for support issues for both Mac and Windows users, this is a showstopper and one that is about to cause me to ask for my money back. So far, the nice shiny and new MBP is back in its box pending a 140 mile trip back to Exeter from whence it came.
SHARK!

Answer 1

Boot Camp was a response to public challenges at the time to see who could find how to install Windows on a Mac - which is totally okay thing.
Then you want Apple to do more than any normal PC vendor selling a laptop where people have to do things like deal with BIOS, drivers and all the things you have had to deal with, for Windows.
I'm not disagreeing, let alone arguing, I agree that hardware abstraction layer type stuff Apple would need to do. But I don't think Apple needs to do more than get Windows installed. Drivers, AV, and all the stuff that comes with Windows doesn't change. But it should not BSOD when you install something you are told you need.
I wouldn't be surprised though to see Windows 7 eventually support Apple hardware out of the box so to speak.
Cookie cutter answers are part of today's customer experience "level one" is no level at all, but a lot of times - and it takes a lot of work - to translate feedback and problems into "cook book" before you get to the troubleshooting (level 2 and above).
Which is why I read sites like MacIntouch; subscribe to MacFixit (tons of articles on a CD along with shareware). And books.
Nvidia has terrible drivers in OS X on the Mac Pro (workstation) while ATI has had very good drivers and OpenGL support.
I prefer to have more choice and freedom when it comes to drivers. As for engineering and how things get qualified (use to see even SCSI hard drives had to be qualified for both the OS; the controller to be used; driver version; firmware; etc).
What I see is the first shipped BIOS/EFI firmware on any device or system is not the one you want.
Back in the 70's I was introduced to "bleeding edge" but we would get premiere on-site support if we were willing to install, adopt, some new IBM service, software/hardware. And sometimes we were there on Sunday on holiday weekends.
One person just could NOT after doing everything under the sun, get Adobe CS4 to install on their new $5000 Mac Pro 2009. Got a new system, worked perfectly.
In 2008 Early Mac Pro, most all systems would freeze on wake from sleep. Took two months before an EFI update was issued that cured the problem. There is/was also a problem with "inrush current" and PSU.
I had Blue Screen with Vista. Repeatedly.
At first I thought it was a new MICROSOFT 4000 keyboard.
Later I wondered if it was my Apple OEM Nvida 7300GT (and some are failing but it worked in OS X) so I bought 2nd, a PC 8600GTS.
And pull 3rd party PCI Express controllers (FW800, SATA 1x, SATA 8x cards).
Came away and thought "oh, it was the 3rd party card" when that seemed to work.
Around the same time I had bought a new WD Caviar 750GB SATA drive.
It was that drive that would cause problems with Vista after the install.
I thought it was something in Microsoft Windows Update that was causing my personal ****, not my equipment. And MS for their drivers. Somebody else's.
And mind you, I would go through install half a dozen times, try installing Boot Camp before updates, after updates, not at all, add AV software.
I finally -- after a full year -- learned a lot (don't learn from things just working and I still say it has always been "Plug and Pray" PnP ) things work. I know the frustration and aggravation and the wish that things were different somehow.
The BSODs that I got were not from Apple Boot Camp. I even ran my system w/o Boot Camp for six months. And this time, with Win7, everything worked fine, wake, sleep, networking, no need for Apple drivers. At all.
I hang out on a forum where people build their own, X58 board, Intel Core i7, eVGA graphics. And how to get even DDR3 to work, and then how to get the most out of and push it to the extreme, then throttle back a notch.
The nice thing about that is you learn from it, like you do from racing and sports, to build a better mousetrap.
Nvidia is bleeding. Even as they and ATI want to stay on leading edge. Intel is contracting (even as they have their best cpu technology ever coming out) and costs that should go into R&D may be harder to "justify" or all the prototype programmers engineers and testing labs. Everything is more commoditized than ever.
Bottom line: I have Leopard 10.5.6. It has Boot Camp 2.1.2 version, later than the 2.1 download. And there has not been a single update posted online. But my original Leopard DVD 10.5.0 has the SAME contents packaged as 2.0 as were in the 1.4 Beta. I spend $129 for a new DVD to get the latest drivers. Make sense?? of course not.
Oh, and my Mac with 64-bit hardware, cpu, the EFI BIOS is 32-bit so no official support from Apple to install BC 2.1.2 or use Vista 64-bit. Snow Leopard will be 64-bit kernel, require and enforce 64-bit drivers. Should be interesting. Because technically, and logic, would say I don't have a true 64-bit BIOS environment.
Got an iMac? not supported with 64-bit. MacBook 2008 had 64-bit support, but not the "Late 2008" there you need MacBook Pro. And yet everyone wants to address more than 2GB (Apple EFI32 allows access to 3.3GB on some, 1.9GB on others, and in my Mac Pro? limited to 1.9GB memory in Windows.... so you know I don't want to run a Xeon workstation in Windows 32-bit.