Welcome to MilkyWay@home

Computation Errors on Cataylist 14.4

Questions and Answers : Windows : Computation Errors on Cataylist 14.4
Message board moderation

To post messages, you must log in.

AuthorMessage
Darrell
Avatar

Send message
Joined: 28 Mar 09
Posts: 9
Credit: 16,162,511
RAC: 0
Message 61829 - Posted: 2 Jun 2014, 23:07:43 UTC
Last modified: 2 Jun 2014, 23:15:15 UTC

Was running an integrated HD3000 and a HD5850 on 13.1, this weekend I shutdown the HD3000 and upgraded the HD5850 to cataylist 14.4. Finally got some Milkyway tasks this afternoon and all of the Milkyway@home 1.2 task are failing. They are failing with an unknown error or memory access violation errors.

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=757905567

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=757905568

The separation modified fit task are completing ok.

Any ideas?

Edit: The errors are happening when tasks hits 100% completion.
ID: 61829 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Alessandro Maitre [E.R.]

Send message
Joined: 27 Nov 09
Posts: 2
Credit: 1,293,837
RAC: 0
Message 61856 - Posted: 9 Jun 2014, 20:39:04 UTC

Same error for me. i have a 5870 and the same driver. The separation modified fit task are ok for me too but the Milkyway@home 1.2 say error when hit the 100%


- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00007FFC5871C520 read attempt to address 0x00000010


Any idea?
ID: 61856 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 61883 - Posted: 12 Jun 2014, 14:47:00 UTC
Last modified: 12 Jun 2014, 14:49:40 UTC

The single largest cause of errors in BOINC is running the cards too fast, and failing to regularly (aka once a week) clean out the cache and undate Windows etc etc. That's particularly so at Milkyway where the apps will rarely run at the full speed of current cards without falling over ( a good thing - means we are not tempted to run the things at full stretch 7 x 24).

Clean out the cache, restart and run it at default speed for a while, if you still get the same issue when running at default speed (and have thoroughly cleaned and updated the card) ..... then its time to scratch the 'ol brain. I acknowledge the reluctance in some to reduce speed drastically for a short while, but its by far and away the fastest way to resolve this.

If it works fine at default speed, slowly increase GPU speed until you get errors (give it an hour or so between upping the speed). When it falls over back off 10 and your good to go. Highly likely you will not be anywhere near the top speed the card is capable of, that's fine, its a (very good) software limitation, not hardware.

Regards
Zy
ID: 61883 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Alez

Send message
Joined: 15 Sep 12
Posts: 20
Credit: 105,341,548
RAC: 0
Message 61909 - Posted: 17 Jun 2014, 20:40:16 UTC

nope, error not caused by speed , over clocking etc,. etc.
This has been a long running issue. With 5xxx and 6xxx series cards you either have to remove milkyway v2 from your preferences and run mod fit or use cat 12.8 or earlier. All the 13 and 14 drivers cause these cards to error here with a memory violation.
ID: 61909 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Questions and Answers : Windows : Computation Errors on Cataylist 14.4

©2024 Astroinformatics Group