For those of us that are using Intel's iGPUs for crunching - beware and play close attention to the following. You may or may not be able to crunch anymore if you allow updates for the driver(s) you currently have. Intel is bending to the whip of M$S and you may lose any OpenCL abilities you may currently have. I don't use mine for crunching, so I don't know what to expect. This may be nothing but crying wolf, but knowing that the M$S drivers for NVidia does not include OpenCL, it just might be the case here also.
https://www.guru3d.com/news-story/intel-changes-graphics-drivers-to-uwd-and-releases-25-20-100-6444-(uwd).html

---

I don't buy computers, I build them!!

You may or may not be able to crunch anymore

"May or may not" seems to be the correct conclusion from the information released so far. I have a test installation of Windows 10 that I can try to update and see what arrives. I may be some time.....

You may or may not be able to crunch anymore

"May or may not" seems to be the correct conclusion from the information released so far. I have a test installation of Windows 10 that I can try to update and see what arrives. I may be some time.....

I tried to get into Intel's community forums this morning to try to get and answer on this and couldn't log in.

---

I don't buy computers, I build them!!

That looks like a classic example of "If it an't broke don't fix it".
If a system is stable and doing what you want then there is no need to update a hardware driver.

---

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

That looks like a classic example of "If it an't broke don't fix it".
If a system is stable and doing what you want then there is no need to update a hardware driver.

That is, in and of itself true, but if someone allows M$S to upgrade their drivers via Windows Update, then there lies the peril. Especially when 1809 or its' successor is implemented, since M$S does not retain data such as 'not the update drivers' when a new major build is installed. You have to go back and reset ALL of your restrictions all over again. And, if you don't save your old driver install packages, you may or may not be able to reinstall them again. One of the questions that I have is will the old driver packages still be available on the Intel site.

---

I don't buy computers, I build them!!

... if someone allows M$S to upgrade their drivers via Windows Update ...

Precisely. I've done an orderly shutdown of 'Windows 7 production mode', and switched to 'Windows 10 test mode': updates are downloading as we speak. I'll report back - later.

Edit - it's reached

Windows 10, version 1809 re-released
On November 13, 2018, we will begin the re-release of the Windows 10 October Update (version 1809), Windows Server 2019, and Windows Server, version 1809. We encourage you to wait until the feature update is offered to your device automatically.

Note for Commercial Customers: November 13 marks the revised start of the servicing timeline for the Semi-Annual Channel (“Targeted”) release for Windows 10, version 1809, Windows Server 2019, and Windows Server, version 1809. Beginning with this release, all future feature updates of Windows 10 Enterprise and Education editions that release around September will have a 30-month servicing timeline.

Two rounds of updates completed, but I'm still at 1803 - not offering me 1809 yet (or should that be 1811, if they're restarting the rollout from November?). I'll leave it trying while I grab some late lunch.

Two rounds of updates completed, but I'm still at 1803 - not offering me 1809 yet (or should that be 1811, if they're restarting the rollout from November?). I'll leave it trying while I grab some late lunch.

Richard, I think I saw something that they were holding off on another re-release after the last sanfu. I know I rolled mine back to 1803 after Edge went belly up whern the re-release came out at the beginning of the month. You may have to go the Media Creation Tool route to get it.

---

I don't buy computers, I build them!!

Just grabbed the Latest Non-UWD Driver from the List in the provided Link. Set Farragut, (Win 10 Pro x64), to NOT Update Device Drivers. In case Windows Overrides this, I'll be prepared to reinstall the Correct Driver - just Downloaded.

What a PAIN!!! :-O


TL


[Farragut Specs:]

i7 7700 with Integrated HD630 GPU
Gigabyte GA-H270-HD3 MOBO
16 GB Corsair Vengeance DDR4 - CL14 RAM
(Win 10 takes 6.5GB for the HD630 - Displayed in BOINC Event Log.)
Win 10 Pro x64

[NOTE:]

As of today, 11-29-2018, current Driver still functions. BOINC is able to run and SETI is able to Crunch.

[EDIT:]

Updated the amount of RAM Win 10 "Reserves" for the HD630... (6.5GB)

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

As of today, 11-29-2018, current Driver still functions. BOINC is able to run and SETI is able to Crunch.

Does that 'current driver' have a version number, and is it UWD?

As of today, 11-29-2018, current Driver still functions. BOINC is able to run and SETI is able to Crunch.

Does that 'current driver' have a version number, and is it UWD?

The Driver I Downloaded does NOT have UWD. The Latest Driver, (reflected on that Site), is UWD - I grabbed the one listed just above it that is NOT UWD.

25.20.100.6373 <--- This is the Driver I grabbed. :-)

[EDIT:]

I did NOT recheck what existing Driver is running on Farragut when I made the change to NOT Update Drivers. I will have to get that later.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

The Driver I Downloaded does NOT have UWD. The Latest Driver, (reflected on that Site), is UWD - I grabbed the one listed just above it that is NOT UWD.

25.20.100.6373 <--- This is the Driver I grabbed. :-)

That is the last legacy driver. Using the Intel® Driver & Support Assistant, the UWD driver is 25.20.100.6444 for Kaby Lake (HD630) iGPUs. It may be different for other Intel iGPUs.

---

I don't buy computers, I build them!!

Even though I don't use my iGPU for crunching, I did d/l the driver directly from Intel and here's the 1st few lines from the event log.

11/29/2018 12:15:07 | | Starting BOINC client version 7.14.2 for windows_x86_64
11/29/2018 12:15:07 | | log flags: file_xfer, sched_ops, task, cpu_sched
11/29/2018 12:15:07 | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
11/29/2018 12:15:07 | | Data directory: D:\BOINC
11/29/2018 12:15:07 | | Running under account Cliff Harding
11/29/2018 12:15:08 | | CUDA: NVIDIA GPU 0: GeForce GTX 1070 (driver version 417.01, CUDA version 10.0, compute capability 6.1, 4096MB, 3558MB available, 6463 GFLOPS peak)
11/29/2018 12:15:08 | | OpenCL: NVIDIA GPU 0: GeForce GTX 1070 (driver version 417.01, device version OpenCL 1.2 CUDA, 8192MB, 3558MB available, 6463 GFLOPS peak)
11/29/2018 12:15:08 | | OpenCL: Intel GPU 0 (ignored by config): Intel(R) HD Graphics 630 (driver version 25.20.100.6444, device version OpenCL 2.1 NEO, 6432MB, 6432MB available, 221 GFLOPS peak)
11/29/2018 12:15:08 | | OpenCL CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 7.6.0.0, device version OpenCL 2.1 (Build 0))
11/29/2018 12:15:08 | SETI@home | Found app_info.xml; using anonymous platform

I don't know if this is of any help.

---

I don't buy computers, I build them!!

Personally, I believe it would be a very good thing if SETI Completely Removed All Intel iGPU Apps and try to forget they ever existed. In Most cases all the Intel App does is Slow down the entire Computer to the point it would run much faster just running the CPU App. SETI has recently noted they need more resources, well, Removing the Intel App would result in MORE production from the machines that are currently using the Intel App. This is Especially True on the Mac Apps where not only does the App slow the entire machine, it produces mostly Bad Results causing wasted resources to verify something that shouldn't have been run in the first place.

Take a look at this machine, https://setiathome.berkeley.edu/results.php?hostid=8624423. That machine should be running the ATI task in about 11 minutes, other machines with similar GPUs do, but, that machine is taking 30 minutes instead of 11. Look at the CPU tasks which are taking close to 5 HOURS, they should be taking about an Hour! Running the Intel App on that machine has slowed it considerably. If SETI needs more resources, then I suggest they Remove what is slowing down the resources they have. I have taken the first step and Removed the Intel App from the Crunchers Anonymous page, No More Intel iGPU Apps from Me. I would suggest SETI do the same, Remove something that usually creates Bad results, and Slows the Computers while doing so.

+1 very well stated
In the past I have stated IGPUs are evil for crunching.

---

A couple of Years ago a few of us tried to fix the Mac iGPU App, it's hopeless. It runs fine on the nVidia GPUs, but produces Bad Results on the Intel iGPU.
I suggested it be removed back then, but, it's still there slowing machines and wasting resources.

11/29/2018 12:15:08 | | OpenCL: Intel GPU 0 (ignored by config): Intel(R) HD Graphics 630 (driver version 25.20.100.6444, device version OpenCL 2.1 NEO, 6432MB, 6432MB available, 221 GFLOPS peak)


I don't know if this is of any help.

Thanks, Cliff - that's very encouraging. But my testing is aimed at the full breadth of the BOINC community, including those hundreds of thousands of volunteers who don't choose to crunch for SETI, and who have never posted on any project's message board. I'd like to be sure that scientific results will continue to flow in from the computers on automatic update, too.

So I'll let my Windows 10 test rig collect 1809 in due course, and see what arrives from Microsoft with it: as we know from the early days of Windows 10, what the manufacturers supply to their own users doesn't always end up in the Windows Update channel.

In the meantime, it's crunching away for SETI to fill in the time, so nothing is lost.

From Event Log:

11/29/2018 10:25:37 AM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 630 (driver version 23.20.16.4973, device version OpenCL 2.1 NEO, 6508MB, 6508MB available, 221 GFLOPS peak)
11/29/2018 10:25:37 AM | | OpenCL CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 7.6.0.611, device version OpenCL 2.1 (Build 611))


So, Farragut is currently on Driver 23.20.16.4973. I will see if I can find this in the List on that Page and DL it to Farragut directly. (On Farragut now...) The other Driver I Downloaded is on the Mac Pro 5,1 System in the event something happens to Farragut. When I get back to Andromeda, (the 5,1 System), I will DL 23.20.16.4973 there, too as a backup.


TL

[EDIT:]

Apparently, 23.20.16.4973 is strictly from MS Directly. I found the appropriate Intel .cab File from MS for 23.20.16.4973 and Downloaded it directly to Farragut.

NOW, I will perform a WD Backup to the MyPassport 2TB External Drive to make sure that I will have full access to this File if/when needed.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Two rounds of updates completed, but I'm still at 1803 - not offering me 1809 yet (or should that be 1811, if they're restarting the rollout from November?). I'll leave it trying while I grab some late lunch.

Richard, I think I saw something that they were holding off on another re-release after the last sanfu. I know I rolled mine back to 1803 after Edge went belly up whern the re-release came out at the beginning of the month. You may have to go the Media Creation Tool route to get it.

Still haven't snagged a Windows Update, but it looks like the Update Assistant should do the trick.

OK, that worked. ~1.5 hours later, I'm up to 1809, and Microsoft installed

30/11/2018 12:33:26 | | CUDA: NVIDIA GPU 0: GeForce GTX 1050 Ti (driver version 388.13, CUDA version 9.1, compute capability 6.1, 4096MB, 3386MB available, 2138 GFLOPS peak)

I'll let it crunch for a bit, and then switch to the Intel GPU (this is one of the BIOSs which prevents running both together), and see what I get for that.