Welcome to MilkyWay@home

computation error on HD 6970 - drive 13.4


Advanced search

Message boards : Number crunching : computation error on HD 6970 - drive 13.4
Message board moderation

To post messages, you must log in.

AuthorMessage
HassanShebli

Send message
Joined: 2 Oct 10
Posts: 74
Credit: 18,362,557
RAC: 0
10 million credit badge9 year member badge
Message 58204 - Posted: 11 May 2013, 6:58:24 UTC

Hi:
I just downloaded the new driver and now all units shows " computation error "!!
What could be the problem?
ID: 58204 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
John Clark

Send message
Joined: 4 Oct 08
Posts: 1734
Credit: 64,228,409
RAC: 0
50 million credit badge10 year member badge
Message 58205 - Posted: 11 May 2013, 9:37:58 UTC

Assuming this driver is the latest AMD one (13.4 or 13.5beta), you may not know that AMD changed the OpenGL/OpenCL part of the driver on 13.1. This is said to be buggy compared to GPU drivers used before. That is OK for gaming but buggy for crunching. The recommended driver that seems to be in common usage is 12.8.

Make sure you uninstall all the AMD driver you use before installing 12.8, or the problem will persist. This means the following files after the initial Catalyst uninstall and reboot -

openCL.msi
SlotMaxinizerBe.dll} These are found in both the System32 and the WOW64
SlotMaximiserAgdll } folders (assuming you use a x64 OS.

amdocl.dll
OpenCL.dll
OpenVideo.dll
OVDecode.dll
Go away, I was asleep


ID: 58205 · 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
100 million credit badge10 year member badgeextraordinary contributions badge
Message 58211 - Posted: 11 May 2013, 17:57:38 UTC - in response to Message 58205.  
Last modified: 11 May 2013, 18:13:17 UTC

Interesting ..... I just got back to Crunching again, now I have been through the whole Working to Fully Retired thing in the last two years. My installation is therefore "clean" (as such). It happily runs V13.4 - going well in fact.

My hardware is not *that* much different - as such - (in a machro architecture sense) from Op's and yours. Its possible differences in base hardware 7XXX, 6XXX and 5XXX cause all this .... we'll see as they say. There has to be something lurking therefore inside yours and the Ops installation to cause this. As to who's *fault* that is - User or Developer - that is not really relevant.

I'll have a ferret and see if I can figure what the differences between Ops, Your's and Mine are to cause the difference, and my running installation.

Meanwhile it would help if you and the Op could give a - detailed - breakdown of the Primary machine used including - especially - software version numbers, utilities loaded blah blah (I'll do the same tonight). I will try and spot the potential differences that result in mine working and both yours not working on 13.4

As a starter, here are my version numbers from the screen found at:
Catalyst Control Center - Information - Software:

Driver Packing Version: 12.104-130328a-155980C-ATI
Catalyst Version: 13.4
2D Driver Version: 8.01.01.1295
Direct3D Version: 9.14.10.0969
Open GL Version: 6.14.10.12217
Catalyst Control Center Version: 2013.0328.2218.38225
AMD Audio Driver Version: 7.12.0.7714

Any drivers found older than the above should be updated before ripping apart anything else. Once we are on the same playing field with drivers, if there is then still a problem, it will be vastly easier to track down the gremlin.

Would be best to go through the whole "updating" thing to make a level playing field between us - usual Windows Updates et al. That would include all the less commonly updated drivers that often get left (sometimes for years). Those can easily be sorted out using:

RadarSync PC Updator http://www.radarsync.com (free, but try and make a well deserve donation however small - even just a few dollars would be good)

and

CCleaner Professional http://www.piriform.com(cheap as chips for the Professional Version which tags its menu Option to the Recycle Bin icon)

A third tool that is invaluable in my eyes is ARO, now in its 2013 incarnation. That's a bit more pricey, but when used in combination of Windows Update et al, and the two utilities above, you are good to go for anything.

http://www.sammsoft.com/ARO2013.aspx
(There will be a reaction against Samsoft from some people, but they haven't let me down yet. Good Software.

Both the first two especially, are written by a couple of the Classic Very Knowledgeable in depth tech guys, and they do a brilliant job, without making a song and dance about it all - highly recommended, they have never let me down yet - been using both since they first started up many moons ago - when used on top of the "standard" updating tools such as Windows Update et al. My Installation runs sweet, clean and no bother because of it. Samsoft are good in my eyes - horses for courses as they say.

All that is a bit of work, I am aware - but not *that* much - and you will come out of it with a well tuned, clean, humming installation, as well as solving the original problem.

Pays your money and takes your choice as they say :)

Regards
Zy
ID: 58211 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
John Clark

Send message
Joined: 4 Oct 08
Posts: 1734
Credit: 64,228,409
RAC: 0
50 million credit badge10 year member badge
Message 58212 - Posted: 11 May 2013, 22:53:21 UTC
Last modified: 11 May 2013, 23:04:42 UTC

Good to see you back here Zydor, and, I hope, enjoying retirement. I do and have been there 5 plus years now. But, I did have an interesting year last year playing with multiple myeloma and bone cancer. In long term remission now.

I am afraid my Milkyway rig is on my old dual Prestonia AGP Xeon making use of XP pro and an HD3850 running under Catalyst 11.6. As soon as I have posted this I will swap to the other PC and get the details from the Catalyst information centre, the equivalent to what you post (a bit later in this post).

When I recently purchased an HD7970 (slowly catching one of your rigs) I crunched Rainbow, and after 2 weeks the output generated 50% errors. This was tackled by much uninstalling, cleaning and reinstalling AMD drivers covering - 13.1, 13.2beta, 13.3beta, 13.4 and eventually back to 12.8. This is a different rig to my Milkyway one, but it crunched Milkyway flawlessly on 13.1 (my original driver. The list of files to remove after a driver uninstall came from a very knowledgeable project programmer.

When I uninstall and clean on my Win7 x64 PC I use the following AMD sourced file cleaner - <amd_cleanup_util_1.2.1.0>. Just Google for it.

It was this past week the erroring problem might have been solver, and may have been down to a failing PSU.

Now for the Catalyst specs for the XP Xeon -

Driver Packaging Version...........8.861-110524a-119610E-ATI
Catalystâ„¢ Version..................11.6
Provider AMD.
2D Driver Version..................6.14.10.7200
2D Driver File Path .............System/ControlSet002/Services/ati2mtag/Device0
Direct3D Version...................6.14.10.0841
OpenGL Version.....................6.14.10.10834
Catalystâ„¢ Control Center Version...2012.0308.2333.42157


Primary Adapter
Graphics Card Manufacturer........Built by AMD
Graphics Chipset..................ATI Radeon HD 3800 Series
Device ID.........................9505
Vendor............................1002

Subsystem ID......................9505
Subsystem Vendor ID...............1002

Graphics Bus Capability AGP
Maximum Bus Setting AGP 8X

BIOS Version 010.079.000.002
BIOS Part Number 113-AB43300-104
BIOS Date 2008/03/17

Memory Size 512 MB
Memory Type DDR3

Core Clock in MHz 669 MHz
Memory Clock in MHz 829 MHz
Go away, I was asleep


ID: 58212 · 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
100 million credit badge10 year member badgeextraordinary contributions badge
Message 58214 - Posted: 12 May 2013, 3:00:41 UTC - in response to Message 58212.  

Sorry to hear of the illness troubles .... fingers crossed for you :)

We are actually - in practice - not *that* far apart in the specs. Biggest difference is with your Catalyst version number (11.6) when the current is 13.4, that will be a major difference that needs eliminating.

The rest looks fine, being on V6 *shouldn't* be an issue (it could turn out to be, as V7 is a major change - I don't know if its an issue yet), but if you can get to V7, that would solve that. When doing the latter, a clean reinstall to V7 will probably be best overall if hardware allows, as you seem to have had to chop and change many versions.

Lots of clutter can get left behind as you sensibly point out, and since you have had some mega woes and hassles, probably best to get a clean install to V7 if possible - at least that would eliminate many potential causes, and set you up nicely for times ahead. Use utilities to get rid of any junk left behind in any large scale deletion - including deleting old circa V6 level directories left behind after alleged "deletion"

Nudge me when you feel you are ready and we can try and work from there ...

Regards
Zy
ID: 58214 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilearkayn
Avatar

Send message
Joined: 14 Feb 09
Posts: 999
Credit: 74,932,619
RAC: 0
50 million credit badge10 year member badge
Message 58215 - Posted: 12 May 2013, 7:01:44 UTC - in response to Message 58214.  

Sorry to hear of the illness troubles .... fingers crossed for you :)

