Having a big big issue with Nvidia 7600 and Driver 162.18

kill4killin · Jul 22, 2007, 07:37 PM

Hello, I am new to these forums, this is my first post in fact

so please bare with me.

I started having problems the other day after running ATItool after hearing rave reviews about it from some friends. I was trying to see if it did any better of a job overclocking my graphics card than RivaTuner did. Well, long story short, it did, but the problem is is that it went a bit to far. My card has a problem that when the RAM is overclocked to far (I know this from experience) it likes to corrupt the graphics driver. Now, it has happened before so I wasn't all the surprised but this time instead of just re-installing windows like I have done in the past, a friend recommended that I try using drivercleaner.net to see if that didn't fix my problem. Well, I went and bought the program, I followed the directions to the letter when using it. Then I went to install driver v.162.18 since it is the newest driver available for my card. I installed it, rebooted and when I entered into windows I was pleasetly surprised that my computer wasn't bluescreening anymore with the driver installed...however, I also noticed that my grahpics card's fan was still spinning very fast like it does when the driver isn't installed...odd, I thought to myself, so I investigated a little into it to find that device manager is reporting it has a corrupted driver....ok, so I went through and did the process with driver cleaner again...reinstalled and rebooted...still has a corrupt graphics driver...so I'm here asking if ANYONE knows what is wrong with my computer? I need a fix and I need it as soon as possible. I have been without my desktop for 3 days now and I really would like to go back to using my desktop rather then my laptop.

Thanks in advance for the help!!!

kill4killin · Jul 22, 2007, 07:54 PM

Ok, forget it, I tried other older versions of the driver as well and it looks like I'm going to declare the cause of death a suicide from my computer not wanting to exist in this world anymore. So, I'm just re-installing windows now I don't really care about it anymore. But lesson learned, DO NOT EXCEED 900mhz on the memory with a 7600GT!!!

But if anyone knows wtf happened please, enlighten me with this information, I still wish to know if there is an easy fix next time it happens because I'm sure I won't heed my own warning I never do.

kill4killin · Jul 22, 2007, 11:23 PM

And an update for anyone that cares, I tried doing the soft install, that made it blue screen even worse saying "fatal system error". Then I just said screw it and I reformatted the entire disk and it somehow messed up and caused the windows partition tool to be unable to read the disk. Then I downloaded Seagate SeaTools and zeroed out the hard drive so it would be back to factory state and then formatted again and am now installing windows. I guess I should have just gone for the reformatt to begin with.

Jul 22, 2007, 07:37 PM	#1
kill4killin DriverHeaven Newbie Join Date: Jul 2007 Posts: 3 Rep Power: 0	Having a big big issue with Nvidia 7600 and Driver 162.18 Hello, I am new to these forums, this is my first post in fact so please bare with me. I started having problems the other day after running ATItool after hearing rave reviews about it from some friends. I was trying to see if it did any better of a job overclocking my graphics card than RivaTuner did. Well, long story short, it did, but the problem is is that it went a bit to far. My card has a problem that when the RAM is overclocked to far (I know this from experience) it likes to corrupt the graphics driver. Now, it has happened before so I wasn't all the surprised but this time instead of just re-installing windows like I have done in the past, a friend recommended that I try using drivercleaner.net to see if that didn't fix my problem. Well, I went and bought the program, I followed the directions to the letter when using it. Then I went to install driver v.162.18 since it is the newest driver available for my card. I installed it, rebooted and when I entered into windows I was pleasetly surprised that my computer wasn't bluescreening anymore with the driver installed...however, I also noticed that my grahpics card's fan was still spinning very fast like it does when the driver isn't installed...odd, I thought to myself, so I investigated a little into it to find that device manager is reporting it has a corrupted driver....ok, so I went through and did the process with driver cleaner again...reinstalled and rebooted...still has a corrupt graphics driver...so I'm here asking if ANYONE knows what is wrong with my computer? I need a fix and I need it as soon as possible. I have been without my desktop for 3 days now and I really would like to go back to using my desktop rather then my laptop. Thanks in advance for the help!!!

Jul 22, 2007, 07:54 PM	Thread Starter #2
kill4killin DriverHeaven Newbie Join Date: Jul 2007 Posts: 3 Rep Power: 0	Ok, forget it, I tried other older versions of the driver as well and it looks like I'm going to declare the cause of death a suicide from my computer not wanting to exist in this world anymore. So, I'm just re-installing windows now I don't really care about it anymore. But lesson learned, DO NOT EXCEED 900mhz on the memory with a 7600GT!!! But if anyone knows wtf happened please, enlighten me with this information, I still wish to know if there is an easy fix next time it happens because I'm sure I won't heed my own warning I never do.

Jul 22, 2007, 11:23 PM	Thread Starter #3
kill4killin DriverHeaven Newbie Join Date: Jul 2007 Posts: 3 Rep Power: 0	And an update for anyone that cares, I tried doing the soft install, that made it blue screen even worse saying "fatal system error". Then I just said screw it and I reformatted the entire disk and it somehow messed up and caused the windows partition tool to be unable to read the disk. Then I downloaded Seagate SeaTools and zeroed out the hard drive so it would be back to factory state and then formatted again and am now installing windows. I guess I should have just gone for the reformatt to begin with.