|So ? Does your power supply have enough capacity for the Radeon card ?|
There are lots of ways your 8800 GT video chipset could have been damaged that have nothing to do with the drivers used that would cause weird symptoms when you used whatever drivers.
Or - the 8800 GT card may have been defective but the effects of that didn't show up until you had used it for a while.
There HAVE been major problems with NVidia video or main chipsets being defective in the past, sometimes in very large numbers, and in many of those cases the symptoms didn't show up until you had used it for a while.
If you get weird video symptoms while booting the computer BEFORE the operating system loads, that cannot be caused by any software on the hard drive - that's a hardware problem.
"The person who suggested this based it on his experience updating lots of PC to win 7."
There's lots of incorrect information on the web.
If you find MANY so called experts are saying the same thing, then what he said MAY be valid.
The video drivers themselves have no overclocking ability. There may be a program included along with the actual drivers that allows you to do that, but that's not part of the actual drivers.
Video "drivers" downloads always include associated programs as well as the actual drivers
On the other hand, I know from experience that NVidia doesn't seem to care whether a particular drivers version works properly with all devices it was intended for, as long as most of them ( or Nvidia video chipsets - see below) , have no problems.
( AMD / ATI removes buggy driver versions from it's web site as soon as enough people report problems with it, and they have previous driver versions easily available.)
I have an older Asus mboard that has an NVidia main chipset. When it was brand new I installed an ATI AIW card on it (Radeon video plus TV tuner and related ATI chips and video and audio input capability).
The AIW card worked fine BEFORE the specific ATI drivers were loaded when the NVidia main chipset drivers had been loaded,
and it worked fine when the the specific ATI drivers HAD been loaded when the NVidia main chipset drivers had NOT been loaded,
and it worked fine when the drivers for both had been loaded in Windows Safe mode or Enable VGA mode,
but it DID NOT work fine when the drivers for both had been loaded and you loaded Windows normally.
I searched the web and found that (newest) NVidia main chipset drivers version and previous versions was / were known to clash with ATI's Catalyst software .
I un-installed Catalyst - no change in symptoms.
I loaded the ATI software from the CD that came with the card rather than the newest ones I had downloaded, Custom install, did not install Catalyst - no change in symptoms.
I un-installed all the ATI software, loaded Omega Radeon drivers instead (they didn't use Catalyst or a need a .Net Framework version like Catalyst does) - no change in symptoms.
(The Omega Radeon drivers use ATI software, some of which is slightly modified - tweaked , with the approval of ATI, but it's supported only by the Omega web site).
I loaded the NVidia main chipset drivers from the mboard CD rather than the newest drivers I had downloaded - no change in symptoms.
I tried de-selecting several things in the NVidia main chipset drivers installation rather than using the default Express or whatever installation for both driver versions - no change in symptoms.
I suppose I could have tried to find an older version of the NVidia main chipset drivers on the web (the Nvidia web site didn't have them at the time), but was so frustrated I bought another new mboard that had an AMD main chipset rather than a Nvidia one.
No problems with the same AIW card !
(The card had NOT been damaged by the NVidia main chipset drivers.)
I came to the conclusion, rightly or wrongly, that Nvidia didn't give a dxxx whether their main chipset drivers clashed with the software for an ATI video chipset card. They have been a bitter rival of ATI since before the company was called NVidia.
The symptoms included
- the computer would black screen and reboot for no apparent reason when you did certain things
- most of the time when it did that, the bios loaded default settings except for the time and time. A custom configuration was required, so that resulted in the bios not finding a bootable hard drive partition to boot from..The computer owner was disabled and could not reset the bios settings herself.
(She wanted a TV tuner on the computer because she found it difficult to use a remote for a regular TV - she could use Media Center in MCE 2005 with a TV tuner adapter quite easily.)
When I used a PCI video card, neither of those things ever happened (see below).
When I used another mboard with the same AIW card, power supply, cpu, ram, and drives, neither of those things ever happened (see below).
I got the AIW PCI-E X16 card for a clearance price (it had never been used before), but even so, it cost me, and was still worth, more than the Asus mboard with the NVidia main chipset. It was much cheaper to try another new mboard, rather than trying a Nvidia video chipset card and having to buy a decent TV tuner card as well. or a Nvidia combo card that had a decent TV tuner built into it, with the original Asus mboard.
I ordered the replacement mboard on the web, and installed a PCI card on the original mboard so that my friend could use her system until I was ready to swap mboards (she had an older PCI TV tuner card that I installed as well) and try the AIW card again - no problems with that video card (a different Radeon video chipset on it).
(I haven't tried a different PCI-E X16 video card with that mboard yet - I didn't have a spare one until recently - both the ones I could try have a Radeon video chipset.)