I'd be willing to bet the external service is trying to automatically determine PNP monitors so you don't have to download the proper monitor driver and colour profiles.
If it does not find it in time, it will not use the driver (just generic LCD or whatever) But in doing so, Vista itself will BSOD on a critical component not loading. If your monitor happens to be *off* or in standby mode when booting, the driver will not load. It will also remember this for the next time you boot, so you get no screen, lol.
I used to have the same problem with Harddrives that took 15 seconds to properly initialize (sometimes it would/sometimes it wouldn't) Vista will then determine that your system has changed, and will not boot up. Luckily most Bioses support harddrive timeouts up to 30 seconds nowadays.
It also used to rarely happen with DHCP timeouts and XP, it would not cause a BSOD, but it would disable the network card until you did a Ipconfig /renew.
Vista = evil BTW. ATi and Nvidia and every addin cardmaker for that matter.
If it does not find it in time, it will not use the driver (just generic LCD or whatever) But in doing so, Vista itself will BSOD on a critical component not loading. If your monitor happens to be *off* or in standby mode when booting, the driver will not load. It will also remember this for the next time you boot, so you get no screen, lol.
I used to have the same problem with Harddrives that took 15 seconds to properly initialize (sometimes it would/sometimes it wouldn't) Vista will then determine that your system has changed, and will not boot up. Luckily most Bioses support harddrive timeouts up to 30 seconds nowadays.
It also used to rarely happen with DHCP timeouts and XP, it would not cause a BSOD, but it would disable the network card until you did a Ipconfig /renew.
Vista = evil BTW. ATi and Nvidia and every addin cardmaker for that matter.
