Multiple problems running BOINC/Einstein
14 Feb 2005 19:07:40 UTC
Topic 187621
(moderation:
I have scanned the message board, but have not found definite answers to two buggy things I am finding with this (my first) attempt at running BOINC and Einstein@home:
System info:
Athlon 64, 3200+ at 2.0GHz, 1GB RAM
Windows XP Home SP2
ATI FireGL T2 video board
BOINC 4.19 downloaded 2/9/05
Problems:
Program runs well, then "locks up"; CPU usage stays at 100%, but in BOINC, "CPU Time" clock, "Progress" and "To Completion" clock freeze or change very slowly. Seems to be triggered especially by operation of other programs or by going in to screen saver mode. Windows error messages which might be related are: "BOINC GUI Error: Failed to clean up Windows Socket Interface", and "Application Error: The instruction at 0X0000000 referenced memory at 0X0000000 - The memory could not be read".
Screen saver graphic does not work. Bouncing "B" ball appears, with "App can't display graphics" message.
Thanks,
Drew Carhart
Naperville, Ill.
Multiple problems running BOINC/Einstein
)
Hi,
BOINC GUI Error: Failed to clean up Windows Socket Interface
This message appears when several instance of BOINC are running at the same time. If BOINC is started when Windows starts, and that you start BOINC again, you have this message.
Check that several instance of BOINC are not running at the same time.
Hope that helps a little...
Edit: As my english is not good I copy/paste a message from CPDN forum:
The message is one that you will get if you try to open more than one instance of BOINC.
This may be happening if you are trying to open BOINC from a start or desktop icon when it is running already. There will be a little BOINC icon in the Windows taskbar; to open the BOINC window right click on that and select 'show'.
It can also occur on startup because you have BOINC twice in startup folders - it could be in your own startup folder twice, or once there and once in the 'all users' folder.
It's down to the way that BOINC is checking that only a single instance is run. When the second boinc_gui program starts up it detects that there is another BOINC program running (it doesn't matter if it's boinc_gui or boinc_cli), so it terminates itself. The exit routine always cleans up the windows socket interface.
(copied from the Q&A section -thanks thyme lawn and andrew hingston)
If you get problems opening up the graphics window it's likely that you'll need to check to see if there are any updates to your graphics driver. Or possibly even rollback to the previous version of the driver (I had to do the other week on a laptop with a Radeon IGP 320M graphics card - the latest ATI driver update caused it to reboot every time I ran an OpenGL or DirectX application, and the BOINC graphics/screen saver is OpenGL).
source
Arnaud
Thanks for that insight,
)
Thanks for that insight, Arnaud;
Since the screensaver function is not working, the only way I can see what BOINC is doing is to open it up; that indeed may be what is causing that conflict. So, I can disble autorun and the screensaver function and start/run the program manually. It did appear that there were conflicts with other software, but they might all have been with the screensaver; I'll have to experiment more.
> I have scanned the message
)
> I have scanned the message board, but have not found definite answers to two
> buggy things I am finding with this (my first) attempt at running BOINC and
> Einstein@home:
>
> System info:
>
> Athlon 64, 3200+ at 2.0GHz, 1GB RAM
> Windows XP Home SP2
> ATI FireGL T2 video board
>
> BOINC 4.19 downloaded 2/9/05
>
> Problems:
> Program runs well, then "locks up"; CPU usage stays at 100%, but in BOINC,
> "CPU Time" clock, "Progress" and "To Completion" clock freeze or change very
> slowly. Seems to be triggered especially by operation of other programs or by
> going in to screen saver mode. Windows error messages which might be related
> are: "BOINC GUI Error: Failed to clean up Windows Socket Interface", and
> "Application Error: The instruction at 0X0000000 referenced memory at
> 0X0000000 - The memory could not be read".
>
> Screen saver graphic does not work. Bouncing "B" ball appears, with "App can't
> display graphics" message.
>
> Thanks,
> Drew Carhart
> Naperville, Ill.
If your screensaver is password protected boinc can't display the graphics. That maight be the cause or try to update the drivers for your graphicscard.