Quote from: doktor83 on October 11, 2018, 05:24:07 PM

Quote from: hlbcal on October 11, 2018, 04:45:02 PM

Quote from: doktor83 on October 11, 2018, 01:06:28 PM

FIXED 1.6.8 IS UP AGAIN ON MEGA

Hopefully this is the last fix of 1.6.8, and it should compile now on pitcairns, hawaiis etc..

I also rewrote the resources freeing code on miner shutdown/restart, so it may take now a little longer to close the miner, but this should solve the problems with driver sometimes crashing on miner close.

If you want to use the old, faster shutdown method, you can use the --forcedshutdown parameter , added in start.bat

Also i changed my mind and no more normal and maxi versions, only maxi. Because no one notices the big message on the first page that says which drivers should be used

Please report if hawaiis and pitcairns compile now.
Thanks

Hi dok,

I still have the same issue. GPU hash rate drop to zero and miner crashed. V1.6.7 is stable, it does not have such issue.

[2018-10-12 00:08:48] watchdog: GPU1 [BUS: 1] hashing speed is 0 H/S
[2018-10-12 00:08:48] watchdog: GPU2 [BUS: 4] hashing speed is 0 H/S
[2018-10-12 00:08:48] watchdog: GPU3 [BUS: 2] hashing speed is 0 H/S
[2018-10-12 00:08:48] watchdog: GPU4 [BUS: 7] hashing speed is 0 H/S
[2018-10-12 00:08:48] watchdog: GPU5 [BUS: 8] hashing speed is 0 H/S
[2018-10-12 00:08:48] watchdog: GPU6 [BUS: 3] hashing speed is 0 H/S
[2018-10-12 00:09:52] watchdog: GPU crash detected, miner will try to restart
[2018-10-12 00:09:52] Restarting miner process

[2018-10-12 00:09:53] Miner version: 1.6.8
[2018-10-12 00:09:53] Windows version: 10.0 build 16299
[2018-10-12 00:09:53] Video driver version: 24.20.11021.1000
[2018-10-12 00:11:36] AMD Platform ID: 1
[

You should lower intensity until your driver won't crash, so hashrate won't fall to 0 and miner won't restart.
It can happen that after driver crash opencl can't be initialised.
Try set that startup script and set overdriventtol to reset gpu's every time before run, maybe that will help.

Hi dok,

I tried to lower intensity, same problem. V1.6.7 works well on the same hardware and GPU driver. I'm pretty sure it is due to something different in V1.6.8