Marlin 0.9.0 major problem!

[Synthica]

Hi,

i have set Marlin 0.9.0 to 2 computers, with log including:

"
:: Batch file sample for Marlin
:: Written by Xurious for SiaMining.com
:: Sia Address: 00091d9619f1e697ddf80e751b68baffc444e7b59eeb54e131f136711d84aebf3bc6e0b820af
:: Updated 2016-08-04
::
:: Your Payout Address.
SET address=Mywalletaddress
:: Worker Name.
SET worker=Myownnickname
:: Intensity. 21 is great for normal desktop usage. 28 is typical for mining.
SET intensity=21
::
marlin.exe -H eu.siamining.com:3333 -u %address%.%worker%" -I %intensity%
"

But after like 5-20minutes, Marlin shuts itself down, just - gone -
This same thing happens on both computers.

1st comp spec: GTX1080 / i5-7400
2st comp spec: GT630M / i7-xxxx

Anyone could help me out?

[Synthica]

Using Win10 64bit on both comps, and not doing anything on computers while mining if it helps.

[pevecg]

Create a bat file in the folder you have the miner.
Edit it so it says: "cmd.exe /k marlin -h eu.siamining.com:3333 -u yourwallet.yourworker -I 21"
This will make your console stay after something fails with marlin miner and you can see what went wrong. If the marlin miner logs it ofcourse.

[cneeper]

This is a few days old, but if you (or anyone else) are still having the problem:

I've noticed this same behavior with Marlin shutting itself down, "just - gone -" as you say. I'm new to mining and new to overclocking GPUs, but in my learning how to overclock, I've discovered that when I really go hog wild and screw up the overclock settings, my computer will crash and reboot. However, now that I'm learning how to methodically push my GPU in baby steps over a long period of time, I'm not crashing so dramatically. Instead, I'm seeing Marlin do this behavior when I've pushed a little to hard on the clock at a particular voltage. This is my key to back off a step on the clock and let it run at the slower clock for a few hours to make sure it's stable at that clock/voltage before stepping up to a higher voltage/clock combination.

What I've noticed is that Marlin will "disappear" faster if I've gone a couple of steps too far. So if Marlin disappears inside of a minute or two, I know to back off a little more aggressively and then run it for a few hours at that clock rate to make sure it's stable. If Marlin take 15 or 20 minutes to crash, as in your case, I can step back just a little bit and see if I'm stable.

So, if you're overclocking your GPU, you might back off a bit and see if you stabilize. If you're NOT overclocking, maybe you need to install the tools anyway and underclock a bit to see if you stabilize. Also perhaps check your temperatures. (ie. maybe your GPU is overheating or getting a little unstable in its age, if it's an older card).

Hope my observations help you or someone else.

[bryan]

@Synthica may need to keep lowering the intensity. Or even set the affinity.

[xurious]

Marlin 1.0.0 has been out for a long time.

See the newest version here: https://siamine.com/marlin