To view parent comment, click here.
To read all comments associated with this story, please click here.
Why should bad drivers bring down an entire OS? And wasn't this one of the much-touted improvements of Vista, the fact that the entired driver stack had been re-written from graphic to sound card drivers?
I honestly find it amusing the kinds of excuses some of you can come up for the lack of quality assurance and proper design principles in Microsoft products.
Why should bad drivers bring down an entire OS? And wasn't this one of the much-touted improvements of Vista, the fact that the entired driver stack had been re-written from graphic to sound card drivers?
So maybe it's not a graphic or sound card driver? Honestly, I don't know of any OS that can stand up to shitty drivers. Sure, the entire OS might not go down in all cases, but generally, it has some sort of unpleasent side effects. For example, if the entire screen goes blank and I have to kill the desktop envrioment, that's not a whole lot better than an OS crash, especially when it takes longer to boot back into the DE than it does to reboot the Windows OS.
And for those who are complaining about the price, the problem isn't that it's too expensive - the problem is you can't afford it 
One of the main points with a client-server based OS is that no device driver should be able to pull down the OS.
It is a very typical reaction to blame everything on anything but Windows.
If it is an out-of-the-box driver as I suspect, then it also is certified. Should a certified driver behave this way ?
It's a fairly safe bet (given that he's including drivers in this), but just not a very useful point.
Let's look at it: 90% Windows Vista Installs don't BSOD on boot. Lots of virtual-memory/SFC etc. protection is built in to prevent rogue software from screwing up the install. so it's likely to be one of:
1) faulty ram (hardware)
2) Dodgy driver (driver)
3) File Corruption (hdd = hardware)
4) Dodgy bios (hardware)
5) Hardware with bad Id (hardware)
6) Not enough ram and no pagefile (harware - kinda)
It's not very likely to be a core vista problem directly. It could be attributed to fault-intolerance though I guess.







Member since:
2005-07-06
I guarentee you it is the hardware (even if it is the drivers that are causing it).