Quote from: wetblanket on May 10, 2018, 02:50:41 AM

Quote from: wetblanket on May 07, 2018, 07:27:43 PM

Quote from: dstm on April 05, 2018, 02:27:27 PM

Quote from: symbiosoft on March 30, 2018, 03:59:12 PM

Quote from: dstm on March 28, 2018, 06:31:17 AM

Quote from: symbiosoft on March 27, 2018, 03:41:37 PM

I had a crash this morning on Linux with DSTM Miner v0.6:

*** stack smashing detected ***: ./zmminer terminated

Huh

Could you pls provide your startup configuration?

Again this morning, same error message.

I don't use a config file, I call zmminer in a bash script:

./zmminer --server $server --port $port \
--telemetry \
--user $worker --pass x \
--time >> "$log" 2>&1

Thanks

Do your log files contain a 'unresponsive gpu' message before the crash?

I didn't see any follow-up on this from `symbiosoft`, but have run into this twice over the last week or so myself. Here are the last few lines of output:

Code:

2018-05-07 04:41:33 AM| ========== Sol/s: 2768.4 Sol/W: 4.02 Avg: 2767.2 I/s: 1482.3 Sh: 31.30 1.00 113
2018-05-07 04:41:46 AM| GPU0 55C Sol/s: 460.4 Sol/W: 4.07 Avg: 466.8 I/s: 249.2 Sh: 4.49 1.00 114 +
2018-05-07 04:41:47 AM| GPU2 59C Sol/s: 466.7 Sol/W: 3.97 Avg: 455.7 I/s: 244.6 Sh: 5.16 1.00 116 +
2018-05-07 04:41:47 AM| GPU1 55C Sol/s: 467.2 Sol/W: 4.06 Avg: 465.3 I/s: 249.5 Sh: 5.81 1.00 115
*** stack smashing detected ***: zm_0.6/zm terminated
Aborted (core dumped)

I'm running with this on the command line (Ubuntu Linux 16.04):

Code:

zm_0.6/zm --time --server us-east.equihash-hub.miningpoolhub.com --port 17023 --user login.rig --pass pass

Here's my latest one (this is new, the previously quoted crash was all I'd seen before now):

Code:

2018-05-09 05:26:50 PM| ========== Sol/s: 2768.1 Sol/W: 4.02 Avg: 2763.7 I/s: 1479.6 Sh: 2.35 0.99 270
2018-05-09 05:26:50 PM| GPU2 60C Sol/s: 456.8 Sol/W: 3.97 Avg: 455.5 I/s: 243.8 Sh: 0.39 1.00 610
2018-05-09 05:26:54 PM| GPU3 61C Sol/s: 454.8 Sol/W: 3.98 Avg: 456.6 I/s: 244.6 Sh: 0.38 0.99 204
2018-05-09 05:26:57 PM| GPU1 56C Sol/s: 470.0 Sol/W: 4.06 Avg: 466.0 I/s: 249.6 Sh: 0.39 0.99 201
2018-05-09 05:26:59 PM|# server set difficulty to: 00011f7d098fe205b0000000...
2018-05-09 05:27:02 PM|> GPU4 64C Sol/s: 454.4 Sol/W: 4.01 Avg: 459.6 I/s: 246.2 Sh: 0.40 0.99 205
2018-05-09 05:27:04 PM|> GPU0 58C Sol/s: 467.9 Sol/W: 4.05 Avg: 464.4 I/s: 248.3 Sh: 0.41 1.00 202
2018-05-09 05:27:08 PM|gpu_id 1 61 3 unspecified launch failure
2018-05-09 05:27:08 PM|gpu 1 unresponsive - check overclocking
2018-05-09 05:27:08 PM|cudaMemcpy 1 failed
Segmentation fault (core dumped)

I assume most others would confirm this is overclock related (duh, the error message?!) - maybe due to the warmer spring weather pushing ambient temperatures up? But, my temps are all consistently below 70C, so this would still surprise me as NOTHING else has changed on this machine since it was rock solid before, other than time has passed and temps have risen.

Only other option is a loose/malfunctioning riser, I suppose.

I think you set too low power