Welcome to MilkyWay@home

All Milkyway@Home 1.39 tasks ending in computation error

Message boards : Number crunching : All Milkyway@Home 1.39 tasks ending in computation error
Message board moderation

To post messages, you must log in.

AuthorMessage
Will Guerin

Send message
Joined: 13 Jun 09
Posts: 3
Credit: 365,525
RAC: 0
Message 65428 - Posted: 12 Oct 2016, 18:52:15 UTC

All MW@H 1.39 WUs have been resulting in computation error after 2-3 seconds. This has been going on for about the past month or so. MW@H worked fine previously. I have made no hardware or software changes. All other projects (27) don't have this problem.

Example WU with problem:

Application - MilkyWay@Home 1.39 (opencl_ati_101)
Name - de_modfit_fast_19_3s_136_ModfitConstraints2_4_1476198705_2379401

Some basic system info:

Windows 10, 64 bit
AMD Phenom(tm) II X4 925 Processor [Family 16 Model 4 Stepping 2]
2x ATI Radeon HD 5700/6750/6770 series (Juniper)
Client version 7.6.22
VBox version 5.1.4r110228

Please let me know if any other info is required to troubleshoot.
ID: 65428 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 25 Feb 13
Posts: 580
Credit: 94,200,158
RAC: 0
Message 65432 - Posted: 12 Oct 2016, 21:13:12 UTC

Hi Will,

According to the error logs, your device does not support double precision which is required for the project. Is it possible your drivers changes as sometimes the drivers do not support double precision even though the card does. I know specifically Windows 10 has been doing some sketchy things to drivers after updates (specifically the anniversary update) or simply overwriting your drivers with Microsoft drivers. Let me know what you find.

Jake
ID: 65432 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Will Guerin

Send message
Joined: 13 Jun 09
Posts: 3
Credit: 365,525
RAC: 0
Message 65440 - Posted: 13 Oct 2016, 17:48:40 UTC - in response to Message 65432.  

Hi Jake,

Thanks for the follow-up and the info. Too bad to hear about the possible sly driver update that broke my capability to run certain MW&H WUs. I guess I'll just have to disable that certain application until I update my driver in the near future.

Thanks again!
ID: 65440 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
mmonnin

Send message
Joined: 2 Oct 16
Posts: 162
Credit: 1,004,365,858
RAC: 16,489
Message 65446 - Posted: 14 Oct 2016, 23:57:38 UTC

I've seen basically the same post across all GPU project forums. Win10 upgraded their driver and broke their crunching as doesn't come with OpenCL. FAH, Asteroids, E@H, MW, Collatz. The anniversary update has had an increase of 'it worked and now it doesn't' reports.
ID: 65446 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Un4given

Send message
Joined: 14 Feb 09
Posts: 19
Credit: 62,373,513
RAC: 0
Message 65931 - Posted: 20 Nov 2016, 20:54:08 UTC

I'm having problems with the files with bundle in their name. I might get 1 in 50 to complete. All the rest give computation errors. The ones that are just the plain old modifiedfit still work just fine.

Looks like I'm back to playing with the .ini file, because these new files are just broken without some tweaks.
ID: 65931 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Keith Myers
Avatar

Send message
Joined: 24 Jan 11
Posts: 696
Credit: 540,005,660
RAC: 86,841
Message 65932 - Posted: 21 Nov 2016, 0:54:17 UTC - in response to Message 65931.  

The computer you're having issues with hasn't been updated to the app version 1.43 yet which can handle the new bundled tasks. You should reset the project on that machine to pick up the new app.
ID: 65932 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : All Milkyway@Home 1.39 tasks ending in computation error

©2024 Astroinformatics Group