Welcome to MilkyWay@home

Incorrect function. (0x1) - exit code 1 (0x1)

Message boards : Number crunching : Incorrect function. (0x1) - exit code 1 (0x1)
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile planetclown

Send message
Joined: 16 Feb 12
Posts: 3
Credit: 22,713,177
RAC: 0
Message 62084 - Posted: 26 Jul 2014, 16:28:14 UTC

I'm seeing errors on my Radeon 7950 boost at stock clock 925MHz on Catalyst 14.4 drivers and Windows 7 64-bit. The errors resulted in a Windows blue screen. I tried underclocking the card back to non-boost clocks (800 MHz) and still get errors and a Windows blue screen. I do have an app_config.xml in place that I've used for some time without issues.

At stock boost clocks, both tasks were Modified Fit v1.3.

Task 1

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
Incorrect function.
 (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.30 Windows x86_64 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' 
Switching to Parameter File
Using AVX path
Found 1 platform
Platform 0 information:
  Name:       AMD Accelerated Parallel Processing
  Version:    OpenCL 1.2 AMD-APP (1445.5)
  Vendor:     Advanced Micro Devices, Inc.
  Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices cl_amd_hsa 
  Profile:    FULL_PROFILE
Using device 0 on platform 0
Found 1 CL device
Device 'Tahiti' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU)
Board: AMD Radeon HD 7900 Series
Driver version:      1445.5 (VM)
Version:             OpenCL 1.2 AMD-APP (1445.5)
Compute capability:  0.0
Max compute units:   28
Clock frequency:     925 Mhz
Global mem size:     3221225472
Local mem size:      32768
Max const buf size:  65536
Double extension:    cl_khr_fp64
<search_application> milkyway_separation 1.30 Windows x86_64 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Parameter file 'astronomy_parameters.txt' is empty
Switching to Parameter File
Error reading number_parameters
21:51:20 (5616): called boinc_finish

</stderr_txt>
]]>


Task 2
<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
Incorrect function.
 (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.30 Windows x86_64 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Parameter file 'astronomy_parameters.txt' is empty
Switching to Parameter File
Error reading number_parameters
21:51:18 (5612): called boinc_finish

</stderr_txt>
]]>


At non-boost clocks (800 MHz) both tasks reported the following.

Task 1 - Mod Fit v1.3
Task 2 - MW@H v1.02
<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
Incorrect function.
 (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>

</stderr_txt>
]]>


Here's my basic app_config.xml
<app_config>
   <app>
     <name>milkyway</name>
     <gpu_versions>
         <gpu_usage>0.5</gpu_usage>
         <cpu_usage>0.5</cpu_usage>
     </gpu_versions>
   </app>
   <app>
     <name>milkyway_separation__modified_fit</name>
     <gpu_versions>
         <gpu_usage>0.5</gpu_usage>
         <cpu_usage>0.5</cpu_usage>
     </gpu_versions>
   </app>
</app_config>


Any ideas?
ID: 62084 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
swiftmallard
Avatar

Send message
Joined: 18 Jul 09
Posts: 300
Credit: 303,562,776
RAC: 0
Message 62085 - Posted: 26 Jul 2014, 18:33:52 UTC

My first inclination would be to detach and reattach. While you are detached, adjust your memory speed down, 300 MHz is plenty, just to make certain there are no heat issues. Also, just crunch one unit at a time. See what happens then.
ID: 62085 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile planetclown

Send message
Joined: 16 Feb 12
Posts: 3
Credit: 22,713,177
RAC: 0
Message 62086 - Posted: 26 Jul 2014, 23:32:57 UTC - in response to Message 62085.  

Thanks for the suggestions, swiftmallard. I'll give them a try and see what happens.
ID: 62086 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile planetclown

Send message
Joined: 16 Feb 12
Posts: 3
Credit: 22,713,177
RAC: 0
Message 62088 - Posted: 27 Jul 2014, 18:45:59 UTC

I detach and reattach and underclocked memory from 1250 to 950 MHz. Was still crunching two at a time and errored out the same as when I was running core clock at 800 MHz.

Task 1
Task 2

Here's the blue screen info for prosperity's sake...
On Sun 7/27/2014 2:06:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072714-32136-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE) 
Bugcheck code: 0xA0000001 (0x5, 0x1, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). 
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR


I may try to re-install the AMD drivers and/or omit the Catalyst Control Center software.
ID: 62088 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
zablociak

Send message
Joined: 2 Sep 11
Posts: 6
Credit: 571,286,756
RAC: 0
Message 62089 - Posted: 27 Jul 2014, 19:18:10 UTC

I assume that your 7950 is not faulty and not overheating.

Then goes:

This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)


I've experienced tons of BSODs caused by atikmdag.sys while crunching MW (and other projects, but not E@H BRPs).

Combination of method described here: http://forums.guru3d.com/showthread.php?t=363233 and disabling Aero in Win7 worked for me.

Reinstalling drivers, using Driver Sweeper, adjusting clocks most probably will not help you.

Regards
Luke
ID: 62089 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Incorrect function. (0x1) - exit code 1 (0x1)

©2024 Astroinformatics Group