Hello. I have a new motherboard installed on my system but realized that if I boot my machine up the chipset drivers for my old motherboard will get loaded before I have the time to uninstall them prior to installing the new ones.
My question is, is there any potential risk of damaging the motherboard while using the wrong chipset drivers, or is claiming so only misunderstanding the workings of a computer system?
So I get it one could somehow damage his hardware that way. Thanks for the answer. I'll get myself one of those UBCD4Win builds so that I can safely recover my files before reinstalling Windows with new drivers.
I've been dissatisfied with ahem's answer. It is not quite informative enough for my own taste. So I've Googled a little bit, and found two almost-contradictory pieces of info:
Ideally, if you install a new motherboard, you should start from a clean slate and build a new OS installation.
When I have not done that, I usually see a lot of "found new hardware" messages as Windows boots the first time. The chipset drivers from the CD aren't a problem. For those, you check Device Manager and try to clear all the "?" and "!" symbols.
The usual result is a working system with bits and pieces of unused drivers scattered over the hard disk.
What I do is get a new hard drive for the new installation, build the OS on the new drive, install the apps on the new drive, then plug in the old drive to transfer the data files.
Unfortunately, there is nothing wrong with ahem's answer. Sometimes the answer is "Maybe" or "It depends".
If you notice in the "wordpress" link, most of the problems that people caused were from bypassing the OS and directly writing to the hardware. When you do that, you had better know what you are doing because you are bypassing all of the protection the OS provides.
I can zap one byte on a hard drive with a disk editor and make that drive unusable to Windows. A disk editor is a program that enables you to write directly to the disk surface. I can overwrite the Media Descriptor byte (Track 0, Sector 0, Byte 3, I think) to convert it to a Unix disk and Windows will not be able to reformat it.
Just so you know, booted without tapping F8 with new MOBO installed, BSOD; booted in safe mode, BSOD too. So, it seems the need for me is whether to do like you, jsc, said, or better, to boot using UBCD4Win, but only if one had XP previously installed, as the file system can get damaged otherwise and you can lose precious data. If you have an extra HDD in hands but no UBCD4Win, though, do it like jsd; that doesn't fail!