Quote from: merc84 on April 22, 2016, 08:53:42 AM

Quote from: Zitdadast on April 22, 2016, 08:03:21 AM

Quote from: thesaltonsea on April 22, 2016, 06:25:11 AM

Quote from: Claymore on April 21, 2016, 05:14:34 PM

Quote from: Realetim on April 21, 2016, 05:04:44 PM

Quote from: Claymore on April 21, 2016, 01:58:41 PM

Quote from: murders10 on April 21, 2016, 01:52:51 PM

Quote from: thesaltonsea on April 21, 2016, 12:57:05 PM

Quote from: Haryford on April 21, 2016, 11:21:21 AM

Quote from: restless on April 21, 2016, 11:14:44 AM

I tried to use -wd 1, but can't make it to close the miner
tried -r -1
tried -r 0
When I mistype pool name (simulating dns /connectivity problem) it just keeps retrying to connect every 20sec, won't close the miner Sad

My miner does not close. It will hang the system. So I use -wd 0 to disable the watchdog, and -r -1 not to restart.

.
+1 , after ver. 3.0 i found my rig 2 times freezed after a crash, i will test with -wd 0 and -r -1 now

+1 same here windows totally freezes and crash sometime i have no unplug it to restart Embarrassed

When GPU fails, often Windows cannot work properly anymore and often it cannot even reboot normally.

In your old miner, 1.0 to 2.0, when the one GPU hang, the mining can still continue in other GPUs.

Disable watchdog: "-wd 0" if you want to continue mining if some GPU failed.

With 3.2 and -wd 0 and -r -1 , i found again my rig rebooted and freezed on boot screen , there was no such problems with the old versions of the miner .

I have the same problem. Maybe you can underclock a bit? The newer version is faster, so stress the GPU more.

Try reduce intensity, also may help to put a timeout in batfile to allow windows sufficient time to load.

What intensity would you recommend for the -ethi? What is teh range of the intnensity? 0-16 or higher?