Questions and Answers : Windows : Computational error message
Message board moderation
Author | Message |
---|---|
Send message Joined: 3 Jan 06 Posts: 2 Credit: 2,025 RAC: 0 |
I checked my climate predict file, and it said computational error. I then went to the project screen and tried to update the file thinking maybe it had \"hung\" or \"crashed\" itself, now the whole project is missing from the WORK screen, but it still shows on the Project screen.The error message is gone, but I have no idea what to do next. |
Send message Joined: 28 Aug 04 Posts: 90 Credit: 2,736,552 RAC: 0 |
Your model chrashed by itself. Your machine should have already downloaded another work unit. If it hasn\'t so push the \'Update\' button in the projects screen and read the messages that are in the messages screen along your update. May be you have network activity at all or with the project suspended? If you use a dial up connection, you have to connect before pushing the update button. But the real reson of the crash of your first result is unknown. But you may exclude the experiment from sheduled and auto-protect virus scans as some virus scanners are locking the files they are scanning. But the experiment doesn\'t like it if its files are locked by another application. Maybe updating the driver of your graphics card may help. It might work, but must not. |
Send message Joined: 3 Jan 06 Posts: 2 Credit: 2,025 RAC: 0 |
Your model chrashed by itself. Your machine should have already downloaded another work unit. If it hasn\'t so push the \'Update\' button in the projects screen and read the messages that are in the messages screen along your update. May be you have network activity at all or with the project suspended? If you use a dial up connection, you have to connect before pushing the update button. 3/1/2006 8:55:51 PM|climateprediction.net|Unrecoverable error for result sulphur_if2a_000859330_0 (<file_xfer_error> <file_name>sulphur_if2a_000859330_0_1.zip</file_name> <error_code>-161</error_code> <error_message></error_message></file_xfer_error><file_xfer_error> <file_name>sulphur_if2a_000859330_0_2.zip</file_name> <error_code>-161</error_code> <error_message></error_message></file_xfer_error><file_xfer_error> <file_name>sulphur_if2a_000859330_0_3.zip</file_name> <error_code>-161</error_code> <error_message></error_message></file_xfer_error><file_xfer_error> <file_name>sulphur_if2a_000859330_0_4.zip</file_name> <error_code>-161</error_code> <error_message></error_message></file_xfer_error><file_xfer_error> <file_name>sulphur_if2a_000859330_0_5.zip</file_name> <error_code>-161</error_code> <error_message></error_message></file_xfer_error>) Pardon the excessive computerese, but this is what the actual error message looked like. As I don\'t really speak program very well, I have less than no idea what caused the crash. I have tried suspending and then resuming the program, updating it, etc. no help. All I got out of this was error code 161. Thank you, Theresa smith |
Send message Joined: 13 Jan 06 Posts: 1498 Credit: 15,613,038 RAC: 0 |
... Unfortunately the \'161\' error masks the underlying error (it simply means that the model ended without results to upload). In the absence of a clear reason for the model failing, we\'re left to guess and make general suggestions. * If you see a microsoft \'Send/DontSend\' dialogue, don\'t select anything until you have gone into boinc and selected \'exit\' from the menu. Hopefully the model will restart from the previous checkpoint rather than giving up and crashing. * If you use Norton or Sophos antivirus, exclude the boinc project directory from the automated scan. * Before playing games etc, set \'no more work\' and \'suspend\' the model - that way they won\'t tread on each other\'s toes. Sometimes simultaneous use of graphics drivers from two different programs seems to cause problems. * Watch out for firewall messages at the same time as when the model crashed, this has been mentioned a couple of times recently. * Run a stability test on your machine, I recommend Prime95 from www.mersenne.org (the \'torture test\' option). Run it for about 24 hours. If this fails, then there may be problems with overheating / overclocking etc, cleaning out dust from the motherboard and fans often helps if this is the case. * Make backups about once per week (of course if the model doesn\'t get that far it\'s not worth bothering!) I'm a volunteer and my views are my own. News and Announcements and FAQ |
©2025 cpdn.org