Need Help - HD3850 AGP & Cat 8.12 +

Halaluyah! I got the 0.19 opti CPU SSE2 app to run on the machine. If only the GPU card would play nice...

The lastest failure on the GPU card gave a lot more information on the issue I'm having. Seems I got a access error, and if I remember correctly, isn't a good sign. Anyway, this is the partial message. Hopefully someone with much more knowledge can decipher the error. Thanks for all the help.

Task ID 50822600
Name ps_s22_15_4866631_1240681273_0
Workunit 50053993
Created 25 Apr 2009 17:41:17 UTC
Sent 25 Apr 2009 17:43:00 UTC
Received 25 Apr 2009 17:44:30 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xffffffffc0000005)
Computer ID 66505
Report deadline 28 Apr 2009 17:43:00 UTC
CPU time 0.09375
stderr out <core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
Running Milkyway@home ATI GPU application version 0.19e by Gipsel
CPU: AMD Athlon(tm) 64 Processor 3400+ (1 cores/threads) 2.41192 GHz (883ms)

Running Milkyway@home ATI GPU application version 0.19e by Gipsel
CPU: AMD Athlon(tm) 64 Processor 3400+ (1 cores/threads) 2.41192 GHz (3343ms)

CAL Runtime: 1.3.145


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0144147E write attempt to address 0x00000000

Engaging BOINC Windows Runtime Debugger...

This set up should work from a clean install of windows, so you might want to remove most of the fluff you've installed already.

Relevant files should be available from guru3d.com.

Assuming XP-32bit:

Catalyst 8.12, then the 8.12 AGP hotfix.
.Net Framework 3.5
DirectX 9.0c

Delete everything from your BOINC/milkyway directory.
Then copy the 0.19e files all to your BOINC/milkyway directory:

app_info.xml
astronomy_0.19_ATI_SSE2e.exe
brook.dll

This should be all you need.

During this time, make sure BOINC is completely closed and shut off.

---

This set up should work from a clean install of windows, so you might want to remove most of the fluff you've installed already.

Relevant files should be available from guru3d.com.

I got the app from Zslip.com - same app?

Assuming XP-32bit:

Catalyst 8.12, then the 8.12 AGP hotfix.
.Net Framework 3.5
DirectX 9.0c

Assumption correct. Done all that. The normal Cat 8.12 wouldn't install. Installed the Cat 8.12 hotfix for the HD3850 AGP card. The only thing I did differently was install the "hacked" version of DirectX 10 for XP, but I had the errors under DirectX 9.0c. It appears that DirectX 10.0 doesn't want to come off of the machine. I did the uninstall but had messages that some components were in use. Tried to overlay with DirectX 9.0c from MS, but when I run DXDIAG, it still shows DirectX 10.0.

Delete everything from your BOINC/milkyway directory.
Then copy the 0.19e files all to your BOINC/milkyway directory:

app_info.xml
astronomy_0.19_ATI_SSE2e.exe
brook.dll

This should be all you need.

During this time, make sure BOINC is completely closed and shut off.

Did this also, except not deleting everything in the directory. I did detach & reattach to Milkyway and had an empty directory. I then put the 4 files for the ATI GPU app (includes the readme.txt file) and restarted. When MW downloaded WUs, it also downloaded the stock CPU app and went about its merry way. I'll try this 1 more time, but that means blowing out 5, precious WUs from MW.

Well I did all that and wasted 6 more WUs. Latest error message shows access error again:

Task ID 50877999
Name ps_s23_15_4921187_1240689687_0
Workunit 50108549
Created 25 Apr 2009 20:01:31 UTC
Sent 25 Apr 2009 20:03:14 UTC
Received 25 Apr 2009 20:05:17 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xffffffffc0000005)
Computer ID 66505
Report deadline 28 Apr 2009 20:03:14 UTC
CPU time 0.453125
stderr out <core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
Running Milkyway@home ATI GPU application version 0.19e by Gipsel
CPU: AMD Athlon(tm) 64 Processor 3400+ (1 cores/threads) 2.41192 GHz (2147ms)

CAL Runtime: 1.3.145


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0144147E write attempt to address 0x00000000

Engaging BOINC Windows Runtime Debugger...

For now, I'm going to try to go back to the opti 0.19 SSE2 CPU app. When this thing goes GPU by its lonesome(ATI), I'll try again then. Maybe I'll have more insight to my issue by then. Thanks all.

I got the app from Zslip.com - same app?

Yeah, the opti app comes from Zslip. I was referring to the 8.12 drivers, .NET Framework and DirectX 9.0c coming from guru3d.

Installed the Cat 8.12 hotfix for the HD3850 AGP card.

My understanding is that hotfix only works if you have the 8.12 drivers installed. The hotfix you install must be the same for the version of Catalyst you install. This might be the root of your problem if you can't get the 8.12 drivers to install properly. Again, it is my understanding that they should absolutely work for your card.

GPU-Z is a program like CPU-Z for your graphics card. Does it show all the statistics you expect your 3850 to be?

---

Well, if I can get a screen print from GPU-Z, everything is in order. Says I have my HD3850 AGP card and has Cat 8.12 drivers on it. I don't have the neat little tools I used to have at work (Snag it, Word, etc...), since I retired. It also says I have directX 10.1 SM 4.1, AGP interface at 8x, memory clock @ 669 MHz, 320 shaders, memory clock @ 829 MHz etc... Anything come to mind for the access issue? Thanks.

Well, if I can get a screen print from GPU-Z, everything is in order. Says I have my HD3850 AGP card and has Cat 8.12 drivers on it. I don't have the neat little tools I used to have at work (Snag it, Word, etc...), since I retired. It also says I have directX 10.1 SM 4.1, AGP interface at 8x, memory clock @ 669 MHz, 320 shaders, memory clock @ 829 MHz etc... Anything come to mind for the access issue? Thanks.

I'm more of a hardware than a software guy, but since GPU-Z is showing directX 10.1.......you might want to concentrate on getting it back to 9.0 and see if that does the trick.

---

GPU-Z will show the DirectX support the card has, which is DirectX 10.1, even if you have older versions of Dx installed. For me it also shows 10.1, while I only have 9.0c installed.

---

Jord.

The BOINC FAQ Service.

Well I've tried a register cleaner & reverting to DirectX 9.0c, but I keep getting the write access error. Does anything in this debug coding give me a hint of what I'm doing wrong? Thanks.

I'm not very experienced in interpreting such output, but for me it looks like amdcaldd.dll does not find a necessary module (another dll file it depends on).
This is most likely the .NET framework. It appears it is not correctly installed on your computer.
If you have already installed all .NET updates one finds on Windows update, I would try to remove the .NET framework completely and to install it again.

I'm not very experienced in interpreting such output, but for me it looks like amdcaldd.dll does not find a necessary module (another dll file it depends on).

