Message boards :
Number crunching :
Getting GPU errors
Message board moderation
Author | Message |
---|---|
Greg W Jones Send message Joined: 28 Nov 02 Posts: 29 Credit: 25,473,210 RAC: 0 |
The computer that I use every day has been reporting "error" results recently. The error message starts with "Incorrect function. (0x1) - exit code 1 (0x1)". A link to the full message is here: http://setiathome.berkeley.edu/result.php?resultid=2100677230 About 2 months ago I started to pay attention to the GPU processing and have upgraded to a GTX 570. The system is about 3 years old. The Kill-a-watt meter indicates that this system is pulling about 390W at full load. My system specs are as follows: Intel Q9450 OC to 3.0 GHz, 8G Ram, 750W PSU, EVGA Superclock GTX 570. Windows 7 64-bit Boinc Manager 6.12.34 Lunatics v0.38 apps Running 2 WU's at a time on the GPU Nvidia 280.26 driver I have noticed that the Seti app_info.xml file seems to have several duplicate entries for the various applications. I assume caused by the Lunatics install. I have stopped getting new work so I can burn down the WU cache. Then I plan on deleting the current app_info file and re-installing the v0.38 apps. This should create a fresh app_info file. I am burnning down the WU cache to not risk loosing them if the app_info file gets messed up. Those WUs have been hard to get lately :) Any help on why I am getting these GPU errors and what I can do to fix them would be appreciated. Thank you, Greg |
Cruncher-American Send message Joined: 25 Mar 02 Posts: 1513 Credit: 370,893,186 RAC: 340 |
That's a Fermi card. Are you running the Fermi app? I seem to recall that Fermi cards with the non-Fermi app gave a lot of errors, when the cards were first introduced.... That's why there's a separate Fermi app. |
Greg W Jones Send message Joined: 28 Nov 02 Posts: 29 Credit: 25,473,210 RAC: 0 |
Yes. (cuda_fermi) in the Application name within Boinc Manager. Thx, Greg |
Steve Robertson Send message Joined: 14 May 99 Posts: 38 Credit: 2,643,210 RAC: 0 |
I got that error when I overclocked my GPU too far. When the graphics driver puked and then recovered, the WU it was crunching at the time got that error. I backed the OC off a few Mhz and haven't seen it since. If you're not OCing your GPU, it could still be your graphics driver recovering from a failure. Have you tried updating your drivers? |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.