First of all, when a driver crashes, that's a security risk, and so drivers should never, ever, crash. Others have pointed this out. It's an OS or driver bug you ran across, not a firefox one.
Now, to the other question: why does only firefox trigger this bug? There's a multipast answer to that:
- Most apps use the old 2d graphics api's, which have been tested thoroughly during the driver development. This includes gimp and photoshop, which don't actually use accelerated graphics, but are normal windows apps no different from e.g. microsoft office.
- Most games share one of a handful of separately developed game engines, because writing a game directly on top of the low-level driver is too much work. Game engines are tested endlessly to ensure they don't trigger any bug in the graphics hardware. Ghost recon's engine was actually developed in close cooperation with nvidia.
- Firefox 4, like IE9, uses the Microsoft Direct2D api to support accelerated graphics. This api is new and uses the existing graphics drivers in ways they didn't foresee. That's why you trigger driver bugs with firefox 4 and not with any of your other software.
Finally, is it a good thing these browsers are using accelerated graphics? Sure, it's a very good thing. It means we're all getting faster web browsing. Once the driver bugs get shaken out by these new api's, we'll all have a better experience for it.