Hey StrayCat! Completely unrelated to this thread but I was wondering if you could share your app_config.xml file with me. I am an old-time member starting back up again. I am an assuming you use Lunatics as well? I looked through your computers and it looks like you have things dialed in quite well.

Thanks in advance!
NRauer

Hey StrayCat! Completely unrelated to this thread but I was wondering if you could share your app_config.xml file with me. I am an old-time member starting back up again. I am an assuming you use Lunatics as well? I looked through your computers and it looks like you have things dialed in quite well.

Thanks in advance!
NRauer

1 thing, update the driver on your 1070 to 442.19 and that will stop the problems with Arecibo VHAR work units. ;-)

Cheers.

higemayuge is already in the list. Guess I'll send a reminder. :^)

---

That's the bad news - the good news (if it really can be called good news) is that it is now down to 2 tasks in progress.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

https://setiathome.berkeley.edu/workunit.php?wuid=3885927696
two nvidia got robbed against two error 9 cards

I updated AMD drivers to 20.2.1, via the "factory reset" method... it's what their new "clean install" is called.
Noticed in Win10 reliability history that the previous AMD drivers crashed multiple times a day. On just sitting on the desktop, in games and in BOINC.
So will keep an eye on that now.

Read an article and editorial expounding on the lack of reliability of the current AMD drivers with their latest products. Seems to be lots of forum traffic about Win10 just crashing down sitting idle in the Desktop. Seems they rushed product to market and didn't apply the necessary resources to make the drivers work correctly.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Newer drivers are validating normally against other (non-AMD GPU) computers.

Newer drivers are validating normally against other (non-AMD GPU) computers.

That's a good thing. The installed base of AMD users are slowly migrating to the newest drivers and reducing the original issue to minimum.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Even my rx 590 puts out a few errors now and again. Since this is my play machine, I'm not going to switch the drivers to compute within the Amd radeon software. Maybe the next batch of drivers may fix this issue.

Just checking, but any driver prior to the 2020.1.1 version is broken, right?
Because of instability problems in Ghost Recon Breakpoint (the game will start a horrible flicker on my monitors after an hour and requires a reboot), I have to return to 19.11.2 for now. I understand it if I can no longer run Seti then. Have no work in progress anyway.

I saw a YT video explaining how to install ONLY the required AMD drivers and not the entire AMD official package.

Was emphatically explained the AMD package is totally borked and causes instability and crashes. If you get rid of everything except the minimal drivers, the drivers and cards run well.

https://www.youtube.com/watch?v=keURVVjApY4

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I've just been stuck in a perpetual Windows 10 Safe Mode reboot cycle, until I tried out my ancient old Hotmail password... which worked. Needed Safe Mode to get rid of the 2020 drivers as their uninstall had b0rked. How difficult to get places, Microsoft!

Edit: the 'buggy' stuff is what I like so much, ReLive's screen shot making, or screen recording.
This system is for gaming first, BOINC second. Seti runs on my low power Android devices, that's fine with me. Once in a blue weekend I run Seti on my RX 5700 XT, just not now.

19.11.2 give their own problems (mouse gets stuck at times, in GRB all kinds of artifacts on screen.)
I ran Kombustor for a good 20 minutes, no artifacts there.

I have seen various reports of AMD driver issues but don't know how much credit to give them. My system uses both an AMD CPU, 3900X, and AMD GPU, 5700. The system was built just about a week after the hardware was released and while I did have some initial problems to work through it has been very stable since. Some people on the internet have strong opinions and ulterior motives. Shocking I know. When you read through the comment threads on tech sites it is littered with Nvidia people screaming about AMD's flaws and shortcomings and vice-versa. The only thing I can say is my system has been very stable.

---

Why yes, Grumpy, there are invalid results returned. There are also far more valid results, and the system runs well and doesn't crash. You seem determined to live up to your nom de plume. I wish you well.

---

Why yes, Grumpy, there are invalid results returned. There are also far more valid results, and the system runs well and doesn't crash. You seem determined to live up to your nom de plume. I wish you well.

looking at your "valid" tasks, it's clear that something isn't right here. your tasks are being validated even when you are returning different/incorrect results from the wingmen.

Examples
https://setiathome.berkeley.edu/workunit.php?wuid=3905271906
you:

Spike count:    6
Autocorr count: 0
Pulse count:    8
Triplet count:  7
Gaussian count: 0

wingmen:

Spike count:    5
Autocorr count: 0
Pulse count:    11
Triplet count:  5
Gaussian count: 0

https://setiathome.berkeley.edu/workunit.php?wuid=3902795339
you:

Spike count:    23
Autocorr count: 0
Pulse count:    6
Triplet count:  1
Gaussian count: 0

wingmen:

Spike count:    22
Autocorr count: 0
Pulse count:    7
Triplet count:  1
Gaussian count: 0

https://setiathome.berkeley.edu/workunit.php?wuid=3905067362
you:

Spike count:    6
Autocorr count: 2
Pulse count:    1
Triplet count:  0
Gaussian count: 0

wingmen:

Spike count:    6
Autocorr count: 2
Pulse count:    1
Triplet count:  2
Gaussian count: 0

you should update your drivers to the ones that actually work (you need any driver after version 20.1.1 i believe). if you are already using the proper fixed drivers, you need to figure out what is wrong with your system that it's producing incorrect results. maybe overheating or something else. either way you should stop SETI processing again until it's fixed.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

All those three examples have been processed by three computers, not the normal two. Provided two of them agree to the required scientific accuracy ("strongly similar"), the WU as a whole will be accepted. The third partner is then given an easy ride, and allowed to pass at a much lower threshhold ("weakly similar").

But in reality, all the electricity and internet bandwidth used by that third computer is utterly wasted: the WU could have been finalised by the two true scientists on their own.

In none of the three example cases was the result produced by computer 8778135 chosen as the canonical scientific result.

All those three examples have been processed by three computers, not the normal two. Provided two of them agree to the required scientific accuracy ("strongly similar"), the WU as a whole will be accepted. The third partner is then given an easy ride, and allowed to pass at a much lower threshhold ("weakly similar").

But in reality, all the electricity and internet bandwidth used by that third computer is utterly wasted: the WU could have been finalised by the two true scientists on their own.

In none of the three example cases was the result produced by computer 8778135 chosen as the canonical scientific result.

at least the first one, he was actually the second person to submit his result, before my system did. and that result specifically looks worse than "weakly similar" to me. but that's just a first glance at the numbers, not a mathematical comparison.

the main point of my post was to explain why he's getting all these "valid" results that really aren't valid. he needs to fix his system, most likely by updating to the latest drivers.

whatever settings were changed server side to have initial replication of 3 for ati cards needs to be reversed now that there are working drivers. so that hosts like this will get majority invalids and realize they have to fix their system

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

whatever settings were changed server side to have initial replication of 3 for ati cards needs to be reversed now that there are working drivers. so that hosts like this will get majority invalids and realize they have to fix their system

I think that "initial replication" is a misnomer on the web page. I think you'll find that the 'initial' replication was indeed 2 (look at some of his 'in progress' tasks for confirmation), but the the figure was upped to three when the first validation was inconclusive and a check task created. It should be labelled 'current replication', or somesuch.

im still not sure why he got credit for it then. i've seen plenty of WUs invalidate for less.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours