Intel HD 4000 Invalid Tasks
5 Feb 2015 2:35:28 UTC
Topic 197958
(moderation:
Just recently started crunching E@H with the iGPU on my i7-3770k after selling off my GTX 680 cards. I'm currently seeing 52 Invalid results compared against 851 Valid results - a rate of 6.1% bad results. That seems a bit high to me but I've little experience crunching with the iGPU. I'm just curious what others have seen in this regard.
The CPU is running overclocked but the iGPU is at stock speed of 1.15GHz. I run CPU tasks as well, but leave one core free to give the iGPU breathing room.
Intel HD 4000 Invalid Tasks
)
Seem rather high.
The most common issue with the Intel HD graphics is their drivers. Basically only 1 or 2 of them work properly for crunching. I use the 10.18.10.3621 drivers. I would suggest you try that version. Intel have a habit of hiding the older drivers though so you might not be able to find it in the Intel Download Center. If not then try this link (Win7 x64 driver).
Oh and never upgrade the drivers using Windows Update. Microsoft tend to include just the graphics part and leave the OpenCL or CUDA components out.
BOINC blog
Matt is running driver
)
Matt is running driver 10.18.10.4061, which in my tests at SETI proved to be as good as 3621 - in fact, I've gone on using it myself on my HD 4000 (host 5744895, also an i7-3770K).
My current figures are 165 invalid against 2,305 valid, for 7.1% - slightly worse.
The driver problems almost all relate to the later HD 4600 and related GPUs: without checking the entire list, I suspect that both of our hosts have fallen foul of being matched with two Haswells for validation purposes.
Keep an eye on BRP4 Intel GPU app feedback thread, where Bernd is planning to look into the whole problem as soon as time permits.
Thanks for the information. I
)
Thanks for the information. I looked at random sample of 10 tasks from both the Valid and Invalid lists and it does seem that the Invalid tasks are more often matched with Haswell chips, but it's tough to know for sure without going through more of the tasks.
RE: Thanks for the
)
You can find out what drivers those haswell hosts run by looking at their scheduler logs (as long as they ask for work)
Claggy