We are actually - in practice - not *that* far apart in the specs. Biggest difference is with your Catalyst version number (11.6) when the current is 13.4, that will be a major difference that needs eliminating.

Regards
Zy


The maximum that he can go up to is about 12.1 if I remember correctly as that is where AMD cut off OpenCL support for XP.
ID: 58215 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
John Clark

Send message
Joined: 4 Oct 08
Posts: 1734
Credit: 64,228,409
RAC: 0
50 million credit badge10 year member badge
Message 58216 - Posted: 12 May 2013, 9:44:33 UTC

I work on the principle that if it is producing good validated work, and it doesn't seem to be broke, to leave well alone.

I should have said the AGP HD3850 is running BOINC7.0.64 (obviously x86 version).

My Win7 PC is currently crunching Donate, and seems to be error free (may be 3% to 5% errors very occasionally). When Donate's work fades (later today or Monday) I plan to return to Rainbow (where I got all the errors). If the work errors less than 5%, over a decent few days, then I will blame the PSU and not the drivers (as they were).

The clean up of .dlls (mainly) is sensible when changing drivers. For Win7 systems that AMD released cleaner clears most for te old files. But the SlotMazimiser Be and Ag files still need manually removing from both the System32 and the WOW64 folders.
Go away, I was asleep


ID: 58216 · 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
100 million credit badge10 year member badgeextraordinary contributions badge
Message 58219 - Posted: 12 May 2013, 10:14:02 UTC - in response to Message 58216.  

