Quote from: SpeedY_Hun on December 05, 2018, 09:01:03 AM

I tried the new beta version, and I still got the "CudaProgram.cu:407 : out of memory " with my 1060 3gb cards if I start ETC mining.

Quote

You have to use Windows 7 or Linux to mine ETC (and soon ETH) with 1060 3GB as Windows 10 "steals" part of the video RAM, making the allocation of enough memory for the DAG impossible even though the DAG is still way less than 3 GB.

Under Win7 is the same problem :/

We have a Win7 test rig with four GTX1060 3 GB and unfortunately it can't mine ETC since epoch 235. It still can mine ETH. Here are the things to look out for if you want to use it for as long as possible:
- Add -eres 0 to the command line or config.txt file to disable over-allocation of the DAG buffer
- Disable Win7 updates
- Open Control Panel, search for "Adjust the appearance and performance of Windows", then disable all the options in the "Visual effects" tab in the "Performance Options" window. This should lower the video memory usage a little

If everything else fails, your can always mine a low DAG coins like UBQ, DBIX, etc (virtually anything else than ETC and ETH will be mineable for quite a long time with 3GB GPU).

Quote from: xunl on December 06, 2018, 05:47:25 PM

Claymore 11.9 can control OC on nvidia 10 series cards as well as AMD RX 580 cards w/o installing any 3rd party tools. Just bare factory device driver minimum installation (no wattman/afterburn is needed). It's running very stable for long time. Can PhoenixMiner do that?

Not yet but we are working on it.

Quote from: hobocoe on December 08, 2018, 09:19:20 PM

Quote from: hobocoe on December 07, 2018, 08:08:54 PM

So im having some issues with the miner. Ive tried everything on my end, and cant get rid of the crashes.

here's my system:
Windows 10 home
ASUS Z270-A-PRO
G3930 Celeron
16gb of RAM
128gb SSD
1 Gigabyte vega 56

When I tried to start the miner originally I was getting a bunch of errors (namely the 1500C temp error and it would lock up the system and put all fans to max) so, i updated to the 4.0b build from 3.5.

Initially the miner was showing 2 Vega GPU's (only 1 installed) and was trying to mine with both of them at the same time. One was around 21mh/s the other was about 8mh/s (non dual mining just trying eth.) To fix this I used the -gpus 1 to tell it just to use 1 GPU, that managed to get it working and mining at normal speed using 1 "card". But, after some random time, usually around an hour into mining, the miner stops hashing and doesnt spit out an error, eventually when you try to move the mouse or hit any key on the keyboard it locks up the system and the only option is to hard shutdown.

So with this and some searching I tried many things, removing the OC settings in Wattman (same result), updating windows (same result), then I updated the driver to the newest beta one and that managed to get it to work with out crashing. Then I implemented dual mining and tested for a couple days with no issues, so then I ran xmr-stak to CPU mine, and tested for a couple days as well. After testing for a couple days I went on vacation, came back it ran fine even through multiple internet drops (typical cable internet issues that have since been fixed with hundreds of dollars of equipment lol) each time reconnecting and continuing to hash like it should. Yesterday, I received my order for some new noctua fans and I shut down the computer and installed the fans. upon rebooting I was getting the same eventual hang in the system.

So I dug into windows update thinking it must have installed an update and was causing this issue. So I uninstalled the update that showed it installed yesterday (besides an adobe flash one as I didnt think that would affect this situation) and its still having the same result. I updated the GPU driver to the newest beta again and still the same issue. Ive since constrained windows update even more than I had it before, to try to prevent something like this in the future.

So with both the 18.11.2 ( i think it was) and the newest 18.12.1.1 beta driver I get the same results.
below is a snippet of the log when it failed, from what I can tell its not showing any errors.

Code:

2018.12.07:11:09:39.599: main *** 1:36 *** 12/7 11:09 **************************************
2018.12.07:11:09:39.599: main Eth: Mining ETH on naw-eth.hiveon.net:4444 for 1:36
2018.12.07:11:09:39.599: main Eth: Accepted shares 42 (0 stales), rejected shares 0 (0 stales)
2018.12.07:11:09:39.599: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.12.07:11:09:39.599: main B2S: Accepted shares 114 (0 stales), rejected shares 0 (0 stales)
2018.12.07:11:09:39.599: main B2S: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.12.07:11:09:39.599: main Eth: Maximum difficulty of found share: 37.8 GH (!)
2018.12.07:11:09:39.599: main Eth: Average speed (5 min): 37.595 MH/s
2018.12.07:11:09:39.599: main Eth: Effective speed: 29.10 MH/s; at pool: 29.10 MH/s
2018.12.07:11:09:39.599: main B2S: Average speed (5 min): 1127.842 MH/s
2018.12.07:11:09:39.599: main B2S: Effective speed: 1086.03 MH/s; at pool: 1086.03 MH/s
2018.12.07:11:09:39.599: main
2018.12.07:11:09:39.662: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","worker":"test","params":[]}

