Advanced search

Message boards : Graphics cards (GPUs) : GTX 770 Driver Warning

Author Message
Midimaniac
Send message
Joined: 7 Jun 13
Posts: 16
Credit: 41,089,625
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwat
Message 31034 - Posted: 26 Jun 2013 | 2:05:25 UTC

Hey all-
I bought one of the first EVGA GTX 770 SC ACX cards. I think I ordered it the day it appeared on the egg. The driver that shipped with the card is 320.08. This driver works perfectly in my system. Windows 7, i7 3770k oc'd to 4.3GHz, 32GB RAM.

A week or so ago a new driver appeared on Nvidia's website: 320.18. At that point I had not read all of the threads on this website urging GPUG users to stick with a driver they know works well. So I installed the new driver and starting experiencing horizontal tearing when watching videos or streaming Netflix. Drives you nutty pretty quick. And you wonder if your brand new card is failing...

I got that driver out of my system and reinstalled the old driver and now all is well again.

Once again:
Driver 320.08 works great for me.
Driver 320.18 was a bummer.


To uninstall the old driver, do it from add/remove programs, don't do it in device manager. You could have up to 4 or 5 Nvidia program entries. Take them all out. Then run regedit.exe. In Windows 7 click start, then type in regedit.exe and it will pop up where you can click to open it. Once Regedit is open make sure you click on computer to start your search at the top of the tree. On the drop-down box for edit click Find, and then type in Nvidia. After it finds the first key pertaining to Nvidia press delete on your keyboard, and then press enter to confirm. Then press F3 to take you to the next key. Go through every key deleting them all. Don't get in a big rush and accidentally remove something that is not Nvidia! If you have never done this before, don't worry. As long as you had typed Nvidia in the find box Regedit won't screw up. Every key that it opens will need to be deleted, and there are A LOT of them. This will likely take you about 10 minutes. In my case, for some reason there was maybe 30 or more keys all really close together that I got a message from the system saying it was impossible to delete them. Huh? Never had that happen before and I was a little worried. After you delete all of the Nvidia keys you can re-boot your 'pooter, re-install your old driver, and all should be well again!

flashawk
Send message
Joined: 18 Jun 12
Posts: 297
Credit: 3,550,319,397
RAC: 1,826,602
Level
Arg
Scientific publications
watwatwatwatwatwatwatwat
Message 31040 - Posted: 26 Jun 2013 | 17:19:51 UTC

They released a beta driver yesterday, 320.49, I was getting ready to give it a shot.

https://forums.geforce.com/default/topic/548402/geforce-drivers/official-nvidia-320-49-beta-display-driver-feedback-thread-released-6-25-13-/

There's been a lot of talk about the 320.18, 320.11 and the 320.08 with people having all kinds of strange issue's (the 320.11 only came with cards on CD).

Midimaniac
Send message
Joined: 7 Jun 13
Posts: 16
Credit: 41,089,625
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwat
Message 31043 - Posted: 26 Jun 2013 | 20:13:38 UTC

It appears I am still getting some horizontal tearing artifacts when I scroll. Not severe, but still annoying. Possibly sometime later today I am going to uninstall and reinstall the Nvidia drivers again. This time I will look in task manager when I come to those keys that the system said were impossible to delete. It must have been that there was something Nvidia related that was still running even after I uninstalled Nvidia from add/remove programs. If that doesn't work I have a backup image I can restore. I will post here whenever I get this fixed!

flashawk
Send message
Joined: 18 Jun 12
Posts: 297
Credit: 3,550,319,397
RAC: 1,826,602
Level
Arg
Scientific publications
watwatwatwatwatwatwatwat
Message 31044 - Posted: 26 Jun 2013 | 21:42:47 UTC - in response to Message 31043.

Why don't you use driver sweeper? That's what it's for, doing all that editing by hand can get tedious, it's been recommended by the community and many, many people use it to remove all traces of drivers. If you do a custom install of the driver there's an option to do a clean install too.

http://www.guru3d.com/content_page/guru3d_driver_sweeper.html

I installed 320.49 and it made a huge difference, GPU load is at a steady 97%, memory controller load is at 32%. I'm going to give it 24 hours and then start bringing the GPU clock back up, I hope this does the trick. It also raised the percentages on the GTX670 that's in the same box, fingers crossed.

Profile Beyond
Avatar
Send message
Joined: 23 Nov 08
Posts: 1104
Credit: 6,101,732,079
RAC: 0
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 31046 - Posted: 27 Jun 2013 | 0:33:18 UTC - in response to Message 31044.

Why don't you use driver sweeper? That's what it's for, doing all that editing by hand can get tedious, it's been recommended by the community and many, many people use it to remove all traces of drivers. If you do a custom install of the driver there's an option to do a clean install too.

http://www.guru3d.com/content_page/guru3d_driver_sweeper.html

Yep, Driver Sweeper works wonders.

I installed 320.49 and it made a huge difference, GPU load is at a steady 97%, memory controller load is at 32%. I'm going to give it 24 hours and then start bringing the GPU clock back up, I hope this does the trick. It also raised the percentages on the GTX670 that's in the same box, fingers crossed.

Hopefullu NV has things sorted out...

Midimaniac
Send message
Joined: 7 Jun 13
Posts: 16
Credit: 41,089,625
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwat
Message 31047 - Posted: 27 Jun 2013 | 1:03:26 UTC

