I keep getting a runtime error on my pc (W7 pro)
I am running ver 6.10.60 with wX widgets ver 2.8.10 (whatever that means)
Any ideas
Hi Latoof
See http://www.wxwidgets.org/ (http://www.wxwidgets.org/)
Are you sure you downloaded the BOING ver 6.10.60 for Windows 7.
Download size for 32bit is 7.62 MB, and for 64 bit is 8.83 MB.
thanks for the reply, yeah seems I d/l the 32bit version and installed it :hbang:
I'll give the x64 a whirl
well that did not help
Bugger!!!!!! More info about the error please.
or
did you have any trouble with previous versions of BOINC? did it work at all 6.10.60? installed anything else?
Thanks for your continued interest in my problem
the previous version 6.10.58 IIRC (not sure if it was x64 or not) did it as well so I tried to upgrade to the latest version.
what more do you want? Where should I look for details?
Oh and I tried a uninstall/reboot/reinstall with no effect on error
BTW my XP laptop does not have any issues with BOINC
here's the error
[attachment deleted by admin]
Did you update BOINC over the top of an existing version without uninstalling it completely first (including manually deleting any BOINC folders and files in C:\Program Files and C:\ProgramData left over after uninstall)?
You will lose any work in progress and will have to reattach to your projects but doing a full uninstall and reinstall of BOINC clears things out properly when you are having trouble.
Are you doing MilkyWay ATI GPU by any chance? If yes update your video driver to a recent version such as Catalyst 11.3 BEFORE attaching to MilkyWay.
You could actually try upgrading to Catalyst 11.3 and see if it fixes things before completely uninstalling and reinstalling BOINC if you wish.
The new MilkyWay ATI application requires recent Catalyst drivers or it will give errors. Boinc.exe itself can refuse to run if the video card driver is not recognised properly.
Sometimes Windows Update can update the Catalyst driver to a version that is not compatible with BOINC and/or MilkyWay. To avoid problems with BOINC do not ever let Windows Update install a different Catalyst driver. Even if the Catalyst version is recent, the version installed by Windows Update may not contain the CAL/Stream/APP files necessary to enable your ATI card to be recognised properly by BOINC. When BOINC cannot recognise your video card, boinc.exe can go into a freeze mode trying to start and cause errors.
Yes Kashi and Prime Grid has the same problem.
Seems the problem started with 6.10.58 and continued when Latoof loaded the new version 6.10.60.
Looks like it is the actual work unit (exe) that is causing the problem. You would think it has to be the video driver (but then again .....)
Is there anything showing in the Action Centre? There should be an error showing on the windows log??? What about BOINC messages, anything there?
Are you crunching CPU or GPU or both. Does BOINC run properly with just CPU work units?
Best of luck mate
Not sure if the error is happening when you start BOINC or afterwards. If you wish to diagnose if it is a video card issue when starting BOINC you can use a cc_config.xml to disable GPUs in BOINC:
Don't start BOINC. Copy and paste the lines below in Notepad. Use Save as type: All files (*.*) and save it as cc_config.xml. Put this file in your BOINC Data directory. For Win 7 this is C:\ProgramData\BOINC. Then start BOINC. If BOINC starts successfully and it previously didn't you will know it is a video card issue (usually BOINC incompatible GPU driver).
<cc_config>
<options>
<no_gpus>1</no_gpus>
</options>
</cc_config>
You can just remove the cc_config.xml file when you no longer need it.
Although it is a release version I have read of some having trouble with BOINC 6.10.60. I am using beta version 6.12.22 on CPU and GPU projects with no problems if you wish to try it.
Hi and thanks to all for the posts/ideas..
I have narrowed things down, it appears to only happen when running climateprediction.net work units
Other projects I run are
Milkyway
Rosetta
Spinhenge
SETI
Docking
I did a Google search for "climateprediction.net runtime error"
1. seems like half the world is having trouble with CP
2. There is a link to the CP web site but am unable to access as their databases are down.
You might want to have a try yourself
thanks for the reply
I'll keep looking on the climatechange.net site and if I find an answer I'll post back
again - Thanks :thumbsup:
I don't know about the Runtime errors but I found most of the errored Climate Prediction tasks on your Windows 7 computer were Code 185 CreateProcess() failed - Access is denied. (0x5)
This is caused by something blocking BOINC from starting up the science application. Always check that you allowed BOINC through your firewall and exclude both the BOINC and BOINC Data directories from actively being scanned by your anti virus and anti spyware product(s).
Put BOINC (boinc.exe and boincmgr.exe) in the trusted zone of your firewall and only scan the directory or directories by hand with your anti-virus and other anti-malware software, after you closed down or suspended BOINC.
Another thing that mucks up Climate Prediction is users shutting down their computer without fully exiting BOINC first. Suspending the Climate Prediction tasks is not sufficient. Automatic software updates such as Windows Update that cause the computer to reboot may also cause these problems.
It does not surprise me that incompatible video card drivers are also known to cause problems with Climate Prediction as well as BOINC in general.
You have full access to the error messages, know exactly when they happen and are thus in a better position than me to have a look on the Climate Prediction forums for relevant information to see if you can fix the problem. With limited information I am shooting in the dark trying to diagnose a cause or suggest possible remedies. Good luck.
Quote from: kashi on April 23, 2011, 09:29:37 PM
found most of the errored Climate Prediction tasks on your Windows 7 computer were Code 185 CreateProcess() failed - Access is denied. (0x5)
Not sure if you meant this as a general comment or you have hacked my pc recently... :shock 'cause I don't recall posting any such info ::)
The work unit that causes the problem appears to be climateprediction.net task hadcm3n_o3v9_1900_40_007200344_2 using hadcm3n version 607
No other work causes the problem, not even the other climateprediction.net units
Haha, fear my überhacker skillz.:shock No, just checked details of tasks for your Win 7 computer on the Climate Prediction website. Thought I may be able to get an idea of what is wrong.
Good that you have narrowed down the cause. Perhaps better to abort that task giving continuing problems and try another or just run one Climate task. Running Climate Prediction on all available cores is very taxing on computer hardware, sometimes running Climate on one or more cores and other CPU projects on the other(s) gives more stability and may also result in better sec/TS as well. This can vary depending on which other CPU projects are run. You probably already know this.
Hard to finish a Climate task without an error, I remember when I was doing it on my A64 Clawhammer just about every task I attempted failed to finish and I only completed a few. Frustrating when some of them failed only 1 or 2 trickles before completion. The stages that had been completed were said to still be of some value at least. Had much more success on a Yorkfield quad running Linux, unless I tried running 4 Climate tasks at once which always resulted in slowdowns and errors.
Haven't done any Climate for a while, must give it another whirl after I get Yoyo to 250K. ;D
thanks to all for your interest and input to my problem.
I have done 2 things now and the issue appears resolved
1. checked my AV and discovered a couple of "apps" related to climateprediction were "restricted" - changed access rights
2. reset the project - drastic perhaps but decided to cut my losses as it were.
I now have two work units in progress and by suspending all other projects/work I forced both to run and no errors so far
Good to hear you've fixed it. Hope it continues to run OK for you now.
I'll have to check out the different models they have now. Last time I ran Climate I chose the older Slab models on Linux because they finished much quicker and granted higher credit rate than the newer models.