Message boards :
Number crunching :
BOINC Crash on start up, corrupt client_state.xml file (?)
Message board moderation
Author | Message |
---|---|
bobby Send message Joined: 22 Mar 02 Posts: 2866 Credit: 17,789,109 RAC: 3 |
After a couple of days of system instability caused it seems by a defective transformer on my cold cathode lights, which was running off the same power cable as my boot drive, I'm finally up and running. Unfortunately BOINC isn't, the client service stops with the error stack below. What I've tried so far: Upgrading to BOINC 6.2.19 from 6.2.19 Running the Prime95 Stress Test (as detailed on http://boincfaq.mundayweb.com/index.php?language=1&viewCat=5&sessionID=023fcb336cf2b6930fd264944b1b0f52). System config: Windows Vista SP1 64 bit, Intel Q9450 CPU, 8 GB RAM. Errors from stderrdae.txt: *** Dump of the Process Statistics: *** - I/O Operations Counters - Read: 199, Write: 224, Other 1345 - I/O Transfers Counters - Read: 802390, Write: 826, Other 18592 - Paged Pool Usage - QuotaPagedPoolUsage: 95072, QuotaPeakPagedPoolUsage: 96064 QuotaNonPagedPoolUsage: 7712, QuotaPeakNonPagedPoolUsage: 7712 - Virtual Memory Usage - VirtualSize: 7348224, PeakVirtualSize: 58687488 - Pagefile Usage - PagefileUsage: 7348224, PeakPagefileUsage: 7348224 - Working Set Size - WorkingSetSize: 11304960, PeakWorkingSetSize: 11304960, PageFaultCount: 2939 *** Dump of thread ID 8176 (state: Initialized): *** - Information - Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000 - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x00000000773178DE read attempt to address 0xFFFFFFFF - Registers - rax=000000000174e078 rbx=000000002a3e3a30 rcx=0000000000de0000 rdx=0000000000000000 rsi=0000000000de0000 rdi=000000002a3e3a40 r8=000000002a3e3a40 r9=0000000000000003 r10=0000000000000000 r11=000000000174b460 r12=0000000000d344a0 r13=0000000073819f70 r14=0000000000000000 r15=0000000000000000 rip=00000000773178de rsp=000000000174e000 rbp=0000000000000000 cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 - Callstack - ChildEBP RetAddr Args to Child 0174e070 771cceaa 029bb7e0 029d3b80 73819f70 737d3ead ntdll!RtlFreeHeap+0x0 0174e0a0 73766dfb 73819f70 00d344a0 029cd7d0 73766e97 kernel32!HeapFree+0x0 0174e0d0 71d95679 40089b10 000031c8 000031c8 4001a687 MSVCR80!free+0x0 0174e100 400194ec c90b8c43 0174fbbc c90b96f3 0174e130 MSVCP80!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::~basic_string<char,std::char_traits<char>,std::allocator<char> >+0x0 0174e140 40030233 029d09e0 40089b10 40089b10 00000000 boinc!+0x0 0174fd00 40011bbb 40089b10 40089b10 00000000 00000000 boinc!+0x0 0174fea0 400407c2 00000000 00000000 00000000 4004cf9a boinc!+0x0 0174fef0 4004d0b8 002cb1a0 00000000 002cea00 00000000 boinc!+0x0 0174ff20 fea8db45 00000000 00000000 00000000 00000000 boinc!+0x0 0174ff50 771c495d 00000000 00000000 00000000 00000000 ADVAPI32!SetServiceStatus+0x0 0174ff80 772f8791 00000000 00000000 00000000 00000000 kernel32!BaseThreadInitThunk+0x0 0174ffd0 00000000 00000000 00000000 00000000 00000000 ntdll!RtlUserThreadStart+0x0 *** Debug Message Dump **** *** Foreground Window Data *** Window Name : Window Class : Window Process ID: 0 Window Thread ID : 0 Exiting... Any and all help appreciated. TIA, Bobby I think you'll find it's a bit more complicated than that ... |
bobby Send message Joined: 22 Mar 02 Posts: 2866 Credit: 17,789,109 RAC: 3 |
Tried running BOINC in non-daemon mode from the command line and got the same dump but an extra line of info on start up: C:\>"C:\Program Files\BOINC\boinc.exe" 21-Nov-2008 18:59:52 [---] Starting BOINC client version 6.2.19 for windows_x86_64 21-Nov-2008 18:59:52 [---] log flags: task, file_xfer, sched_ops 21-Nov-2008 18:59:52 [---] Libraries: libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.3 21-Nov-2008 18:59:52 [---] Data directory: C:\ProgramData\BOINC 21-Nov-2008 18:59:52 [---] Running under account Bobby Kent 21-Nov-2008 18:59:52 [SETI@home] Found app_info.xml; using anonymous platform 21-Nov-2008 18:59:53 [---] [error] Can't handle file info in state file I had a backup of a really old state file and gave that a try, seemed to work, but given that it's old it doesn't reference any of the workunits I now have cached... The call stack also appears to implicate the state file: *** Dump of the Process Statistics: *** - I/O Operations Counters - Read: 197, Write: 0, Other 569 - I/O Transfers Counters - Read: 911190, Write: 0, Other 14070 - Paged Pool Usage - QuotaPagedPoolUsage: 117488, QuotaPeakPagedPoolUsage: 117488 QuotaNonPagedPoolUsage: 7616, QuotaPeakNonPagedPoolUsage: 7616 - Virtual Memory Usage - VirtualSize: 7618560, PeakVirtualSize: 69713920 - Pagefile Usage - PagefileUsage: 7618560, PeakPagefileUsage: 7618560 - Working Set Size - WorkingSetSize: 11063296, PeakWorkingSetSize: 11063296, PageFaultCount: 2712 *** Dump of thread ID 7076 (state: Initialized): *** - Information - Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000 - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x00000000777178DE read attempt to address 0xFFFFFFFF - Registers - rax=000000000012dec8 rbx=000000002a3e3a30 rcx=0000000000ea0000 rdx=0000000000000000 rsi=0000000000ea0000 rdi=000000002a3e3a40 r8=000000002a3e3a40 r9=0000000000000000 r10=0000000072060000 r11=0000000000000200 r12=0000000000da40c0 r13=0000000072119f70 r14=0000000000000000 r15=0000000000000000 rip=00000000777178de rsp=000000000012de50 rbp=0000000000000000 cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 - Callstack - ChildEBP RetAddr Args to Child 0012dec0 775cceaa 033bc1d0 033d3690 72119f70 720d3ead ntdll!RtlFreeHeap+0x0 0012def0 72066dfb 72119f70 00da40c0 033cd2e0 72066e97 kernel32!HeapFree+0x0 0012df20 72165679 40089b10 000031c8 000031c8 4001a687 MSVCR80!free+0x0 0012df50 400194ec 8ae78c0d 0012fa0c 8ae7e95d 0012df80 MSVCP80!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::~basic_string<char,std::char_traits<char>,std::allocator<char> >+0x0 0012df90 40030233 033d04f0 40089b10 40089b10 00130000 boinc!FILE_INFO::~FILE_INFO+0xd (c:\src\boincsvn\branches\boinc_core_release_6_2\client\client_types.c:653) 0012fb50 40011bbb 40089b10 40089b10 00000000 00130000 boinc!CLIENT_STATE::parse_state_file+0x11 (c:\src\boincsvn\branches\boinc_core_release_6_2\client\cs_statefile.c:178) 0012fcf0 400407c2 00130000 0012fd20 00000000 400403c8 boinc!CLIENT_STATE::init+0x0 (c:\src\boincsvn\branches\boinc_core_release_6_2\client\client_state.c:230) 0012fd40 40040ca7 00000001 00388c60 00000000 777192f7 boinc!boinc_main_loop+0x0 (c:\src\boincsvn\branches\boinc_core_release_6_2\client\main.c:460) 0012ff20 4004efd0 00130000 13199096 00130000 00000000 boinc!main+0x5 (c:\src\boincsvn\branches\boinc_core_release_6_2\client\main.c:733) 0012ff50 775c495d 00000000 00000000 00000000 00000000 boinc!__tmainCRTStartup+0x19 (f:\sp\vctools\crt_bld\self_64_amd64\crt\src\crtexe.c:597) 0012ff80 776f8791 00000000 00000000 00000000 00000000 kernel32!BaseThreadInitThunk+0x0 (f:\sp\vctools\crt_bld\self_64_amd64\crt\src\crtexe.c:597) 0012ffd0 00000000 00000000 00000000 00000000 00000000 ntdll!RtlUserThreadStart+0x0 (f:\sp\vctools\crt_bld\self_64_amd64\crt\src\crtexe.c:597) *** Debug Message Dump **** *** Foreground Window Data *** Window Name : Window Class : Window Process ID: 0 Window Thread ID : 0 Exiting... I guess it got corrupted, is there any way to fix this? I think you'll find it's a bit more complicated than that ... |
bobby Send message Joined: 22 Mar 02 Posts: 2866 Credit: 17,789,109 RAC: 3 |
Went for the easy option and reset the project. All appears well now. Thread can be closed. I think you'll find it's a bit more complicated than that ... |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14654 Credit: 200,643,578 RAC: 874 |
Did you happen to preserve the damaged statefile for inspection, before replacing it with the old one? No matter what was wrong with it, no data error should make a properly-written application crash as badly as that. And since you're using a still-current v6.2.19 BOINC, I think the BOINC developers should be made aware of this. |
©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.