Welcome to MilkyWay@home

Computational error on new build


Advanced search

Message boards : Number crunching : Computational error on new build
Message board moderation

To post messages, you must log in.

AuthorMessage
NostradamusJones
Avatar

Send message
Joined: 27 Dec 14
Posts: 3
Credit: 123,243,556
RAC: 0
100 million credit badge7 year member badge
Message 64143 - Posted: 3 Dec 2015, 0:41:42 UTC

I'm getting a computational error on all work units that begin "de_80_dr8..."

Windows 10 64bit. 2500K. amd 6950. Current amd driver.

Any ideas? I'm a bit frustrated.

Let me know if you need any further info.

Thx so much :D
ID: 64143 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
captainjack

Send message
Joined: 22 Jun 13
Posts: 41
Credit: 58,159,999
RAC: 7,455
50 million credit badge8 year member badge
Message 64147 - Posted: 3 Dec 2015, 14:26:35 UTC

Hi NostradamusJones,

I also have an AMD 6950. When I ran Catalyst version 13.1 drivers, I could successfully run both "milky@home" tasks and "milkyway@home separation (modified fit)" tasks. Now that I have upgraded to a more recent version of Catalyst, I can no longer run the "milkyway@home" tasks. It is a known quirk of the AMD 6950.

If you really want to run the "milkyway@home" tasks, you will need to install the older drivers.

If you want to stay with current drivers you can simply exclude the "milkyway@home" tasks from your project preferences. This is what I chose to do.

Hope that helps.
ID: 64147 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
NostradamusJones
Avatar

Send message
Joined: 27 Dec 14
Posts: 3
Credit: 123,243,556
RAC: 0
100 million credit badge7 year member badge
Message 64151 - Posted: 4 Dec 2015, 15:49:14 UTC

Ahoy Cap'n Jack,

This sort of reinforces what I had concluded. When I would try to install 13.1, Windows 10 would be like, "No thanks, the basic generic microsoft display driver is better". I'm pretty sure I could go to Windows 7 and get it to work, but at this point it has become too much of a headache.

I had become a little tunnel visioned, thanks for the suggestion to do other projects. That's the route I'm going. I was just a big fan of the Milky Way project.

Thanks for stopping by, I wish you fair winds and following seas. :)
ID: 64151 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2797
Credit: 463,252,303
RAC: 6,908
300 million credit badge13 year member badgeextraordinary contributions badge
Message 64152 - Posted: 5 Dec 2015, 11:14:19 UTC - in response to Message 64151.  

Ahoy Cap'n Jack,

This sort of reinforces what I had concluded. When I would try to install 13.1, Windows 10 would be like, "No thanks, the basic generic microsoft display driver is better". I'm pretty sure I could go to Windows 7 and get it to work, but at this point it has become too much of a headache.

I had become a little tunnel visioned, thanks for the suggestion to do other projects. That's the route I'm going. I was just a big fan of the Milky Way project.

Thanks for stopping by, I wish you fair winds and following seas. :)


MilkyWay is trying to get enough funds to both stay running and to upgrade the Servers, ugrading the Servers would mean also updating the Boinc Server side software which should take care of the problems you are seeing. So if you leave keep an eye on things, they could get better as the money starts flowing in.
ID: 64152 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
disturber

Send message
Joined: 11 Jan 15
Posts: 8
Credit: 75,884,093
RAC: 0
50 million credit badge7 year member badge
Message 64156 - Posted: 6 Dec 2015, 6:54:32 UTC

I had issues with Windows 10 forcing the new AMD drivers down my throat. I ended up using third party software to remove the new driver from the hidden windows driver repository. After that, it still replaced the driver a few hours later, even after checking all the boxes telling windows not to update drivers. I disabled the service that installs drivers and had no problems since then. In my case the new driver added about 10% longer to the compute time, which is an unacceptable waste of electricity.

Mickey, how does the server side software fix this problem? I had the same slower compute time with Einstain@Home, so I rolled back drivers in Windows 7 for that. I think they have newer software, but I could be wrong.
ID: 64156 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2797
Credit: 463,252,303
RAC: 6,908
300 million credit badge13 year member badgeextraordinary contributions badge
Message 64157 - Posted: 6 Dec 2015, 11:13:31 UTC - in response to Message 64156.  

I had issues with Windows 10 forcing the new AMD drivers down my throat. I ended up using third party software to remove the new driver from the hidden windows driver repository. After that, it still replaced the driver a few hours later, even after checking all the boxes telling windows not to update drivers. I disabled the service that installs drivers and had no problems since then. In my case the new driver added about 10% longer to the compute time, which is an unacceptable waste of electricity.

Mickey, how does the server side software fix this problem? I had the same slower compute time with Einstain@Home, so I rolled back drivers in Windows 7 for that. I think they have newer software, but I could be wrong.


It won't, Win10 is causing it's own problems and as you discovered new drivers are NOT always better. What should be fixed though is the old Boinc Server version that MW is running that fails to see the R series cards without jumping thru hoops to use them.
ID: 64157 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
NostradamusJones
Avatar

Send message
Joined: 27 Dec 14
Posts: 3
Credit: 123,243,556
RAC: 0
100 million credit badge7 year member badge
Message 64163 - Posted: 10 Dec 2015, 2:55:03 UTC - in response to Message 64152.  

Ahoy Cap'n Jack,

This sort of reinforces what I had concluded. When I would try to install 13.1, Windows 10 would be like, "No thanks, the basic generic microsoft display driver is better". I'm pretty sure I could go to Windows 7 and get it to work, but at this point it has become too much of a headache.

I had become a little tunnel visioned, thanks for the suggestion to do other projects. That's the route I'm going. I was just a big fan of the Milky Way project.

Thanks for stopping by, I wish you fair winds and following seas. :)


MilkyWay is trying to get enough funds to both stay running and to upgrade the Servers, ugrading the Servers would mean also updating the Boinc Server side software which should take care of the problems you are seeing. So if you leave keep an eye on things, they could get better as the money starts flowing in.


Awesome, Mikey. I actually decided to purchase some different graphics cards. Stayin' on the Milky Way train!
ID: 64163 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Computational error on new build

©2022 Astroinformatics Group