Fantastic news, thank you :-)

I apologise for the paucity of useful information since requested the day before. I've been pretty much exclusively on iOS and ChromeOS devices the past couple days. Though most all that I knew I already related, barring the predictable BOINC log entries stating variations on a theme of "missing intel_gpu GPU".
Luckily that didn't slow you down! :-)

Cheers!

---

"The surest sign that intelligent life exists elsewhere in the universe is that it has never tried to contact us." - Calvin and Hobbes (Bill Watterson)

I also refer to a SETI test in that thread: like then, today's test with the SETI app has led to an inconclusive result, so I suspect Intel have tweaked the precision or driver optimisation again. Bernd is aware of the Einstein problem, but too busy to do anything about it: I don't feel like waking Raistmer out of his slumbers before I set off on my travels. So I'm inclined to let this one lie until some cold, boring, winter's evening.

Change of plan. The two SETI tasks I ran with the original OEM driver threw up multiple issues, so much so that the first one needed four replications before SETI found a pair which could validate together.

That suggests that there may be something more seriously wrong with the current application mix at SETI, and Raistmer and I are going to run some more substantial offline tests.

In the meantime, that level of replication is obviously wasteful for the project and all concerned: I suggest that - whilst observed testing is very welcome - you don't put these newest iGPUs into full SETI production until we report back.

That's a shame. Thanks for the update!

---

"The surest sign that intelligent life exists elsewhere in the universe is that it has never tried to contact us." - Calvin and Hobbes (Bill Watterson)

Change of plan. The two SETI tasks I ran with the original OEM driver threw up multiple issues, so much so that the first one needed four replications before SETI found a pair which could validate together.

That suggests that there may be something more seriously wrong with the current application mix at SETI, and Raistmer and I are going to run some more substantial offline tests.

In the meantime, that level of replication is obviously wasteful for the project and all concerned: I suggest that - whilst observed testing is very welcome - you don't put these newest iGPUs into full SETI production until we report back.

Apologizes, but what is "current" for an iGPU? Yesterday I decided to enable my UHD 630 for crunching Seti, and it appears to be working just fine. No thrashing and tasks are being completed and validated, much to my surprise. Let me know if you need any help testing anything.

As mentioned somewhere in this thread, I updated to version 26.20.100.6890 (Latest) Date: 5/29/2019 (DCH version) from https://downloadcenter.intel.com/download/28816/Intel-Graphics-Windows-10-DCH-Drivers?product=80939, and all my previous problems went away as well.

Raistmer is still looking through the test logs I sent him, but I think it might really have been the older drivers this time (he always blames the drivers, and I always blame his coding. We're fine: last time, it turned out to be a compiler optimisation flag, so we were both wrong).

My test machine is running at All tasks for computer 8670176: looking good so far. The single inconclusive seems to be a dodgy wingmate with several inconclusives and invalids.

Unfortunately, there's no sign of the promised v7.16 yet, but anyone who finds themselves stymied by the DCH extensions list can download the 'artifact' test build from https://ci.appveyor.com/project/BOINC/boinc/builds/25266698/artifacts