CUDA problems (Lunatics) / zero status but no finished file

Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1313604 - Posted: 10 Dec 2012, 18:04:07 UTC - in response to Message 1313597.  

Unfortunately I corrupted my BIOS due tue a very badly designed BIOS update procedure. Since I probably will not find a way to recover, I must wait a few days for a replacement motherboard. I'm thankful for all your ideas and will continue with your suggestions as soon as possible.



Ugh, sorry to hear that, and hopefully they're speedy with that. Sounds like there was some update then. I'll guess they're fiddling with the memory settings or PCIe etc, Fingers crossed they're still ironing out the kinks with the model.

Jason
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1313604 · Report as offensive
Profile Helsionium
Volunteer tester
Avatar

Send message
Joined: 24 Dec 06
Posts: 156
Credit: 86,214,817
RAC: 43
Austria
Message 1343195 - Posted: 5 Mar 2013, 6:57:17 UTC
Last modified: 5 Mar 2013, 6:57:27 UTC

Sorry for resurrecting this old thread, but I want to note that the problem has finally been solved.

My card, the "Zotac Geforce GTX 660 Ti AMP! Edition" is factory-OC'ed to 1150 MHz core and 1650 MHz memory clock - voltage already maxed.
The solution was to reduce the memory clock to 1500 MHz. It's running fine for days now (at core frequency 1200 MHz). Any higher value, particularly 1530 MHz and up, caused the driver to occasionally crash (with x41zc_cuda50; the previous x41g only caused the "zero status..." problem but no driver crashes) and whenever the driver crashed, the clock frequencies would be reset to factory and constant crashes (every 20 seconds or so) would happen from that point on.

I didn't notice this solution earlier because I never thought I had to decrease memory speed by that much. Anyway, it's fine now.
Thank you, jason_gee, for all your help.

Kind regards,
Helsionium

ID: 1343195 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file


 
©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.