Errors running Einstein@home on Intel 2500 graphics
3 Aug 2013 21:06:28 UTC
Topic 197113
(moderation:
http://einsteinathome.org/host/8253267
This computer appears to be getting errors on all work units that it tries to run on its Intel HD 2500 graphics chip (i5-3570 CPU). The CPU tasks are completing normally, but I'm concerned that there is something wrong with the Intel GPU app, or with the configuration of my computer. I have tried updating to the latest Intel graphics drivers but it didn't have any effect. Any suggestions?
Errors running Einstein@home on Intel 2500 graphics
)
This is an example of the error information in one of the failed tasks. Apart from the task ID and the memory locations, they are all the same error.
Stderr output
7.0.64
(unknown error) - exit code -1073741819 (0xc0000005)
Activated exception handling...
[09:48:09][2748][INFO ] Starting data processing...
[09:48:09][2748][INFO ] Using OpenCL platform provided by: Intel(R) Corporation
[09:48:09][2748][INFO ] Using OpenCL device "Intel(R) HD Graphics 2500" by: Intel(R) Corporation
[09:48:11][2748][ERROR] Couldn't build OpenCL program (error: -11)!
[09:48:11][2748][INFO ] OpenCL shutdown complete!
-------------------
Error occured on Friday, August 2, 2013 at 09:48:11.
C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe caused an Access Violation at location 00d00000 Writing to location 00d00000.
Call stack:
00D00000
0040A4AD C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:0040A4AD releaseProgramKernels /home/jenkins/workspace/workspace/EAH-BRP/SLAVE/MINGW64-OPENCL/TARGET/win64-opencl/src/opencl/app/demod_binary_ocl.cpp:2205
0040A639 C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:0040A639 shutdown_ocl /home/jenkins/workspace/workspace/EAH-BRP/SLAVE/MINGW64-OPENCL/TARGET/win64-opencl/src/opencl/app/demod_binary_ocl.cpp:1874
0040B75E C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:0040B75E initialize_ocl /home/jenkins/workspace/workspace/EAH-BRP/SLAVE/MINGW64-OPENCL/TARGET/win64-opencl/src/opencl/app/demod_binary_ocl.cpp:347
00401EC1 C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:00401EC1 MAIN /home/jenkins/workspace/workspace/EAH-BRP/SLAVE/MINGW64-OPENCL/TARGET/win64-opencl/src/demod_binary.c:467
008488D8 C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:008488D8 main /home/jenkins/workspace/workspace/EAH-BRP/SLAVE/MINGW64-OPENCL/TARGET/win64-opencl/src/erp_boinc_wrapper.cpp:453
004013CE C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:004013CE __tmainCRTStartup /build/mingw-w64-RGpMuZ/mingw-w64-2.0.3/build/x86_64-w64-mingw32/all/mingw-w64-crt/../../../../mingw-w64-crt/crt/crtexe.c:309
004014E8 C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP5_1.39_windows_x86_64__BRP5-opencl-intel_gpu.exe:004014E8 mainCRTStartup /build/mingw-w64-RGpMuZ/mingw-w64-2.0.3/build/x86_64-w64-mingw32/all/mingw-w64-crt/../../../../mingw-w64-crt/crt/crtexe.c:195
7706652D C:\Windows\system32\kernel32.dll:7706652D BaseThreadInitThunk
7729C521 C:\Windows\SYSTEM32\ntdll.dll:7729C521 RtlUserThreadStart
-------------------
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000800D00000
Engaging BOINC Windows Runtime Debugger...
Looks like a problem with the
)
Looks like a problem with the driver installation (OpenCL can't start), but I see you've completed at least one task now. How did you fix it?
MrS
Scanning for our furry friends since Jan 2002
I'm sorry I didn't reply
)
I'm sorry I didn't reply earlier. I actually turned off GPU computing on that machine because I couldn't get it to work and forgot about this message thread. The computer did run a few CPU work units so the completed task(s) you saw were most likely CPU work units, not GPU.