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?

Fire up Catalyst Control Centre from the Task Bar, then go to Information, then Software, it should then give you a Catalyst version.

If you want to revert to an earlier driver, Uninstall the Catalyst driver, reboot, then Use the AMD Catalyst Uninstall utility (only for Windows 7 at the moment), reboot, then install the older driver,
(The Catalyst driver Installer/uninstaller doesn't remove all the files from System32 and SysWOW64 directories, and earlier driver Installers won't overwrite later APP runtimes)

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?

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?

Fire up Catalyst Control Centre from the Task Bar, then go to Information, then Software, it should then give you a Catalyst version.

If you want to revert to an earlier driver, Uninstall the Catalyst driver, reboot, then Use the AMD Catalyst Uninstall utility (only for Windows 7 at the moment), reboot, then install the older driver,
(The Catalyst driver Installer/uninstaller doesn't remove all the files from System32 and SysWOW64 directories, and earlier driver Installers won't overwrite later APP runtimes)

Claggy

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?

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?

To follow my last post, and to respond to this, specifically, Driver 9.0.100.2000. It seems the numbers referred to in the post I responded to an hour ago refer to the version of Catalyst/CCC? And I'm assuming that the CCC version and the driver I get might be tied together ... ?

I did a "roll back driver" while in control panel/system/hardware/... .
It is now at 8.821.0.000.
No more blue screens, but BAM does not indicate GPU computing is enabled.
Under Tools/Computing Preferences, use of GPU was already checked (by default?).

I joined SETI at the end of the year so I was just getting started when my graphics card began having problems and yesterday I upgraded to an Win 8 I7 with a Nividia GT 640 and late yesterday over 100 items were downloaded to my Computer. I had never seen more than 14 with my old computer. Several of the work units processed much quicker than I could track them. But today there are still about 100 that have been sitting in a Status of Downloading all day and all are SETI@homeEnchanced6.10 (cuda_fermi). I saw at least 2 astropulse process but these 100 are just sitting there. I cannot make the execute.

I have now changed my setting to only download Astropulse 6 I believe.
I hate to just abort them.

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?

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)

I suspect you were responding to Vito, but ... .

I only had 1 WU for opencl, and it errored out. Another has downloaded. I have not checked its status yet.

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

The problem is you don't follow the links.

How else you can explain your "Searched high and low for an older version of CCC. Found one."
after the 2 posts by Claggy with 3 proper links and explanations what to do?

Your response is NOT helpful.

I made it quite clear I was at work. That means this had low priority. Preparing for teaching a class or grading for it obviously MUST carry higher priority.

I followed TWO links provided by Claggy.
One was to AMDs spot for download of DRIVERS.
Hence, the blue screen of death I mentioned.
I disabled the GPU so that would stop and so other WUs could be crunched in the meantime, and until I could get another chance to try to sort things out.
Rather than using a Fix/Uninstall feature Claggy mentioned, I used "Roll back driver" when I followed CONTROL/SYSTEM/HARDWARE (as mentioned by another poster, and as I stated before).
The second link I followed was to the "HAL6000" cheat sheet. From that, I figured that I needed a CCC version that matched the driver version. I uninstalled the CCC I had, and downloaded and installed the earlier version that matched the driver.
Upon doing that, and re-enabling the GPU, then re-booting BAM, BAM indicated GPU computing was enabled and downloaded 1 WU for it to work on, among other non-GPU associated WUs.

I've been with S@H since '99, and BOINCing since '05. I've followed along with a number of tweaks, and usually get it right on the first attempt. If not, the second or third. Sometimes, the issue isn't even anything any BOINCer has ever encountered, yet I get it straightened out. But, I ask.

So, thank you so much for your cordial and informative (and WRONG) post (I followed TWO ... count 'em, TWO) of the links.
Pardon me if I am not going to stay around at the office for a few more hours to get it straightened out on day one, and pardon me for having a job that takes priority over tweaking BOINC to do more.

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: