New AstroPulse applications for GPUs.

Updated AMD driver on one of my newer office computers so I could get it working on WUs the GPU could help with.
Upon reboot of system and BOINC, I got the blue screen of death.
A file by the name of, approximately, atiok3x2.dll was trying to write to rom, and it was stopped.
Before I complain to IT, any thoughts from the BOINC side?
(Yes, the provost knows I run the program. There will be no NEZ type stuff here.)

All AMD Catalyst starting from 12.10 are broken in term of usage with SETI OpenCL apps (at least with OpenCL MB app). And 13.2 beta 3 known to be unable to compile CL files for both apps at all.
So, better to stay with Cat 12.1 or 12.8.

OK, my action was prompted by a notice in BOINC manager, so I went directly to the AMD website and used their auto-detect to see what system I have and let it auto-decide what driver I needed.
So, between classes, or just after the last class of the afternoon, I will have to check what driver it gave me. I think I might find this fairly easily, but, just in case, can you or someone else indicate where to look for what driver it installed?

So, between classes, or just after the last class of the afternoon, I will have to check what driver it gave me. I think I might find this fairly easily, but, just in case, can you or someone else indicate where to look for what driver it installed?

Looks like they gave Catalyst Version 13.1.
I'll have to worry about this in an hour.
Next question is where to get the old driver (like 12.1, 12.8). Is that easy to locate on the AMD website?

Going back to CCC Version 12.1 did NOT change the DRIVER. The driver is still 9.0.100.2000.

A whole pile of your results have ended in errors.
If you visit the "number crunching" message board you will see a pinned topic which deals with this known problem.
(I suffered the same with my new cruncher, and the solutions offered work, but you may have to try them one at a time to see which works best for you)
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

If you have a problem it would be much better to try to solve it over in the number crunching forum.
____________
In an alternate universe, it was a ZX81 that asked for clothes, boots and motorcycle.

Beer/wine o'clock, the best of the o'clocks.

Humpty dumpty sat on a wall, along came a giant, and cooked him for breakfast.

If you have a problem it would be much better to try to solve it over in the number crunching forum.

Suggestions (link?) to a current thread dealing with such issues? Would rather put it in the "right place" than start a new thread.

Proper thread to discuss issues with new app is release thread of that app.
Here is release thread for stock app.
Release thread for r1761 is here: http://setiathome.berkeley.edu/forum_thread.php?id=70723

EDIT: regarding error you got - no idea. Need debugger for that on your host perhaps. Also, try to run app offline (i.e., via bench for example) will it crash ?
If yes, then we can try with latest build (or very verbose build) and pdb file for it. Just report in rev1761 thread.

EDIT2: cause you got that error with stock app better to answer right here:

single pulses: 0
repetitive pulses: 30
percent blanked: 9.53
class T_remove_radar: total=3.91e+009, N=1, <>=3.91e+009, min=3.91e+009, max=3.91e+009
class T_main_loop_L1: total=5.04e+013, N=111, <>=4.54e+011, min=4.51e+011, max=4.58e+011
class T_FFT_forward: total=2.64e+010, N=909312, <>=2.91e+004, min=7.58e+003, max=3.25e+007
class T_remove_radar_randomize: total=1.94e+012, N=1817736, <>=1.07e+006, min=2.88e+002, max=2.75e+007
class T_build_chirp_table: total=0.00e+000, N=0, <>=0.00e+000, min=1.84e+019, max=0.00e+000
class T_DataWrite: total=1.82e+009, N=88800, <>=2.05e+004, min=3.27e+003, max=4.65e+005
class T_DataWrite_ns: total=0, N=0, <>=0, min=0 max=0
class T_oclReadBuf: total=3.14e+007, N=909312, <>=3.40e+001, min=2.40e+001, max=3.38e+005
class T_ChirpWrite: total=0.00e+000, N=0, <>=0.00e+000, min=1.84e+019, max=0.00e+000
class T_ChirpWrite_ns: total=0, N=0, <>=0, min=0 max=0
class T_dechirp: total=2.45e+010, N=909312, <>=2.70e+004, min=1.01e+004, max=6.90e+006
class Dechirp_ns: total=0, N=0, <>=0, min=0 max=0
class Half_ns: total=0, N=0, <>=0, min=0 max=0
class T_PC_single_pulse_kernel_FFA_update: total=4.83e+013, N=909312, <>=5.31e+007, min=5.16e+007, max=1.28e+008
class PC_ns: total=0, N=0, <>=0, min=0 max=0
class T_oclReadBuf: total=3.14e+007, N=909312, <>=3.40e+001, min=2.40e+001, max=3.38e+005
class T_oclWriteBuf: total=1.86e+009, N=88800, <>=2.09e+004, min=3.38e+003, max=4.66e+005
class T_FFT_inverse: total=1.12e+010, N=909312, <>=1.23e+004, min=5.61e+003, max=6.87e+006
class T_ffa: total=2.08e+009, N=1, <>=2.08e+009, min=2.08e+009, max=2.08e+009
class T_GPU_buffer_read_backs: total=0, N=0, <>=0, min=0 max=0
OCL_ZERO_COPY USE_OPENCL OPENCL_WRITE USE_INCREASED_PRECISION SMALL_CHIRP_TABLE COMBINED_DECHIRP_KERNEL
rev 1316


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0040A1FA read attempt to address 0x00399E0C

Engaging BOINC Windows Runtime Debugger...