Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actualsamoth

Posted 10 November 2012 - 07:51 AM

The computer crashing is something that should not happen, ever, under normal circumstances.

A bug in the installer should at best make the installer crash and Windows showing a "Error 0x0000000C" or "Program has stopped responding" or similar error, but that is unlikely to happen. Missing access rights could make the install fail, but should show an error alert, but should not even crash the installer (I'm boldly assuming that the nVidia guys check for at least such very obvious error conditions).
The installer used is not something that's written for only one driver, but a tool that is reused many times for many driver revisions, and something that has been thoroughly tested both before releasing it and "in the field" by millions of users. It's extremely unlikely that it has any show-stopper bugs.

A driver bug (endless loop) could in principle of course cause the computer to bluescreen, but only after the driver has been installed and the computer was restarted, not while the installer is running. At least, this is in principle possible under Windows XP (in later versions, it would only cause the desktop manager to kill and restart the driver, the computer should not crash). But even if such a thing is in principle possible, it is extremely unlikely because drivers have such a huge install base (which is a gigantic field test). It is nearly impossible that such a thing goes unnoticed for longer than a day or two.

The by far most probable reason is faulty hardware. Black lines are another such thing that shouldn't happen except if the hardware is faulty. You're not overclocking, are you?

#1samoth

Posted 10 November 2012 - 07:50 AM

The computer crashing is something that should not happen, ever, under normal circumstances.

A bug in the installer should at best make the installer crash and Windows showing a "Error 0x0000000C" or "Program has stopped responding" or similar error, but that is unlikely to happen. Missing access rights should show an error alert, but should not even crash the installer (I'm boldly assuming that the nVidia guys check for at least such very obvious error conditions).
The installer used is not something that's written for only one driver, but a tool that is reused many times for many driver revisions, and something that has been thoroughly tested both before releasing it and "in the field" by millions of users. It's extremely unlikely that it has any show-stopper bugs.

A driver bug (endless loop) could in principle of course cause the computer to bluescreen, but only after the driver has been installed and the computer was restarted, not while the installer is running. At least, this is in principle possible under Windows XP (in later versions, it would only cause the desktop manager to kill and restart the driver, the computer should not crash). But even if such a thing is in principle possible, it is extremely unlikely because drivers have such a huge install base (which is a gigantic field test). It is nearly impossible that such a thing goes unnoticed for longer than a day or two.

The by far most probable reason is faulty hardware. Black lines are another such thing that shouldn't happen except if the hardware is faulty. You're not overclocking, are you?

PARTNERS