This utility installs the Intel Chipset Driver. This driver also resolves the yellow exclamation point error Device Manager Exclaimation Point Error that may appear in Device Manager as 'SM Bus Controller' which indicates that a driver is not installed for that device. This zip archive contains the files needed for installing the Chipset driver. If it has been installed, updating (overwrite-installing) may fix problems, add new functions, or expand existing ones. Even though other OSes might be compatible as well, we do not recommend applying this release on platforms other than the ones specified.
INSTALLING THE SOFTWARE IN INTERACTIVE MODE:
- Verify that all system requirements have been met.
- Download and unzip the archive.
- Run the setup program.
- You will be prompted to agree to the license agreement. If you do not agree, the installation program will exit.
- Upon successful installation you will see a screen listing Intel Chipset Device Software as installed. You can view the instalation logs by clicking on View Log Files in the bottom left-hand side corner.
INSTALLING THE SOFTWARE IN SILENT MODE:
- Verify that all system requirements have been met.
- Download and unzip the archive.
- Run the setup program for silent install: SetupChipset.exe -s
- The utility will perform the necessary updates and record the installation status in the following system registry key: HKEY_LOCAL_MACHINESoftwareIntelINFInst
- If the utility was not invoked with the '-norestart' swith, the system may automatically restart if the setup was successful.
- NOTE: If prompted, the system MUST be restarted for all device updates to take effect.
- To determine whether the install was successful, verify the 'version' value in the registry key
- In Silent Mode the utility will not display the license agreement. When using Silent Mode the license agreement, license.txt, will be placed in the following folder: %ProgramFiles%IntelIntel Chipset Device Software
- Please read this agreement.
About Chipset Drivers:
Windows OS automatically installs a generic driver that allows computers to recognize basic motherboard functions. However, to make use of all board components, appropriate chipset drivers must be applied.
If you install this package, the system will receive related information regarding the chipset. Also, this step might improve compatibility and bus transfer speeds, add various changes for sleep state behavior, power saving functionality and others, or include support for new features.
To apply this release, simply make sure your system configuration is supported by this package, get the file, run the available setup, and follow the on-screen instructions. Bear in mind that installing inappropriate chipset drivers can cause computers to malfunction.
In addition to that, do perform a system restart after you have completely applied the present release so that all changes take effect. Despite the off-chance that other OSes might be compatible, we do not recommend installing any software on platforms other than the highlighted ones.
That being said, check the supported platforms, click the download button and apply the chipset driver. Moreover, don’t forget to check with our website as often as possible to stay up to date with the latest releases.

The problem may very well be solved and I can honestly tell you that I have never seen anything like this before.
So instead of running check disk, I thought I would give something else a shot first. The drive that I had installed was my back-up in my other PC and had been fully functional so I didn't necessarily think that was the issue. I had a brand new 1 TB drive that I had planned to use as my primary back-up in this PC so since it was new I thought I would give it a shot to see if it would recognize that drive.
So I pulled the old drive and attempted to pop in the new drive, but it wouldn't go into the sata data cable. After a close review it appears that the plastic protector on the sata data cable connection on the drive broke off into the data cable. I assume that I had a loose connection and that is why it would occasionally recognize it.
Luckily, I just happened to have another sata data cable on hand and tried it with the new drive and not only did it recognize it, it is installing right now.
So I just partitioned that drive. Not my preferred method, but since the other drive appears to be useless now I guess this is the route that I am going to have to take. Maybe I will buy an external for my back-up in time.
I really appreciate the help. It was quite a learning experience for me.