From reading on the net, I kinda gathered it was a ddl that was called by amdcaldd (values passed to child by amdcaldd - RetAddr Args to Child
and returns a GetLastError = '126' (not found). This made me wonder about the 8.12 hotfix for AGP cards, but so far, everything else works with the card (even tried a game to see if it would die, but didn't). Since I had no idea what was missing, I screamed for help again.

This is most likely the .NET framework. It appears it is not correctly installed on your computer.
If you have already installed all .NET updates one finds on Windows update, I would try to remove the .NET framework completely and to install it again.

I have .NET 3.5 installed (after .NET 2.0 insatlled with the driver). I'll give the removal of all .NET versions and reinstall .NET 3.5. At least this won't take 6 forevers! I'll post results when it's been accomplished.

Thanks again CP!

@ CP

Uninstalled .NET & updated with the .NET 3.5 SP1. It installed successfully.

I shut down BOINC and started task manager to insure all BOINC processes were not running & then put the 3 ATI files in the Milkyway file. Started BOINC and resumed 1 task.

I got the same write access error with the same addresses & return codes.

I guess I'll keep looking. Thanks for the help.

Don't those 3 ATI files go in the Windows\system32 folder, and not in the MilkyWay folder?

---

Calm Chaos Forum...Join Calm Chaos Now

Don't those 3 ATI files go in the Windows\system32 folder, and not in the MilkyWay folder?

I believe the 3 files you're referencing are the renamed files for Cat 9.2 & above.

The 3 files I put in the Milkyway folder were the ATI_SSE2 opti app, the app_info_xml, & the brook.ddl to have my APG card crunch Milkyway. Thanks.

Don't those 3 ATI files go in the Windows\system32 folder, and not in the MilkyWay folder?

I believe the 3 files you're referencing are the renamed files for Cat 9.2 & above.

The 3 files I put in the Milkyway folder were the ATI_SSE2 opti app, the app_info_xml, & the brook.ddl to have my APG card crunch Milkyway. Thanks.

Oops, sorry, I misunderstood which files you were talking about.

---

Calm Chaos Forum...Join Calm Chaos Now

@ Donnie
Boy you seem to be in deep.
Ok first of all, I have heard and read that the Cracked Direct X 10 or 11 for XP COULD be infected. Follow this link below. Good information about it.
http://www.megaleecher.net/Download_DirectX_11

Also IF you are infected with Direct X 10 go to google and type "doctor web" and download the "cure it" software onto a usb or cd. NOT on your computer has the executable will be infected right away.

I also feel that your registry is now clogged up with ATI and BOINC entry.
Why dont you
1. Uninstall BOINC (then delete the folder in C:\Program Files\BOINC)
2. Unisntall any and all ATI you may have (even the control panel from ATI)
3. Go in C:\Program Files\ again and delete any folder left from ATI
4. Download a freeware to cleanup registry like ccleaner from http://www.ccleaner.com/ (Myself I use regcure whit a licensed copy) and CLEAN
5.Reboot
6.Do an online scan (Kaspersky recommended)
If by then there is no virus found or you havent formatted yet keep reading.
7.Click on start then "run" then type dxdiag (this will defenately tell you what you have for a directX)
8.DX10 is part of the OS and can't be removed. But 10 is not a full version of DX. You still need the 9.0 runtimes for games and applications.
Run the 9.0c installer and it will install all the needed runtimes and files so that you can play games that are for 10 or for 9.0.
9.Make sure you have the ati_0.19e_win32_SSE2 and the hotfix.
10.Reinstall 8.12 then reboot
11. Reinstall BOINC. 6.5.0 is recommended as it is stable (my opinion)
12. Attach to MW (good luck on getting any WU)
13. If you can just run 0.1 days worth of WU to start.
when you get the appropriate files Shut down BOINC and unzip the ati_0.19e_win32_SSE2 in the C:\Documents and Settings\All Users\Application Data\BOINC\projects\milkyway.cs.rpi.edu_milkyway_gpu folder.
Your done.
I am not sure what the hotfix is and whether you have to run it prior or after.
Reformat if you feel it could fix the directX10 problem.
If all fails I am sorry I tried my best. I am not computer tech by any means.

Martin Chartrand

@ Martin

The only thing I didn't do in your suggestions was to run my register cleaners (I have 3 and they always give different results) after I uninstalled & deleted anything that had the ATI name on it & after I uninstalled BOINC.

When I run DXDIAG, the dialog box informs me I'm at DirectX 10.0 (running XP SP3). I installed BOINC 6.6.20 because I have 2 machines (both dual core AMDs) running nVidia cards (2 GTX 260/216's & 2 GTX 280's) with BOINC 6.6.20 & my quad (twin AMD FX-74s) with 3 ATI HD4850s with BOINC 6.6.20 and haven't had any issues with scheduling, LTD, or STD, with the exception of running Seti@Home GPU when GPU Grid was down for 3 days. I believe that was because I was running a CPU project with Seti GPU & Seti went into a negative long term debt & short term debt situation. I got around that by suspending the CPU project until GPU Grid came back online and Seti went about its merry way without slowing down again.

BTW, this mobo is a Giabyte GA-K8U AMD 754 socket with an Athlon64 3400+ chip (single core) in it. Nothing is overclocked. All drivers have been updated to current drivers using Driver Agent. This is the only mobo I have that is 100% current. Also running XP SP3 as mentioned above.

Concerning the DirectX 10.0 download, I had McAfee anti virus running & Windows firewall running and never received any warnings about any virus. Graphics & 3D rendering look fantastic when I load the game that came with the card (The Witcher by Atari). I'm not a gammer, but I wanted to test the card with the DirectX 10.0 software (and the Cat 9.4 AGP hotfix) and it didn't disappoint me.

I've even loaded the Cat 9.4 AGP hotfix (mentioned above) on the machine and added the 3 amdcalcl, dd, & rt DDLs to the system 32 folder. CP (Cluster Physik) informed me this wouldn't run on XP, but I haven't had a problem with it yet.

I've had the output file absent (the write access issue) with the ATI_SSE2 opti app since DirectX 9.0c & the ATI Cat 8.12 AGP hotfix and I was just updating drivers to somehow get the message to disappear. No joy as of yet.

The 8.12 AGP hotfix (and 9.4) CCC have a SmartGart tool that will set the AGP bus for optimum performance & stability. But in both versions, it showed AGP off and at 0x speed and would not allow me to set it to 4x or 8x. PC Wizard confirmed that AGP on the AGP bus was disabled (it also has a AGP3 mode disabled). I'm beginning to believe this might be the root of my issue, but I can't confirm that. PC Wizard also shows me that the Northbridge chip on this mobo has a uli 3.0 AGP controller and that the AGP card is attached to PCI bus #0. The same NB chip also has the HT controller on it. I don't know why this is so, but the APG card is stuck in the AGP slot and, as I mentioned earlier, the game grapics, rendering, and movement are great. GPU-Z shows the buss interface as AGP 8x @ PCI.

If I can't figure out what called module is missing, I just might reformt the hard drive and reinstall Windows (Activation key willing) Saturday & Sunday. I've never had an easy install yet. This will really be my last option as I'm not looking forward to spending a week to put everything back on the machine.

Thanks for your suggestions & help. Maybe I'll get there someday.

I've even loaded the Cat 9.4 AGP hotfix (mentioned above) on the machine and added the 3 amdcalcl, dd, & rt DDLs to the system 32 folder. CP (Cluster Physik) informed me this wouldn't run on XP, but I haven't had a problem with it yet.

Normal apps and games will run. The bug will only affect the CAL interface, i.e. GPGPU applications.

The 8.12 AGP hotfix (and 9.4) CCC have a SmartGart tool that will set the AGP bus for optimum performance & stability. But in both versions, it showed AGP off and at 0x speed and would not allow me to set it to 4x or 8x. PC Wizard confirmed that AGP on the AGP bus was disabled (it also has a AGP3 mode disabled). I'm beginning to believe this might be the root of my issue, but I can't confirm that. PC Wizard also shows me that the Northbridge chip on this mobo has a uli 3.0 AGP controller and that the AGP card is attached to PCI bus #0. The same NB chip also has the HT controller on it. I don't know why this is so, but the APG card is stuck in the AGP slot and, as I mentioned earlier, the game grapics, rendering, and movement are great. GPU-Z shows the buss interface as AGP 8x @ PCI.

If I remember it right, the AGP controller driver has to be installed before the graphics driver. Maybe that is the culprit. One looses quite a bit of performance if the AGP port runs in the PCI compatibility mode and the graphics driver may even not work correctly. So could you check that you have the appropriate northbridge driver (containing the AGP controller) installed?