Yes it worked! :)

1st MW v1.02 WU successfully crunched since I installed my HD 5850!
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=492758643

Although it's not been validated yet, and now 2 more successfully crunched :) (again not yet validated).
Annoying to have to run such old drivers though! What's going on there?

So just to re-iterate what I did to fix it :-

Uninstalled everything of previous cat driver using cat manager (including itself).
Rebooted to safe mode
Ran Display Driver Uninstaller (driver sweeper's replacement)
Rebooted into normal mode & installed Cat 13.1 driver
Rebooted 1 last time!

Thanks to Mikey & Captain Jack for putting me on track :)

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Those 3+1 now validated :).

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Those 3+1 now validated :).

I am glad it is now working!!!!!

As for Windows uninstallers they have been notoriously BAD ever since Windows 2! It's the sharing files concept MS uses that causes the problems.

Windows 2!? Lol, that was a while ago! I started on Win 95, have used windows 3.1 a few times though.

Oh & I have 98 validated MW 1.02 WUs now, so definitely sorted :).
Maybe now I'll see what my 5850 can overclock to......

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Those 3+1 now validated :).

I am glad it is now working!!!!!

As for Windows uninstallers they have been notoriously BAD ever since Windows 2! It's the sharing files concept MS uses that causes the problems.

Especially since those early shared support files had no version control, and the installers had to rely on datestamps when deciding whether a file was overwritable. Anybody can falsify a datestamp, and some otherwise reputable companies did.

Looking at the 30 errored WUs for your machine they are all MilkyWay@Home v1.02 (opencl_amd_ati) app WUs, so it isn't all GPU apps failing you, just that 1.
What you mean I guess is WUs not apps, totally different thing.

If you go to your 'my account'>MW@H preferences >click 'edit my MW@H preferences' >untick 'Milkyway@home' >update preferences then you can run the other GPU app (make sure the others remain ticked & that you have allowed GPU crunching elsewhere.
So you can use your GPU without errored WUs :).

What drivers are you using for your HD 6950?

Still no news from the project folk though!!

Driver package 13.152.1.8.


I'll un-select Milkyway@home and select the other apps and gpu. I don't want to get the other tasks for cpu though. Will see what goes down. Will report back shortly.

So far so good. Milkyway@home seperation modified fit crunching with no errors.

Thanks for the help!

Now that my 6950 has been swapped out for a 7870XT, I seem to be able to crunch MW 1.02 again. Three validated thus far. None had a computation error while running. Currently on Cat 13.9.

Edit: My 7950 now seems to be able to successfully complete 1.02 tasks as well. Previously, they would always fail on this card also. Cat 13.9 is the same driver I was running before I removed the 6950, so changing that card out of the machine is the only thing different between then and now.

---

Interesting, I might try 13.9 again then.

So far so good. Milkyway@home seperation modified fit crunching with no errors.

Thanks for the help!

Cool, but check out my posts on Jan 30th here, I was able to get my 5850 to crunch MW 1.02 WUs again :).

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Forgot to say :o, Tom helped me too with the driver problem (via PM) so thanks to him too :)

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Over 400 validated MW 1.02 WUs!

---

Hi Matt, good to hear.

Btw fancy submitting some crunching times to my MW benchmark thread?
The 7870XT in particular would be interesting to see as it would be the only 1 atm!

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Yes, I'd be happy to share. This 7870XT is great but for the fact that it tends to run a bit hot (as compared to my 7950 at the same speed).

Looks like that thread is only for MW Separation (Modified Fit) from your criteria, right? I've posted my 5 most recent tasks at the 213.76 level.

---

Ok I finally got around to trying 13.9 again, after un-installing 13.1 , then doing a 'deep' clean, then installing 13.9 & rebooting after each step.

13.9 instantly gave errors on MW 1.02 WUs (they ran for ~9s)

Matt
Weird that your 7950 is now ok after the 6950's gone, but their definitely seems to be an issue with 5800s & 6900s with Cat 13.9, & probably 13.4 (I'm trying that 1 now).

[update] Cat 13.4 errors out the MW 1.02 WUs too, (although interestingly they ran for ~60s this time).
So it seems clear, if you have a 5800 or 6900 card the latest driver you can use for being able to crunch all GPU WUs is Cat 13.1.

Out of interest, I'm going to try Cat 14.1 beta v1.6 - nope that caused errors within 9s too.

And back 13.1 & all ok now :).

Could the MW staff give us some idea what's going on here?

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Thank you for this thread.
I was also having problems with my 2 5870's.
Downgraded to 13.1 did the trick.

I would also like to say how disappointed I am with lack of interest from the devs on this issue.
Not one reply from them concerning this.
Pathetic!

---

Had the same issue with my HD6950 for months. Rolling back to older drivers is not an option. It's a shame the devs didn't fixed the problem yet.

Why can't you down grade drivers?

Thank you for this thread.
I was also having problems with my 2 5870's.
Downgraded to 13.1 did the trick.

I would also like to say how disappointed I am with lack of interest from the devs on this issue.
Not one reply from them concerning this.
Pathetic!

Couldn't agree more!

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

At work I downgraded to 12.6 in order to make my HD4850 work.
At home with my HD6950 I'm also gaming so I'm not willing to downgrade.
The only solution is to keep using the "modified fit", although these WU's seem to give less credit/hour than the standard ones.

My 4870 worked ok with Cat 13.1

Re your 6950, is 13.1 that much worse than 13.12 for playing the games you have?
Didn't know mod fit WUs gave less credit/hr, I wonder why they do that?

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

I'm also gettting Computation error for all the M@H projects. Any solutions to this?
I'm on the latest boinc version (7.2.39 x64) and boinc keeps running as a service. All the other projects on the same CPU are okay.

What should I do? Keep on sending errors until someone fix it?