Back a few months ago, I got a message from someone about one of my systems outputting a lot of errors, inconclusive, and failed results. I started looking into things, and did a reset of the project, and things seemed to be great, but now are back to worse than before. Nearly every one is an inconclusive, and those that aren't, seem to be failures.

Should I reset the project again? Is this a problem with the system I'm using, or the versions of the software, or drivers?

I want to contribute, not hold back the project. I'm thinking of killing this system from the account if I can't get this under control.

It's the fastest system too.

It's a Windows 10 Core i7 with tons of memory and drive space, and *should* be great on the project, but blows chunks for some reason.

This all seems to have started around April 12th. Did something change at that time?

Thanks for any assistance...

Most of the invalids and errors are associated with the GPU.
http://setiathome.berkeley.edu/results.php?hostid=7907828

A few things pop to mind - did you update the drivers, or did Windoze update them for you? (I know that, with Nvidia GPUs, letting Windoze update the drivers is a very bad thing.)
If you look in number crunching you will find a number of threads reporting this sort of problem, and suggesting appropriate drivers etc.

---

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

Thanks for the response. I checked around after posting, and found a comment about using the 'legacy drivers' from the AMD website. I was 'gifted' the Microsoft drivers. I downloaded and installed the legacy, and the problems seem to have gone away. I only had, after the first few screens, two or three inconclusive results, and no failures. Quite an improvement.

I think I turned off Windows 'helpful' updating.

This system I'm having the issues with is a notebook, and I guess I'm not surprised that it might cause problems. Between it being a notebook, and Windows' 'help', I'm surprised *anything* works.

But enough complaining about Windows. I could go on all night...

I'll have to keep a closer eye on this one.

Thank you!