You are a great resource, thank you for your advice. I would have never thought to check the debug flags and even I didn't investigate that option until just now with your pointer.
I am dealing with three different notebooks running boinc and the Einstein@Home project. The one I am using to write this comment is the ACER Aspire 7730Z. I toggled the Event Log Diagnostic Flag and found that the scrsaver_debug was not enabled, so I put the check mark next to it to enable it, saved and closed the ELDF.
However, I am able to get new tasks and run the screensaver albeit still no constellation lines. I downloaded the latest BM the other day,
The earlier post was concerning the Dell Inspiron notebook with the 4 tasks running but nothing happens when pushing the "Show Graphics" button. I will close this post now and start up the Dell to check the status of the ELDF scrsaver_debug flag.
FWIW & IIRC & IMHO The following occurs to me : for some time now the driver of the video subsystem/card is not required to support earlier versions of OpenGL to claim compliance to OpenGL standards. Thus the Starsphere screensaver - as written using early OpenGL contexts ( version 1.x ? ) - may not function correctly ( including not working at all ), even when run on hardware that apparently supports OpenGL. That ought manifest as runtime OpenGL errors, but I don't recall whether or not the screensaver code checks & reports this.
For that matter, where is the screensaver source code available these days ??
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
True, but in Bobby's case that shouldn't be the case as the screensaver works, in principle. It's "just" closed "prematurely" which indicates a different reason. Also, our tests so far didn't reveal any OpenCL incompatibilities but those test can't possibly include all system variants of course.
Thanks to Oliver I checked the debug flags and selected the screensaver debug by placing the check mark next to it. I also selected the Apply button saved and closed the debug toggle. Afterwords, immediately, there was no change meaning still nothing happening when I pushed the Show Graphics button.
I decided to leave the computer on crunching the tasks running over night. About 50% of the tasks were complete at the time.
So, I get up this morning and checked the computer and noticed it just completed all 4 tasks, reported the work done, downloaded new tasks and started to crunch them.
Then I just thought go ahead John and click on the Show Graphics button to see if anything had changed. THEY HAD! now have the stars sphere happily working on this computer,
I can't thank Oliver enough for his help and patience with my posts!
I checked the event log for the screen saver and cleaned out old messages. I left the computer alone long enough to activate the screen saver and it did the same thing with flashing once for loading, once for the stats and the star globe flashed and then it cycled back. This is what the error message reads:
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x00007FFB95E1A859
Engaging BOINC Windows Runtime Debugger...
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00007FF65B2ECC00 read attempt to address 0x00000050
Engaging BOINC Windows Runtime Debugger...
That is the end of the file. Where do I look now? I have been activating just the star globe by itself and maximizing the window so I see the star globe, but this is not a screen saver, just a program running.
I have been activating just the star globe by itself and maximizing the window so I see the star globe, but this is not a screen saver, just a program running.
And I take that works as expected? If so, this is hard proof (another) that the graphics app isn't at fault here. The graphics app is the same as the (starsphere) screensaver. The difference is only the way it's launched. It appears when launched by the BOINC screensaver, the BOINC screensaver runs into a memory issue, as stated by the log entries:
Quote:
Reason: Out Of Memory (C++ Exception)
Reason: Access Violation (0xc0000005)
Is there a memory problem on your PC, in particular when you're running BOINC tasks? Is BOINC (and its screensaver) at its latest version?
As stated in a different thread, for me the following happens (in short):
- I can start the graphics for the workunits with the button (working fine)
- The screensaver, however, does not start up and ends up in an endless loop of "loading screensaver", failing, loading again...
----------------
Longer version:
stderr.txt:
...
2021-02-22 15:44:11.3980 (18108) [normal]: Start of BOINC application 'C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einstein_O2MD1_2.09_windows_x86_64__GWnew.exe'.
Activated exception handling...
15:44:11 (18108): Can't open init data file - running in standalone mode
2021-02-22 15:44:11.4000 (18108) [CRITICAL]: ERROR: no result file has been specified
...
stderrgfx.txt:
...
15:43:45 (7544): Can't open init data file - running in standalone mode
No node found using XPath expression: /project_preferences/graphics/@fps
No node found using XPath expression: /project_preferences/graphics/@quality
No node found using XPath expression: /project_preferences/graphics/@width
No node found using XPath expression: /project_preferences/graphics/@height
15:43:45 (7544): Can't open init data file - running in standalone mode
No node found using XPath expression: /project_preferences/graphics/@fps
No node found using XPath expression: /project_preferences/graphics/@quality
No node found using XPath expression: /project_preferences/graphics/@width
No node found using XPath expression: /project_preferences/graphics/@height
15:43:45 (7544): Can't open init data file - running in standalone mode
15:43:45 (7544): Can't open init data file - running in standalone mode
...
Running on Windows 10.
Graphics do work if I start them from BOINC-Manager for any given workunit.
I have uninstalled BOINC, deleted ALL local files, reinstalled and the screensaver worked exactly once. Next start (after 5 Minutes of idle) produced this error again.
EDIT:
I changed the settings here on the website (1920x1080, 60 fps)... refreshed the project in BOINC-Manager and it worked... extactly once. Now it is broken again.
:-(
Thanks for the report. This appears to be a problem with the science app (stderr.txt), not the screensaver (stderrgfx.txt). Are you sure the former is running correctly (your computers are hidden)? Also, when you start the graphics app manually via the BOINC Manager, does it actually show details about the running task or just empty placeholders?
Hi Oliver, You are a great
)
Hi Oliver,
You are a great resource, thank you for your advice. I would have never thought to check the debug flags and even I didn't investigate that option until just now with your pointer.
I am dealing with three different notebooks running boinc and the Einstein@Home project. The one I am using to write this comment is the ACER Aspire 7730Z. I toggled the Event Log Diagnostic Flag and found that the scrsaver_debug was not enabled, so I put the check mark next to it to enable it, saved and closed the ELDF.
However, I am able to get new tasks and run the screensaver albeit still no constellation lines. I downloaded the latest BM the other day,
The earlier post was concerning the Dell Inspiron notebook with the 4 tasks running but nothing happens when pushing the "Show Graphics" button. I will close this post now and start up the Dell to check the status of the ELDF scrsaver_debug flag.
Regards,
John
FWIW & IIRC & IMHO The
)
FWIW & IIRC & IMHO The following occurs to me : for some time now the driver of the video subsystem/card is not required to support earlier versions of OpenGL to claim compliance to OpenGL standards. Thus the Starsphere screensaver - as written using early OpenGL contexts ( version 1.x ? ) - may not function correctly ( including not working at all ), even when run on hardware that apparently supports OpenGL. That ought manifest as runtime OpenGL errors, but I don't recall whether or not the screensaver code checks & reports this.
For that matter, where is the screensaver source code available these days ??
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Hey Mike, long time no
)
Hey Mike, long time no see!
True, but in Bobby's case that shouldn't be the case as the screensaver works, in principle. It's "just" closed "prematurely" which indicates a different reason. Also, our tests so far didn't reveal any OpenCL incompatibilities but those test can't possibly include all system variants of course.
The source can be found here.
Stay safe mate,
Oliver
Einstein@Home Project
Oliver Behnke wrote: Hey
)
Hi Oliver! Indeed. Nearly ten years I think.
And you too. At least we have a vaccine or three coming.
Maybe I'll get to 'drop in' one of these years ... LOL ;-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Well, folks I've got some
)
Well, folks I've got some good news!
Thanks to Oliver I checked the debug flags and selected the screensaver debug by placing the check mark next to it. I also selected the Apply button saved and closed the debug toggle. Afterwords, immediately, there was no change meaning still nothing happening when I pushed the Show Graphics button.
I decided to leave the computer on crunching the tasks running over night. About 50% of the tasks were complete at the time.
So, I get up this morning and checked the computer and noticed it just completed all 4 tasks, reported the work done, downloaded new tasks and started to crunch them.
Then I just thought go ahead John and click on the Show Graphics button to see if anything had changed. THEY HAD! now have the stars sphere happily working on this computer,
I can't thank Oliver enough for his help and patience with my posts!
Regards,
John
Lots of good info here. It
)
Lots of good info here. It will take me a while to crunch it. I will let you know how it all turns out.
Thanks
Bobby
Oliver: I checked the
)
Oliver:
I checked the event log for the screen saver and cleaned out old messages. I left the computer alone long enough to activate the screen saver and it did the same thing with flashing once for loading, once for the stats and the star globe flashed and then it cycled back. This is what the error message reads:
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x00007FFB95E1A859
Engaging BOINC Windows Runtime Debugger...
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00007FF65B2ECC00 read attempt to address 0x00000050
Engaging BOINC Windows Runtime Debugger...
That is the end of the file. Where do I look now? I have been activating just the star globe by itself and maximizing the window so I see the star globe, but this is not a screen saver, just a program running.
Thanks
Bobby
I have been activating just
)
And I take that works as expected? If so, this is hard proof (another) that the graphics app isn't at fault here. The graphics app is the same as the (starsphere) screensaver. The difference is only the way it's launched. It appears when launched by the BOINC screensaver, the BOINC screensaver runs into a memory issue, as stated by the log entries:
Is there a memory problem on your PC, in particular when you're running BOINC tasks? Is BOINC (and its screensaver) at its latest version?
Oliver
Einstein@Home Project
As stated in a different
)
As stated in a different thread, for me the following happens (in short):
- I can start the graphics for the workunits with the button (working fine)
- The screensaver, however, does not start up and ends up in an endless loop of "loading screensaver", failing, loading again...
----------------
Longer version:
stderr.txt:
...
2021-02-22 15:44:11.3980 (18108) [normal]: Start of BOINC application 'C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einstein_O2MD1_2.09_windows_x86_64__GWnew.exe'.
Activated exception handling...
15:44:11 (18108): Can't open init data file - running in standalone mode
2021-02-22 15:44:11.4000 (18108) [CRITICAL]: ERROR: no result file has been specified
...
stderrgfx.txt:
...
15:43:45 (7544): Can't open init data file - running in standalone mode
No node found using XPath expression: /project_preferences/graphics/@fps
No node found using XPath expression: /project_preferences/graphics/@quality
No node found using XPath expression: /project_preferences/graphics/@width
No node found using XPath expression: /project_preferences/graphics/@height
15:43:45 (7544): Can't open init data file - running in standalone mode
No node found using XPath expression: /project_preferences/graphics/@fps
No node found using XPath expression: /project_preferences/graphics/@quality
No node found using XPath expression: /project_preferences/graphics/@width
No node found using XPath expression: /project_preferences/graphics/@height
15:43:45 (7544): Can't open init data file - running in standalone mode
15:43:45 (7544): Can't open init data file - running in standalone mode
...
Running on Windows 10.
Graphics do work if I start them from BOINC-Manager for any given workunit.
I have uninstalled BOINC, deleted ALL local files, reinstalled and the screensaver worked exactly once. Next start (after 5 Minutes of idle) produced this error again.
EDIT:
I changed the settings here on the website (1920x1080, 60 fps)... refreshed the project in BOINC-Manager and it worked... extactly once. Now it is broken again.
:-(
Thanks for the report. This
)
Thanks for the report. This appears to be a problem with the science app (stderr.txt), not the screensaver (stderrgfx.txt). Are you sure the former is running correctly (your computers are hidden)? Also, when you start the graphics app manually via the BOINC Manager, does it actually show details about the running task or just empty placeholders?
Cheers,
Oliver
Einstein@Home Project