Don't forget Arkayn's comment .... you need to change Operating Systems from XP, without that you don't get off the starting block - you will not get past V13.1 to the current 13.4 due to the need to have OpenCL up and running with current versions. Without being on 13.4 you cant get onto current versions and get back on track with this.

The time to make the dreaded change of Core Operating System from XP has arrived :)

Regards
Zy
ID: 58219 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
John Clark

Send message
Joined: 4 Oct 08
Posts: 1734
Credit: 64,228,409
RAC: 0
50 million credit badge10 year member badge
Message 58230 - Posted: 12 May 2013, 17:01:47 UTC

I am leaving the dual Xeon on x32 XP for the time I keep it running.

When W2K ran out years ago, I had it protected by ESET's full suit and it ran faultlessly, and protected, until I recently upgraded it to XP pro.

No problem when the security patches stop coming in from my W2K experience.
Go away, I was asleep


ID: 58230 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemmstick
Avatar

Send message
Joined: 23 Nov 09
Posts: 29
Credit: 17,119,258
RAC: 0
10 million credit badge10 year member badge
Message 58257 - Posted: 14 May 2013, 8:52:34 UTC - in response to Message 58230.  
Last modified: 14 May 2013, 8:53:44 UTC

I am leaving the dual Xeon on x32 XP for the time I keep it running.

When W2K ran out years ago, I had it protected by ESET's full suit and it ran faultlessly, and protected, until I recently upgraded it to XP pro.

No problem when the security patches stop coming in from my W2K experience.

Why not use Linux? You'll get much faster processing speeds on Linux over that bloated, outdated, badly compiled OS.

Catalyst 13.4 on Linux works perfectly fine with this project.
ID: 58257 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : computation error on HD 6970 - drive 13.4

©2019 Astroinformatics Group