Issue with 7.2.28 and Notices

Author	Message
Steve Dodd Send message Joined: 28 Nov 09 Posts: 11	Message 51383 - Posted: 20 Nov 2013, 13:38:18 UTC Last modified: 20 Nov 2013, 13:40:41 UTC Hi all, I'm having an issue with the new version. After installation, I've noticed that I immediately get a notice for new messages. When I click the tab, I receive a displayed message that says something like "...retrieving messages." After a while, the application just exits. I think that the BOINC processes are still running, just the manager aborts. Anyone else having this issue. (I've notice it on at least 4 of my machines, all running Windows 7 Pro or higher. CPUs are Intel) ID: 51383 ·

Sirius B Send message Joined: 12 Jun 09 Posts: 2099	Message 51387 - Posted: 20 Nov 2013, 14:30:53 UTC - in response to Message 51383. Just finished updating here. Also exited after clicking on notices with the same message. ID: 51387 ·

Richard Haselgrove Volunteer tester Help desk expert Send message Joined: 5 Oct 06 Posts: 5082	Message 51390 - Posted: 20 Nov 2013, 15:13:31 UTC Could you both check whether you have a file called 'stderrgui.txt' in your BOINC data directory, please? And if so, is there a full runtime debugger log file in there? Don't (*please* don't :P) post the whole thing, but just check if it matches - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000000014018AAB8 read attempt to address 0x00000141 (are both addresses identical?) If so, the devs are aware, and your reports will give some useful extra routes by which the problem can be triggered. If your addresses are different, please tell us and hang on to the file - it might be needed for additional diagnosis. Thanks. ID: 51390 ·

Steve Dodd Send message Joined: 28 Nov 09 Posts: 11	Message 51406 - Posted: 21 Nov 2013, 0:44:51 UTC O.K. the short version of your request Richard :) Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000007FEFDFD2F11 write attempt to address 0x00000020 Engaging BOINC Windows Runtime Debugger... ****************** BOINC Windows Runtime Debugger Version 7.2.28 Dump Timestamp : 11/19/13 18:08:44 Loaded Library : dbghelp.dll Loaded Library : symsrv.dll Loaded Library : srcsrv.dll Loaded Library : version.dll Debugger Engine : 4.0.5.0 the first time ------------------------------------------------------------- Unhandled Exception Detected... - Unhandled Exception Record - Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000007FEFDFD2EF6 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... Reason: Access Violation (0xc0000005) at address 0x000007FEFDFD2EF6 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000007FEFDFD2EF6 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000007FEFDFD2EF6 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... ****************** BOINC Windows Runtime Debugger Version 7.2.28 Dump Timestamp : 11/20/13 02:55:35 Loaded Library : dbghelp.dll Loaded Library : symsrv.dll Loaded Library : srcsrv.dll Loaded Library : version.dll Debugger Engine : 4.0.5.0 the 2nd time ID: 51406 ·

Steve Dodd Send message Joined: 28 Nov 09 Posts: 11	Message 51407 - Posted: 21 Nov 2013, 0:52:43 UTC Richard, on my Xeon machine, I just got this when trying to read notices: Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x0000000077BFE4E4 write attempt to address 0x00000024 Engaging BOINC Windows Runtime Debugger... ******************** BOINC Windows Runtime Debugger Version 7.2.28 Dump Timestamp : 11/20/13 16:46:45 Loaded Library : dbghelp.dll Loaded Library : symsrv.dll Loaded Library : srcsrv.dll Loaded Library : version.dll Debugger Engine : 4.0.5.0 ID: 51407 ·

candido Send message Joined: 21 Nov 13 Posts: 1	Message 51408 - Posted: 21 Nov 2013, 1:57:48 UTC - in response to Message 51407. - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x00000001401D2F65 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... ID: 51408 ·

Sirius B Send message Joined: 12 Jun 09 Posts: 2099	Message 51409 - Posted: 21 Nov 2013, 5:43:37 UTC Last modified: 21 Nov 2013, 5:49:24 UTC Just booted up and Boinc stated 2 notices. opening the notices tab, total blank screen, seconds later Boinc shutdown. Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x75D39029 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... ******************** BOINC Windows Runtime Debugger Version 7.2.28 Dump Timestamp : 11/21/13 05:25:34 Loaded Library : dbghelp.dll Loaded Library : symsrv.dll Loaded Library : srcsrv.dll Loaded Library : version.dll Debugger Engine : 4.0.5.0 ID: 51409 ·

Richard Haselgrove Volunteer tester Help desk expert Send message Joined: 5 Oct 06 Posts: 5082	Message 51411 - Posted: 21 Nov 2013, 11:33:29 UTC Rom has posted a test version of BOINC which may alleviate some of these problems. Use at your own risk. Available installers: Windows 7.2.29 - boinc_7.2.29_windows_intelx86.exe - boinc_7.2.29_windows_x86_64.exe ID: 51411 ·

Sirius B Send message Joined: 12 Jun 09 Posts: 2099	Message 51412 - Posted: 21 Nov 2013, 12:55:00 UTC - in response to Message 51411. Thanks Richard. Just upgraded. It seems to be working okay now, but will keep an eye on it. ID: 51412 ·

Jord Volunteer tester Help desk expert Send message Joined: 29 Aug 05 Posts: 15483	Message 51444 - Posted: 22 Nov 2013, 8:46:05 UTC 7.2.31 is now recommended. It has the BOINC Manager crash fix. http://boinc.berkeley.edu/download.php ID: 51444 ·

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.