Yes, there is a very logical reason...I will try to explain it.
In ComputerLand, there is a term used..."corruption"...which simply means that some facet of our computing aspect...has become damaged or gone awry.
Normally we refer to "file corruption" but there is also file system corruption and RAM corruption. Amy one of these items incurring corruption...may cause a minor or a major irritation for us users. We shall focus on file corruption, since that seems to occur most often and is more easily dealt with.
When a file suffers damage, there is no report from the file itself in many cases. But, sooner or later...Windows will become aware that something is not happening as it should...and it will create an error or an error message. BSODs are probably the most obvious error messages, while less obvious error messages can be found in Event Viewer.
This is all routine...there is little that any user can do to prevent file corruption. The mechanics of just how the damage came about...is not understood, nor does it need to be understood. It's the effect on the system that is important, what is important is how we can deal when we suspect/know that a given file is damaged.
The basic cure for such...is to remove the damaged file and replace it with an undamaged file. That's why the typical cure for "corrupt drivers" is remove/replace.
Which is what you have done by uninstalling the old driver...and replacing it
Some material on file corruption that attempt to explain what I consider "unexplainable":
Causes of Data Corruption - http://ezinearticles.com/?Causes-of-Data-Corruption&id=817785
Data corruption and loss causes and avoidance - http://www.thexlab.com/faqs/datacorruption.html
Edited by hamluis, 06 December 2012 - 10:48 AM.