Questions and Answers :
Windows :
Visual Fortran run-time error
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 May 10 Posts: 2 Credit: 39,768 RAC: 0 |
Hi, I don't if this i the right place where to ask for help... Anyway, I'll start from here. In the last 5 days I'm getting a run-time error during climate-prediction simulation. Here is the message I get: --------------------------- Visual Fortran run-time error --------------------------- forrtl: severe (24): end-of-file during read, unit 20, file C:\ProgramData\BOINC\projects\climateprediction.net\hadsm3dhet2_k3qr_006614501\fort.20 Image PC Routine Line Source hadsm3_se_6.07_wi 0056E572 Unknown Unknown Unknown Stack trace terminated abnormally. --------------------------- OK --------------------------- Is there something I can do to fix the problem? Are you aware of this problem? Thanks. |
Send message Joined: 2 May 10 Posts: 2 Credit: 39,768 RAC: 0 |
Maybe I should have added some info. Here are some details about my system: Hewlett-Packard Pavilion dv6 Notebook Intel(R) Core(TM) i7 CPU (1.6 GHz) 4GB ram Windows 7 Home Premium, 64 bit |
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
This problem has been around for years, but the bad news is that there's no definitive answer or cure. It just happens to some computers some of the time. There have been a few suggestions of things to try, but I forget what they were. If you look down the list of posts below yours, you'll see a few other mentions about Fortran. Some of them may contain links to "answers". Backups: Here |
Send message Joined: 27 Apr 05 Posts: 1 Credit: 33,010 RAC: 0 |
I have the same problem. Here are some details about my system: Dell inspiron 1520 Intel(R) Core(TM) 2 duo CPU T750 (2.2 GHz) 4GB ram Windows 7 ultimate, 64 bit |
Send message Joined: 13 Aug 09 Posts: 1 Credit: 960,445 RAC: 14,033 |
I am also having the same issue with the Visual Fortran error. My system is AMD , running Vista Business A most annoying problem as the jobs I am getting from you are huge and span a 1 year deadline. I dont mind using the PC to work on these projects but having it fail into a month of computing is a waste of processing power I could donate elsewhere. please look into this or I may be forced to no longer accept these failing jobs. NOTE: your jobs used to run fine this problem is only in the last couple/several months. And my system has not changed. Thanks |
Send message Joined: 5 Aug 04 Posts: 1496 Credit: 95,522,203 RAC: 0 |
I am also having the same issue with the Visual Fortran error. It has been known since starting this project seven years ago that the scientists gain usable information from failures (i.e., those failures not caused by users' machines). The current FAMOUS Tasks use parameter sets testing the envelope of scientifically-valid parameter space. In so doing, many attempts will fail. The failures are valuable because they help define reasonable settings. At this point in the exercise, the failures are, perhaps, more valuable than the completions. Case in point: Beta currently has a version with a parameter accidentally set too high by a factor of ten. Every one of these Tasks fail. Still, the lead scientist on the CPDN FAMOUS project asked us to run more of them because they give him valuable date to evaluate. By the way, these Task are short, VERY short, compared to what we used to run. Edit: Numerous posts exist on these Boards re. Visual Fortran error. (Use the "Advanced search" option.) "We have met the enemy and he is us." -- Pogo Greetings from coastal Washington state, the scenic US Pacific Northwest. |
Send message Joined: 29 Sep 04 Posts: 2363 Credit: 14,611,758 RAC: 0 |
To add a bit to what Astro says: Franco, you've had two types of error. * This FAMOUS crashed with error code 22 and forrtl: severe (47) (visual fortran run time library, visual fortran being the language that the models are written in). On the model's page click on stderr out + to see the messages. They include 'write to READONLY file'. This apparently usually happens when an AV scan happens while the model's running and locks the file. The solution is to exclude all Boinc and climateprediction files from AV scans, or only to run scans after fully exiting from Boinc. * More than one model type has the error code 1073807364 (0x40010004). This is caused by not fully exiting from Boinc before shutting down the computer. There's a Boinc FAQ about it here. To fully exit from Boinc right-click on the Boinc icon at the bottom of the screen and select Exit. If you get a pop-up dialogue when you do this, check the boxes. Or you can do it from the open Boinc manager: File > Exit. Suspending the models isn't sufficient. Closing the Boinc manager window isn't sufficient. You must fully exit from Boinc. The only model types available at the moment are FAMOUS. You can read about them in the form News thread at the top of the Number Crunching section. About 6 posts before the end of that thread. You can subscribe to the News thread and receive an email about new announcements, but you need to enable email notification in the Community preferences of your account. When new model types are released that's where we'll describe them. Cpdn news |
©2024 climateprediction.net