Until recently (like the last week or so) I have had no issues and it hums along at night doing its thing. In the last week it seems every task that is running on the GPU is coming up the "COMPUTATIONAL ERROR". Any ideas on how to fix it?

1) Back-off any overclocking if any applied
2) Remove any command line parameters that you may be using and let a task run with default settings
3) Remove driver for GPU and re-install one downloaded from the NVidia website
4) Re-seat GPU.
5) Try a different PCIe power cable from PSU
6) Try card in a different PC if possible, if it works in another PC then check PSU of the PC that had the problem

Run GPU-z and use the OpenGL and OpenCl demos to verify that card is working correctly.... and still I fear, and still I dare not laugh at the Mad Man!
Queen - The Prophet's Song

Until recently (like the last week or so) I have had no issues and it hums along at night doing its thing. In the last week it seems every task that is running on the GPU is coming up the "COMPUTATIONAL ERROR". Any ideas on how to fix it?

I agree with every troubleshooting step that has been offered. That "NVIDIA Quadro M6000 (4095MB)" appears to be a very muscular card. It should produce excellent results in its stock setup.

Also, if you are not running TThortle to make sure you system is not running to hot, I would download that free app and install it.

Please get back with us if the troubleshooting steps don't appear to be working.

If you remove all command line parameters from your mb*sog.txt card and the problems go away, please post those parameters here so we can offer some ideas on how to "fix" them.

HTH,
Tom"You are entitled to your own opinion but not to your own facts." Senator and Professor Patrick Moynihan
---
https://GalensonConsulting.WordPress.com

If this has happened suddenly then the cause is a step change. The most probable is MS has "kinldly" updated the GPU driver, so I would first make sure I was using the correct driver from nVidia, not from MS. Do a "clean" installation (hidden under the "advanced installation" button) which removes the old driver. Even if a reboot is not forced after the installation do a reboot just to make sure.
As you are running "stock" applications there is no need to worry about "removing command lines", as they are not used on your system.Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

1) Back-off any overclocking if any applied
2) Remove any command line parameters that you may be using and let a task run with default settings
3) Remove driver for GPU and re-install one downloaded from the NVidia website
4) Re-seat GPU.
5) Try a different PCIe power cable from PSU
6) Try card in a different PC if possible, if it works in another PC then check PSU of the PC that had the problem

Run GPU-z and use the OpenGL and OpenCl demos to verify that card is working correctly.

Oops, I got my utilities mixed up, it is GPU_Caps_Viewer available from Geeks3d that has the OpenGl and OpenCl demo tests.... and still I fear, and still I dare not laugh at the Mad Man!
Queen - The Prophet's Song

It appears that this was caused by Windows doing a driver update triggered by my lovely IT department. I also started getting problems while rendering in SolidWorks due to them issuing the MS driver for my Quadro card instead of one from nVidia.

Check for overheating : All parameters are logged on this machine and the GPU temp never got above 85ºC

Check PSU / PSU Cables : Computer has redundant 1250watt PSU's which both have smart reporting on them. Neither one fails the onboard tests when they are polled. Cables are non interchangeable sadly.

Remove Command Line Parameters : I only run the application in its base configuration and have never used the command line parameters.

Re-Seat GPU : Did not do this as this computer is less than 4 months old housed in an A/C's office in southern California. Corrosion should not be an issue (will do this if I get more errors though as a precautionary measure)

Try card in another PC : I will do this if I get more issues with it as there are 4 clones of this machine in the office.

Hi all, I am having a similar problem as the OP. However I have computation errors for both CPU and GPU tasks. Tasks run for 5 seconds and then fail with the error.
Host id is: 8332726. The problem started yesterday after a reboot. I have done the following in an attempt to resolve the issue but the results are the same after each attempt:
1. Confirmed no Windows patch installed prior to re-boot per above
2. Clean install of Nvidia drivers from Nvidia
3. CCleaner run on Registry
4. Project reset in Boinc Manager
5. Complete uninstall and re-install of Boinc Manager
6. Memory scan - returned a clean result
Suggestions/advice will be appreciated, this machine is was a workhorse.

Crashes with error 0xc0000005 can be heat related, driver related, bad memory, a badly written application or interference from malware/adware/a virus.
Both your CPU and GPU tasks show that the crash happens in the CPU app setiathome_8.00_windows_intelx8!+0x0 , so I would start with checking whether the motherboard chipset drivers are still intact and correct. Next I'd check the system with a good malware scanner (Malwarebytes & HitmanPro), good up-to-date anti virus (full system scan, including rootkit scan).

Memory scans normally don't put the same strain on the memory as intensive usage does, because memory checkers just check the memory but don't heat up the surrounding system. Testing whether it's the applications here that don't do well can be done by adding another project and run that on CPU and GPU (e.g. Einstein@Home), if that doesn't throw all the errors, it's Seti's apps.Jord

Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.

Jord, Thank you for the advice. Malwarebytes did in fact find a couple of issues. HitmanPro did not find anything additional.
After taking the steps you suggested, the machine is back up and running SETI (and a couple of Einsteins).
Thanks again.