So, about a month ago I bought the Vega 56 to use in my 2nd mining rig due to the very nice monero hashrate on it.
Installed the Vega 64 bios on it just to see how it performed with overclocks. Didn't get a good stability, so ended up with wattman settings: -30% gpu freq, 950 mem, -20% power.
After some struggle with using a riser on it (got ~1300H/s) I ended up putting it directly in the PCIe x16 slot and been hasing at ~1800H/s for a good month now.
The time to expand came so I bought 2 more Vega 56's along with a EVGA G2 1600W PSU to prepeare for future expansion of 3 more Vega 56's.
I get the PSU and cards, flash the Vega 64 bios on both the two new 56's, HBCC configured, raised windows virtual memory to 60GB, set the same wattman settings as mentioned above.
Fired up xmr-stak-amd-notls with these settings:
"gpu_threads_conf" : [
{ "index" : 0, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
{ "index" : 0, "intensity" : 1600, "worksize" : 8, "affine_to_cpu" : false },
{ "index" : 1, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
{ "index" : 1, "intensity" : 1600, "worksize" : 8, "affine_to_cpu" : false },
{ "index" : 2, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
{ "index" : 2, "intensity" : 1600, "worksize" : 8, "affine_to_cpu" : false },
],
The first thing I notice is that 2 of the cards jump right to just below 1800H/s and the 3rd sits down at ~1300H/s which I'm assuming is the card connected to the PCIe x16 slot as mentioned above.
I though this was a power issue with the previous PSU, but now I guess its more pointing to the motherboard I had laying around that I decided to use until I reach 3 GPUs.
However, the real issue here is stability. After a couple of hours (sometimes just 15minutes) hashing it just stops hashing. The miner seemingly is alive, it just doesn't do anything.
If I ctrl-c it asks if I want to end the batch job, which indicates the process itself isn't hung I guess.
I tried different miners with the same result, lastly the cast-xmr miner.
I also tried flashing stock Vega 56 bios, running with no OC settings at all, always the same issue.
I'm leaning towards doing an early switch of the motherboard (it has just 1 PCIe x16 and 2 PCIe x1 so not exactly future ready for the rig..), but I'd like others input for other things to check.
Thanks!
Extra info:
OS: Windows 10 Pro
RAM: 16GB
SSD: 120GB
Driver: August 23 blockhain driver
Edit: Just happened again and I tried to check amd settings, but now that window is just blurred and even I stop the program and restart it continues just to be a blurred window on the screen.
Event viewer says:
Message 1:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1: 141
P2: ffffe501a85ef010
P3: fffff809a6d4f7d8
P4: 0
P5: 190c
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171128-0946.dmp
\\?\C:\Windows\TEMP\WER-2943937-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF45C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF46C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF46D.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_56df233ee0d876b17be48e5447a258e0bd4b64ed_00000000_cab_1938f47b
Analysis symbol:
Rechecking for solution: 0
Report Id: 4f0ff9fb-15c1-4fa4-afee-73c70644f2f8
Report Status: 4
Hashed bucket:
Message 2:
Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 091d0664-c644-4cbc-bbf7-02dcf25d9a03
Problem signature:
P1: 141
P2: ffffe501a85ef010
P3: fffff809a6d4f7d8
P4: 0
P5: 190c
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171128-0946.dmp
\\?\C:\Windows\TEMP\WER-2943937-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF45C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF46C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF46D.tmp.txt
\\?\C:\Windows\Temp\WER1718.tmp.WERDataCollectionStatus.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_56df233ee0d876b17be48e5447a258e0bd4b64ed_00000000_cab_1b911aa1
Analysis symbol:
Rechecking for solution: 0
Report Id: 4f0ff9fb-15c1-4fa4-afee-73c70644f2f8
Report Status: 268435456
Hashed bucket:
