How to Update Drivers

[Razorbacx]

I'm looking for the best way to update my Drivers as I believe that I've finally narrowed down all the issues that I've been having with Windows 7 due to faulty Drivers. I've updated my NVidia Driver, Realtek HD Audio Driver & Realtek NIC Driver. I now need to update the following Drivers and do not know where to locate them or if there is an easier way to update them without using the Deivce Manager. The following Drivers are according to third party software (Driver Agent) from the Gigabyte website are outdated and need to be updated:

USB Input Device
Intel (R) ICH10 Family 2 Port Serial ATA Storage Controller 2-3A26
Intel (R) ICH10 Family 4 Port Serial ATA Storage Controller 1-3A2
Standard Dual Channel PCI IDE Controller
HID Compliant Mouse

Using the Device Manager to search for and install updated Drivers thru the internet is an absolute waste as I've found out. In every instance Windows tells me that the best Driver is already installed, although I was able to dl and install three (3) updated Drivers that I am hoping will once and for all stop the BSOD and other error's. Maybe I'm slow or much more ignorant than I thought I was by trusting Windows to do this for me, however at this point I am open for suggestions and will be most appreciative of any and all advice.

Regards,

Razorbacx

[Major_A]

Intel Chipset Drivers
http://majorgeeks.com/Intel_Chipset_Sof ... d1667.html

Typically when I do a fresh install of Windows I install drivers in this order:
Chipset
Video
Audio
LAN/etc...

This isn't essential but I've rarely encountered an issue installing drivers this way.

Another thing to consider, when you update sound/video drivers uninstall the old ones before you proceed to install the new ones.

[Razorbacx]

Anyone know what the below error means?

wuaueng.dll (424) SUS20ClientDataStore: The database page read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 98304 (0x0000000000018000) (database page 2 (0x2)) for 32768 (0x00008000) bytes failed verification. Bit 17431 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.

I got 20 of these errors in my Event Log.

Warning 1/20/2010 3:58:34 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:29 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache
Warning 1/20/2010 3:58:20 PM ESENT 399 Database Page Cache

[hnzw_rui]

This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.

From Windows' diagnostics, at the very least, it's a corrupted sector on your hard drive. Either that or a failing hard drive. I suggest slaving the drive to another computer and doing a chkdsk. You might also want to look at the SMART diagnostics.

You know, it's quite possible all the errors you've been experiencing can be attributed to a failing hard drive rather than incompatible drivers...