Einstein@Home keeps crashing instantly....
20 Jan 2019 2:12:17 UTC
Topic 217972
(moderation:
Hi,
I haven't used boinc in awhile and I wanted to let it run on my new system. Here are the specs:
i7-8700k | MSI Z370 Gaming Carbon Pro | MSI RTX 2080 DUKE OC 8GB | 2x8GB Corsair LPX DDR4 3000 | Samsung EVO960 250GB M.2 | Cooling beQuiet Dark Rock Pro3 | PSU Corsair RM650X
Unfortunately, Einstein@Home Gamma-Ray Pulsar Binary search (nvidia gpu type) keeps crashing constantly. It starts a new task, runs for a few seconds, then my screen goes black and it starts a new one. The other one it shows with a computation error.
I never had problems in the past. But I never tried with the RTX 2080 before.
I already tried different clock rates on the video card. first I though it was because of my overclock, but it also crashes on stock clocks right away.
Any ideas what the issue could be?
mjbn77 wrote:I never tried
)
That is the problem. The Turing cards (RTX 2080, 2080 Ti, and 2070, so far) do not work properly when run on Einstein Gamma-Ray Pulsar using the current Einstein application for any of the Windows drivers released for Turing to date. The failure syndrome displayed by your card is just like that shown by a dozen other cards here.
I imagine it is some combination of bugs or limitations in the Einstein application, the Nvidia driver, and the Turing hardware. I think there is nothing you can do to avoid it.
Two of the three series of GRP files issued since October suffer this problem with Turing, and one did not. I can't predict which types of files Einstein will issue in the future. We currently hope either that Nvidia will implement a driver fix, or that Einstein will issue a revised application which somehow avoids the problem.
Thank you for your report--I now have sixteen user systems on my list of Einstein Turing hosts which have displayed this problem. If you are interested in reading more about our experience here, you can read this thread on which most of the last few hundred posts arise from this problem.
Thank you for the quick
)
Thank you for the quick response. At least now I know that its nothing wrong with my hardware.