Guys,
I'll give DriverSweeper a try. First though, I'm going to try reinstalling 320.08 using RegEdit again, because I want to try & Figure out why the system was telling me there was some keys that were impossible to delete.

After I get that part taken care of I'll give 320.49 a try, just for kicks. Flashawk maybe I missed it or maybe I've forgotten already, but which 700 card do you have, the 770? And you were having trouble with which driver? And you are saying your GPU load went up with the 320.49 driver?

I reset my local compute preferences to 99% like you guys recommended and it did indeed force Rosie to yield one core, which is cool. The result is that GPU load went from 82% to 86%. With Rosie suspended and GPUG running alone my GPU load only hits 92% though. Give me some time to play around and then I'll post here and let you guys know how it turns out.

I had to make this reply twice because the first one didn't show up on the thread! Uh-oh... Not sure what happened, but I hope it's not hanging around somewhere where it's not supposed to be!

flashawk
Send message
Joined: 18 Jun 12
Posts: 297
Credit: 3,550,319,397
RAC: 1,826,602
Level
Arg
Scientific publications
watwatwatwatwatwatwatwat
Message 31048 - Posted: 27 Jun 2013 | 4:14:59 UTC
Last modified: 27 Jun 2013 | 4:19:26 UTC

I have the EVGA GTX770 SC ACX Super clocked (02G-P4-2774-KR). I couldn't even get the 320.18 to recognize the 770 so I didn't use it (must be an XP64 thing), so I settled on the 320.08 international that came on disk and at least got the card recognized but shortly after started getting spontaneous reboots. I backed down the GPU speed, lowered the GPU voltage, dropped system RAM from 1600 9-9-9-24 to 1333 10-10-10-27 and it stabilized. Tomorrow, I'll start putting those settings back, slowly and see what happens. They are supposed to release a new WHQL driver next week.

Edit: Were starting to scrape the bottom on the long queue.

Midimaniac
Send message
Joined: 7 Jun 13
Posts: 16
Credit: 41,089,625
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwat
Message 31049 - Posted: 27 Jun 2013 | 5:23:38 UTC - in response to Message 31048.

I'll be darned. We have the exact same card, only I'm using Win 7 Professional.

OK, what I did:

After running add/remove programs on all 6 Nvidia entries I rebooted into safe mode and opened task manager to make sure there was nothing that has to do with Nvidia running. Then I opened regedit and manually took everything out that was left. I did not use DriveSweeper for 3 reasons:

1- I wanted to see why on my first attempt at uninstalling 320.18 there was 20 or 30 keys that the system said were impossible to remove. Those keys were in a Windows folder called PnpLockdown. I believe they are data pertaining to BOINC that was locked up in temporary files pertaining to my current tasks. I noticed several of the keys had OpenCL in their names.

2- I know RegEdit works, and I decided that because someone recommended a software program as a substitute in a couple of threads somewhere was not a good reason to put my faith in it. There is no way RegEdit can not work, really, and I thought the 10 minutes spent using RegEdit was well worth the time spent.

3- I realized the reason I passed on DriveSweeper the first time I saw it recommended in a thread somewhere is because I couldn't find a page to download it that wasn't full of ads designed to trick you into downloading something else. You know what I mean. But I actually did go to the download page again today and attempt to download it. I was tricked into downloading 77zip.exe, which appears all over the place on that website. According to AVG that file is a virus, so AVG removed it for me before I could even save it. At that point I thought SCREW THIS and left the download page.

So it seems I successfully removed 320.18. I was a little wary of installing the beta driver 320.49 but went ahead with it anyway, and everything is working just fine. Did you read the 66 page pdf release notes file that pertains to it? I skimmed over it. They had all of the known issues laid out there in black and white, but I didn't see anything that pertains to the 770, so I suppose we are going to be OK with it. I do not get 97% GPU loading like you do though. My load is exactly the same as it was before: Running 7 cores of Rosie & 1 core of GPUG I get 86% GPU load according to NV-Z. If I run GPUG by itself I get 92% load. That might not look like much, but a 10hr task at 92% turns into 10hr,42min at 86%. But, since I have only 1 GPU, I can't see doing that and wasting my CPU time.

Cheers!
John

Midimaniac
Send message
Joined: 7 Jun 13
Posts: 16
Credit: 41,089,625
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwat
Message 31071 - Posted: 27 Jun 2013 | 19:00:05 UTC - in response to Message 31049.

Today I'm getting 95% load with GPUG running a SANTI task.

ExtraTerrestrial Apes
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 17 Aug 08
Posts: 2688
Credit: 1,172,901,099
RAC: 370,180
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 31077 - Posted: 27 Jun 2013 | 21:02:23 UTC
Last modified: 27 Jun 2013 | 21:03:43 UTC

GPU utilization in XP and linux is always significantly higher, so that's likely the cause of the difference here.
Edit: and GPU utilization varies by WU type. Santi are short ones, aren't they? If I was you I'd only run long-run queue tasks on a GPU as powerful as the GTX770. Only go for short ones if nothing else is available.

MrS
____________
Scanning for our furry friends since Jan 2002

Post to thread

Message boards : Graphics cards (GPUs) : GTX 770 Driver Warning