I just installed the newest version of BOINC 7.0.45 yesterday and since then I have been having a challenge keeping my BOINC system running without suspending and shutting down.

Its been next to impossible for me to try to determine what kind of problem might be occurring because once I notice that its suspended, the event log is also cleared so there are no clues to what may have happened to cause the shutdown of the entire program too.

I was not having this issue before I upgraded to 7.0.45 so I suspect it may have something to do with the new version but I don't know if anyone else is experiencing the same problem or not.

HELP!!! Most of the Projects I am listed as Barblovesroses

I hope the info below from the event log data gives you enough info to help you begin to trace what you need to figure this out. If there is anything else I can get for you, please ask and I'll be glad to get it for you as I'm frustrated at trying to restart the program constantly...I usually have to reboot my computer to get it going again and that's frustrating.


1/30/2013 3:23:12 AM Starting BOINC client version 7.0.45 for windows_x86_64
1/30/2013 3:23:12 AM log flags: file_xfer, sched_ops, task
1/30/2013 3:23:12 AM Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
1/30/2013 3:23:12 AM Data directory: C:\ProgramData\BOINC
1/30/2013 3:23:12 AM Running under account barb
1/30/2013 3:23:12 AM Processor: 4 AuthenticAMD AMD A8-3520M APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
1/30/2013 3:23:12 AM Processor: 1.00 MB cache
1/30/2013 3:23:12 AM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
1/30/2013 3:23:12 AM OS: Microsoft Windows 7: Home Premium x64 Edition, Service Pack 1, (06.01.7601.00)
1/30/2013 3:23:12 AM Memory: 5.48 GB physical, 10.96 GB virtual
1/30/2013 3:23:12 AM Disk: 673.79 GB total, 556.20 GB free
1/30/2013 3:23:12 AM Local time is UTC -5 hours
1/30/2013 3:23:12 AM VirtualBox version: 4.1.22
1/30/2013 3:23:12 AM CAL: ATI GPU 0: AMD Radeon HD 6x00 series (Sumo) (CAL version 1.4.1741, 512MB, 479MB available, 710 GFLOPS peak)
1/30/2013 3:23:12 AM OpenCL: ATI GPU 0: AMD Radeon HD 6x00 series (Sumo) (driver version 1084.4 (VM), device version OpenCL 1.2 AMD-APP (1084.4), 512MB, 479MB available, 710 GFLOPS peak)
1/30/2013 3:23:12 AM Reading preferences override file
1/30/2013 3:23:12 AM Preferences:
1/30/2013 3:23:12 AM max memory usage when active: 2804.95MB
1/30/2013 3:23:12 AM max memory usage when idle: 5048.92MB
1/30/2013 3:23:12 AM max disk usage: 30.00GB
1/30/2013 3:23:12 AM (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
1/30/2013 3:23:12 AM Not using a proxy
1/30/2013 3:40:56 AM Running CPU benchmarks
1/30/2013 3:41:28 AM Benchmark results:
1/30/2013 3:41:28 AM Number of CPUs: 4
1/30/2013 3:41:28 AM 1358 floating point MIPS (Whetstone) per CPU
1/30/2013 3:41:28 AM 3803 integer MIPS (Dhrystone) per CPU

1/30/2013 3:45:09 AM Reading preferences override file
1/30/2013 3:45:09 AM Preferences:
1/30/2013 3:45:09 AM max memory usage when active: 2804.95MB
1/30/2013 3:45:09 AM max memory usage when idle: 5048.92MB
1/30/2013 3:45:09 AM max disk usage: 30.00GB
1/30/2013 3:45:09 AM Not using a proxy


Near as I can tell this is the kind of info you ask for when someone is having a problem with their computer and BOINC...let me know if you need anything else.

Barb

I think I figured out what was causing the problem and I wanted to let you know what it was.

I had an error message from a job that was running from the VOLPEX project telling me that I had a task that was overdue and that I probably should abort it as I likely wouldn't get credit for it. This task was what was causing my entire BOINC system to suspend repeatedly.

Following is a capture of the message that I happened to capture once before a suspension happened and when I did abort the task. Doing that seemed to stop the problem that I was having. I sent the following message to the VOLPEX message board and wanted to share it with you as well:



I had the following message in my event log regarding a VOlpex task


1/30/2013 4:58:38 AM | VolPEx | Task 5116_volpex_worker_3311_1359526817 is 0.15 days overdue; you may not get credit for it. Consider aborting it.

I didn't think too much about it, however my entire BOINC system kept suspending repeatedly since earlier in the day and I couldn't figure out what was causing it and the event logs were also being deleted every time the system was suspended too.

The only thing that I could track down on my own was this Volpex task that kept showing up as needing to be aborted because of an overdue time on it, so I aborted it and that appears to have taken care of the issue I had so I thought I ought to report this situation to you so you could look into the issue in the event others may need to be aware of it too. I had also reported my concern to BOINC because I couldn't figure this out but I will let then know that I figured out the problem too.

Following is the rest of the event log that went along with the problem.

1/30/2013 4:58:39 AM | VolPEx | Sending scheduler request: Requested by project.
1/30/2013 4:58:39 AM | VolPEx | Not requesting tasks: project is not highest priority
1/30/2013 4:58:42 AM | VolPEx | Scheduler request completed
1/30/2013 4:59:58 AM | VolPEx | task 5116_volpex_worker_3311_1359526817 aborted by user
1/30/2013 4:59:59 AM | VolPEx | Computation for task 5116_volpex_worker_3311_1359526817 finished
1/30/2013 5:00:25 AM | VolPEx | update requested by user
1/30/2013 5:00:27 AM | VolPEx | Sending scheduler request: Requested by user.
1/30/2013 5:00:27 AM | VolPEx | Reporting 1 completed tasks
1/30/2013 5:00:27 AM | VolPEx | Not requesting tasks: project is not highest priority
1/30/2013 5:00:29 AM | VolPEx | Scheduler request completed


Barb

Why did you update to 7.0.45? It's not the recommended version, it's a development version and therefore can be unstable and crash. And when that happens, we always ask that you please please send the information to the BOINC alpha email list, so that the developers know about it. They don't read these forums.

If you wanted to be an alpha tester, you're welcome, the more the merrier. But then follow these instructions.

With that out of the way, it sounds like your client is crashing.
First check what the client last wrote in stdoutdae.txt in your BOINC Data directory C:\ProgramData\BOINC\
Then check if these crashes left any telling tale in the stderrdae.txt file in your BOINC Data directory C:\ProgramData\BOINC\
You can also check in Windows Even Viewer (Start->Administrative Tools->Event Viewer->Windows Logs->System & Application Logs) for any pointers (red and yellow markers) around the time of the crash.

And please, when you post logs, don't snip in them. The log you posted lacks any projects you've added to your BOINC, yet it also doesn't say it's not got any projects added... It may well be a project application that crashes that takes the client along with it. Not something you'd want to omit from any logs, just to 'hide' which projects you're running, or which hostIDs that's with.

---

I may have spoken too soon.

The problem is continuing today.

I thought I had a solution last night, but volpex was not the answer.

In answer to your question, another project recommended that I upgrade to fix a problem that was occuring in it with "file output missing message" so I did what they recommended to me to do. This problem kicked in after that happened.

I am not a "techie" person and am not sure that I will be able to figure out the suggestions you made but I will give them a try.

I was unaware of the desired assistance requirements for people running the beta version of BOINC. Perhaps it would be best if those requirements were posted at locations where people download the versions because I've been directed by various people in the past to download beta versions of BOINC to resolve problems I was having but no one ever told me about any of the requirements you just told me about regarding particpating and registering with the developers and the alpha email list. Please remember that not every person who decides to participate in BOINC is a computer wizard.

I contacted the BOINC Message board because I thought that this was the proper formum to contact when someone was having a problem with anything related to BOINC. I've never been made aware of a separate alpha email list until just now.

I wasn't intentionally hiding any logs, I thought I was providing info to a project that was causing the problem.

Maybe I should just go back and restore my computer back to before I installed this new BOINC version. That would probably be the simplest fix...

I wouldn't bother about the BOINC Alpha email list as the people there are only really interested in analysing bugs in the latest test version. They wouldn't be interested in helping you; they'd expect you to help them to improve BOINC.

If you aren't a tester, download your BOINC from here:

http://boinc.ssl.berkeley.edu/

Or if you have a backup that would allow you to revert to a stable version of BOINC that you had earlier, restore it.

VOLPEX is an alpha test project ie not for ordinary members who want an easy ride with projects and tasks that work. If you're running it you should be reporting bugs and problems on their forum. If you don't want to do this, or haven't got the time or expertise, the best thing would be to detach from VOLPEX or set it to No New Tasks in the Projects section of BOINC Manager.

I restored and things seem stable again thankfully.

I wont be in any hurry to upload new versions of BOINC Beta until they have been up and operating for several months in the future just to be on the safe side after this experience.

I've been working with the people at Volpex for a while now and haven't had any problems with their project until this problem with the new BOINC version, and yes, if there are problems, I do report to them directly at their message board.