SETI@home v7 7.03 (opencl_intel_gpu_sah) - Computation Error

Message boards : Number crunching : SETI@home v7 7.03 (opencl_intel_gpu_sah) - Computation Error
Message board moderation

To post messages, you must log in.

AuthorMessage
ph.gsc.sevilla.larry

Send message
Joined: 13 Mar 12
Posts: 5
Credit: 11,510,421
RAC: 21
Philippines
Message 1648335 - Posted: 2 Mar 2015, 0:20:36 UTC

I have an Intel i7-4790 running Win 7 x64.

The BOINC app SETI@home v7 7.03 (opencl_intel_gpu_sah) gives Computation Error.

fyi
ID: 1648335 · Report as offensive
Bill Butler
Avatar

Send message
Joined: 26 Aug 03
Posts: 101
Credit: 4,270,697
RAC: 0
United States
Message 1648356 - Posted: 2 Mar 2015, 3:17:14 UTC - in response to Message 1648335.  

Yes, 57 recent Intel GPU work unit errors on that computer.

The reason given:
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x6A0B507C read attempt to address 0x00000001


Not sure why.
How many simultaneous Intel GPU workunits are you running at a time?
"It is often darkest just before it turns completely black."
ID: 1648356 · Report as offensive
Profile Sutaru Tsureku
Volunteer tester

Send message
Joined: 6 Apr 07
Posts: 7105
Credit: 147,663,825
RAC: 5
Germany
Message 1648385 - Posted: 2 Mar 2015, 5:33:23 UTC - in response to Message 1648335.  
Last modified: 2 Mar 2015, 5:44:02 UTC

You use the 10.18.10.3960 driver.


Message boards : Number crunching : Intel gpu not seen by BOINC - Message 1627983
(...)
Do not use the 10.18.10.3960 driver shown as 'previously released' on the page retrieved by an Intel driver search for G3220 - that driver has definitely been reported as producing invalid results with current BOINC project science applications.



Example, I use the 10.18.10.3408 driver (which is on the driver DVD for the CPU/mobo combi, with Intel® Celeron® J1900 CPU + Intel® HD Graphics iGPU, Win8.1 x64) - and since 1 1/2 months no problems.
ID: 1648385 · Report as offensive
Werecow
Avatar

Send message
Joined: 13 Mar 05
Posts: 56
Credit: 4,917,657
RAC: 3
United States
Message 1659456 - Posted: 30 Mar 2015, 20:49:49 UTC

Another host 7442021 with Intel GPU also generating the same computation errors on every task, but using 10.18.14.4029 driver. Is this a known issue? I did a brief search and didn't find that driver mentioned anywhere.
ID: 1659456 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1659458 - Posted: 30 Mar 2015, 20:59:24 UTC - in response to Message 1659456.  

Another host 7442021 with Intel GPU also generating the same computation errors on every task, but using 10.18.14.4029 driver. Is this a known issue? I did a brief search and didn't find that driver mentioned anywhere.

He is also using a HD 5000 iGPU. I don't know if the application has been tested on that hardware yet, with any driver - I certainly don't have one.
ID: 1659458 · Report as offensive
MaVac

Send message
Joined: 24 Mar 08
Posts: 3
Credit: 807,800
RAC: 0
Czech Republic
Message 1660838 - Posted: 2 Apr 2015, 19:52:36 UTC - in response to Message 1659458.  

I received a message from werecow:
Your computer Host # 6947495 has a problem; the Intel GPU is only generating Error results.

If you are not able to solve the problem yourself, please ask questions on the Message Boards. Someone there will be happy to help :)

What should I look for? I have i7-4770K with HD4600 (driver 10.18.10.3977)
ID: 1660838 · Report as offensive
MaVac

Send message
Joined: 24 Mar 08
Posts: 3
Credit: 807,800
RAC: 0
Czech Republic
Message 1660849 - Posted: 2 Apr 2015, 20:02:27 UTC - in response to Message 1660838.  

I just installed BOINC client 7.4.42 and Intel driver 10.18.14.4156 so we will see...;-)
ID: 1660849 · Report as offensive
Werecow
Avatar

Send message
Joined: 13 Mar 05
Posts: 56
Credit: 4,917,657
RAC: 3
United States
Message 1660914 - Posted: 2 Apr 2015, 23:33:41 UTC - in response to Message 1660849.  

Updating drivers may or may not solve the problem. Quoting HAL9000 in this thread http://setiathome.berkeley.edu/forum_thread.php?id=76941

I wonder if that has to do with your driver version 10.18.14.4156. In the world of GPU crunching latest rarely is the greatest. As such the last driver version 15.36.14.4080 were listed as DO NOT USE for SETI@home. As it would produce errors. When we were discussing iGPU drivers last. Version 10.18.10.4061 with 10.18.10.3621 as fall back were known to be good. Versions 4156 may be good as well, but falls into unknown/untested.


You may have to revert to an older release known to produce good results, although I don't know which one that would be for your hardware -- others are much better versed in the pros/cons of what really works vs. "latest and greatest".
ID: 1660914 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1660956 - Posted: 3 Apr 2015, 3:25:59 UTC - in response to Message 1660914.  

Updating drivers may or may not solve the problem. Quoting HAL9000 in this thread http://setiathome.berkeley.edu/forum_thread.php?id=76941

I wonder if that has to do with your driver version 10.18.14.4156. In the world of GPU crunching latest rarely is the greatest. As such the last driver version 15.36.14.4080 were listed as DO NOT USE for SETI@home. As it would produce errors. When we were discussing iGPU drivers last. Version 10.18.10.4061 with 10.18.10.3621 as fall back were known to be good. Versions 4156 may be good as well, but falls into unknown/untested.


You may have to revert to an older release known to produce good results, although I don't know which one that would be for your hardware -- others are much better versed in the pros/cons of what really works vs. "latest and greatest".

I have seen a few Haswell machines running 4156 without producing errors. Given the problem drivers tend to generate nearly 100% errors it is a good sign. I have not seen any Ivy Bridge system running it. I have not checked the driver to see if it supports Ivy Bridge or only the newer Haswell & Broadwell GPUs.
With GPU drivers & crunching "If it isn't broke don't fix it" really applies.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1660956 · Report as offensive
MaVac

Send message
Joined: 24 Mar 08
Posts: 3
Credit: 807,800
RAC: 0
Czech Republic
Message 1661986 - Posted: 6 Apr 2015, 14:25:50 UTC - in response to Message 1660914.  

Now it looks like there are no errors at all, maybe the updated client and drivers helped me. ;-)
ID: 1661986 · Report as offensive

Message boards : Number crunching : SETI@home v7 7.03 (opencl_intel_gpu_sah) - Computation Error


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.