2018.12.07:11:09:39.762: eths Eth: Received: {"jsonrpc":"2.0","result":["0xe13a2a342758ec7cefd8f38301b96583af181a0a1e5283a6f963d97deb1f1715","0xd9fa539e539d09362305f037610448e954ff0c3ef9d32854040c1c0c8cfa45a7","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.12.07:11:09:43.061: eths Eth: Received: { "id":0 , "jsonrpc":"2.0", "result": ["0x3d6aa7cbc4e584f537233d1e98c760608cdb90c4869d4e6d62dfa5a45b6495b5","0xd9fa539e539d09362305f037610448e954ff0c3ef9d32854040c1c0c8cfa45a7","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"] }
2018.12.07:11:09:43.061: eths Eth: New job #3d6aa7cb from naw-eth.hiveon.net:4444; diff: 4000MH
2018.12.07:11:09:44.605: main Eth speed: 37.311 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:09:44.605: main B2S speed: 1119.315 MH/s, shares: 114/0/0
2018.12.07:11:09:48.065: eths Eth: Received: { "id":0 , "jsonrpc":"2.0", "result": ["0xf779042bcafe4f48beb5364925785e556fcbf274d32c679127fc476e7b5b355c","0xd9fa539e539d09362305f037610448e954ff0c3ef9d32854040c1c0c8cfa45a7","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"] }
2018.12.07:11:09:48.065: eths Eth: New job #f779042b from naw-eth.hiveon.net:4444; diff: 4000MH
2018.12.07:11:09:49.804: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:09:49.804: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:09:54.830: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:09:54.830: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:09:59.973: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:09:59.973: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:01.017: duas B2S: Received: {"id":null,"method":"mining.notify","params":["5e1","d020859b8e0ebb0954b3b49511fb9419e0237444297a183bc625eb89630b3d9d","0200000040b60a5c010000000000000000000000000000000000000000000000000000000000000000ffffffff1f03f88229062f503253482f0478b70a5c08","7969696d700000000000012071842b000000002321037670d24409d242e8dd518bf6aaab36162c8536a3e8789892d7db79cf401ca3e1ac00000000",["8ecd9e09f8831e65d1e6f5f19acc409bdb057bbb3f8304e902a6eb6f527b5d7f"],"00002004","1a03628a","5c0ab640",true]}
2018.12.07:11:10:05.180: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:10:05.180: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:10.212: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:10:10.212: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:15.215: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:10:15.215: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:20.291: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:36
2018.12.07:11:10:20.291: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:24.689: main
2018.12.07:11:10:24.689: main *** 1:36 *** 12/7 11:10 **************************************
2018.12.07:11:10:24.689: main Eth: Mining ETH on naw-eth.hiveon.net:4444 for 1:36
2018.12.07:11:10:24.689: main Eth: Accepted shares 42 (0 stales), rejected shares 0 (0 stales)
2018.12.07:11:10:24.689: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.12.07:11:10:24.689: main B2S: Accepted shares 114 (0 stales), rejected shares 0 (0 stales)
2018.12.07:11:10:24.689: main B2S: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.12.07:11:10:24.689: main Eth: Maximum difficulty of found share: 37.8 GH (!)
2018.12.07:11:10:24.689: main Eth: Average speed (5 min): 31.891 MH/s
2018.12.07:11:10:24.689: main Eth: Effective speed: 28.87 MH/s; at pool: 28.87 MH/s
2018.12.07:11:10:24.689: main B2S: Average speed (5 min): 956.723 MH/s
2018.12.07:11:10:24.689: main B2S: Effective speed: 1077.63 MH/s; at pool: 1077.63 MH/s
2018.12.07:11:10:24.689: main
2018.12.07:11:10:25.363: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:25.363: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:30.476: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:30.476: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:35.682: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:35.682: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:40.724: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:40.724: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:45.930: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:45.930: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:50.989: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:50.989: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:10:56.181: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:10:56.181: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:11:01.420: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:11:01.420: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:11:05.395: wdog GPU1 not responding
2018.12.07:11:11:05.395: wdog Thread(s) not responding. Restarting.
2018.12.07:11:11:06.630: main Eth speed: 0.000 MH/s, shares: 42/0/0, time: 1:37
2018.12.07:11:11:06.630: main B2S speed: 0.000 MH/s, shares: 114/0/0
2018.12.07:11:11:09.812: main
2018.12.07:11:11:09.812: main *** 1:37 *** 12/7 11:11 **************************************
2018.12.07:11:11:09.812: main Eth: Mining ETH on naw-eth.hiveon.net:4444 for 1:37
2018.12.07:11:11:09.812: main Eth: Accepted shares 42 (0 stales), rejected shares 0 (0 stales)
2018.12.07:11:11:09.812: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.12.07:11:11:09.812: main B2S: Accepted shares 114 (0 stales), rejected shares 0 (0 stales)
2018.12.07:11:11:09.812: main B2S: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.12.07:11:11:09.812: main Eth: Maximum difficulty of found share: 37.8 GH (!)
2018.12.07:11:11:09.812: main Eth: Average speed (5 min): 26.163 MH/s
2018.12.07:11:11:09.812: main Eth: Effective speed: 28.65 MH/s; at pool: 28.65 MH/s
2018.12.07:11:11:09.812: main B2S: Average speed (5 min): 784.903 MH/s
2018.12.07:11:11:09.812: main B2S: Effective speed: 1069.36 MH/s; at pool: 1069.36 MH/s
2018.12.07:11:11:09.812: main

If anyone has any trick or tips to get this issue fixed please let me know, I would love to get back the random stability that I had for that short time.

(Oh and thank you Phoenix crew for getting the Nvidia DAG issue resolved! I was finally able to use my Nvidia rig and tested it for 3 days with no issues!)

Thank you all for any help you can provide.

So after messing with it so much and it hanging in the middle of i guess an update install it destroyed my win install so i went ahead and upgraded to my new drive and installed windows 10 pro fresh. everything was good for about 3 hours then it locked up which is the longest ive been able to get it to run besides the one 12 day period randomly.

We have one Gigabyte Vega 56 and it is a real PITA as far as stability goes, even without any overclock. Basically, the problem is probably related to overheating HBM. Make sure that the temperature limit of the card is set very low (e.g. no more than 60 degrees C) because the memory will almost always be much hotter. Also the fan must be allowed go at least to 60% and you must make sure that there is relatively cool airflow for the card (i.e. don't put it in the middle where it sucks hot air from the other cards). Note that this is not Vega problem but Gigabyte problem - we have two other Vega cards from PowerColor and they work fine without any stability issues.

Quote from: yoonline on December 08, 2018, 01:27:45 AM

Code:

2018.12.08:02:23:40.345: main Phoenix Miner 4.0b Windows/msvc - Release build

2018.12.08:02:23:40.345: main No CUDA driver found
2018.12.08:02:23:42.121: main OpenCL driver version: 17.8-BETA
2018.12.08:02:23:42.121: main Available GPUs for mining:
2018.12.08:02:23:42.121: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 1.2, 3 GB VRAM, 36 CUs
2018.12.08:02:23:42.121: main GPU2: Radeon RX 580 Series (pcie 3), OpenCL 1.2, 3 GB VRAM, 36 CUs
2018.12.08:02:23:42.121: main GPU3: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 3 GB VRAM, 36 CUs
2018.12.08:02:23:42.121: main GPU4: Radeon RX 580 Series (pcie 6), OpenCL 1.2, 3 GB VRAM, 36 CUs
2018.12.08:02:23:42.121: main GPU5: Radeon RX 580 Series (pcie 8), OpenCL 1.2, 3 GB VRAM, 36 CUs

2018.12.08:02:23:43.710: main Starting GPU mining
2018.12.08:02:23:43.710: main Matched GPU1 to ADL adapter index 6 (method 1)
2018.12.08:02:23:43.737: main GPU1: Using the X2 ODN API
2018.12.08:02:23:43.737: main GPU1: Created ADL monitor for adapter 6; overdrive version: 7
2018.12.08:02:23:43.737: main GPU1: using the blockchain beta driver
2018.12.08:02:23:43.737: main Matched GPU2 to ADL adapter index 24 (method 1)
2018.12.08:02:23:43.763: main GPU2: Using the X2 ODN API
2018.12.08:02:23:43.763: main GPU2: Created ADL monitor for adapter 24; overdrive version: 7
2018.12.08:02:23:43.764: main GPU2: using the blockchain beta driver
2018.12.08:02:23:43.764: main Matched GPU3 to ADL adapter index 18 (method 1)
2018.12.08:02:23:43.792: main GPU3: Using the X2 ODN API
2018.12.08:02:23:43.792: main GPU3: Created ADL monitor for adapter 18; overdrive version: 7
2018.12.08:02:23:43.792: main GPU3: using the blockchain beta driver
2018.12.08:02:23:43.792: main Matched GPU4 to ADL adapter index 0 (method 1)
2018.12.08:02:23:43.820: main GPU4: Using the X2 ODN API
2018.12.08:02:23:43.820: main GPU4: Created ADL monitor for adapter 0; overdrive version: 7
2018.12.08:02:23:43.820: main GPU4: using the blockchain beta driver
2018.12.08:02:23:43.820: main Matched GPU5 to ADL adapter index 12 (method 1)
2018.12.08:02:23:43.848: main GPU5: Using the X2 ODN API
2018.12.08:02:23:43.848: main GPU5: Created ADL monitor for adapter 12; overdrive version: 7
2018.12.08:02:23:43.848: main GPU5: using the blockchain beta driver
2018.12.08:02:23:43.848: wdog Starting watchdog thread
2018.12.08:02:23:43.849: main Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.12.08:02:23:44.051: main Listening for CDM remote manager at port 3333 in read-only mode
2018.12.08:02:23:44.054: main GPU1: 28C 70%, GPU2: 26C 70%, GPU3: 28C 70%, GPU4: 27C 70%, GPU5: 28C 70%
2018.12.08:02:23:45.022: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (172.65.218.238)

2018.12.08:02:23:45.214: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.12.08:02:23:45.214: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.12.08:02:23:45.368: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x4f508231e87cdba2ccb108dd61fb36a8396f5c39f0f7235f9278355a4087e4fe","0xd9fa539e539d09362305f037610448e954ff0c3ef9d32854040c1c0c8cfa45a7","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x68757f"]}
2018.12.08:02:23:45.368: eths Eth: New job #4f508231 from us1.ethermine.org:4444; diff: 4000MH
2018.12.08:02:23:45.368: GPU1 GPU1: Starting up... (0)
2018.12.08:02:23:45.369: GPU1 GPU1: Generating ethash light cache for epoch #228
2018.12.08:02:23:45.370: GPU2 GPU2: Starting up... (0)
2018.12.08:02:23:45.372: GPU3 GPU3: Starting up... (0)
2018.12.08:02:23:45.374: GPU4 GPU4: Starting up... (0)
2018.12.08:02:23:45.376: GPU5 GPU5: Starting up... (0)
2018.12.08:02:23:48.578: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x562566f0f8be03dcf25ae394daa6f4ad1118b4b59c468ac6984c7bd03fd9149a","0xd9fa539e539d09362305f037610448e954ff0c3ef9d32854040c1c0c8cfa45a7","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x687580"]}
2018.12.08:02:23:48.578: eths Eth: New job #562566f0 from us1.ethermine.org:4444; diff: 4000MH
2018.12.08:02:23:48.874: GPU1 Light cache generated in 3.5 s (12.7 MB/s)
2018.12.08:02:23:48.929: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.12.08:02:23:48.929: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0)
2018.12.08:02:23:49.008: GPU1 GPU1: clCreateCommandQueue (-6)
2018.12.08:02:23:49.114: GPU3 GPU3: clCreateCommandQueue (-6)
2018.12.08:02:23:49.216: GPU4 GPU4: clCreateCommandQueue (-6)
2018.12.08:02:23:49.319: GPU5 GPU5: clCreateCommandQueue (-6)
2018.12.08:02:23:49.421: GPU2 GPU2: clCreateCommandQueue (-6)
2018.12.08:02:23:49.849: wdog Thread(s) not responding. Restarting.
2018.12.08:02:23:50.078: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x0581642034553cd9947e039b68a21d84753436db76ee2f91866a9aee0ffc8865","0xd9fa539e539d09362305f037610448e954ff0c3ef9d32854040c1c0c8cfa45a7","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x687581"]}
2018.12.08:02:23:50.078: eths Eth: New job #05816420 from us1.ethermine.org:4444; diff: 4000MH
2018.12.08:02:23:50.097: GPU1 GPU1: Starting up... (0)
2018.12.08:02:23:50.113: GPU2 GPU2: Starting up... (0)
2018.12.08:02:23:50.118: GPU3 GPU3: Starting up... (0)
2018.12.08:02:23:50.136: GPU4 GPU4: Starting up... (0)
2018.12.08:02:23:50.155: GPU5 GPU5: Starting up... (0)

WINDOWS 10 Block chaindriver. Im having this problem
run great with Claymore, but i want to use phoenix..

Definitely a driver issue. The cards are shown having 3 GB VRAM and only OpenCL 1.2 (they must show 4 GB VRAM and OpenCL 2.0). Still, before reinstalling the drivers, check the Task Manager to see if there is any running instance of PhoenixMiner or any other miner and if so, restart Windows.
If this doesn't help, use DDU to remove the current drivers completely, then install them again (the blockchain drivers will do but obviously they are messed up somehow, so better use newer drivers, for example 18.5.1 and make sure that the Compute mode is turned on).

Quote from: Digital_Seytan on December 08, 2018, 11:52:37 AM

Why only dual mining only AMD cards and not Nvidia cards PM dev??

We will be adding dual mining for Nvidia GPUs in the next version.