 Show Posts
|
|
Pages: [1]
|
Doktor, i also have issue to report goes like this have 4 rigs, all 4 of them go from xmr stak to srbminer1.5.8 each rig 6x Vega 18.5.2 all 4 rigs run super stable with srbminer one of the rigs i restart for some reason after like 2000 minutes of uptime other 3 rigs run for like 3000-3500 minutes of uptime and then all crash at approximate the same time the miner stopped saying GPU hashrate 0, restarting miner, but miner could not restart, even by process kill or try to reset PC, it hangs in reset process. Only hard reset help Why would all miners stop at same uptime?  Anyway, I reset all so canīt really say what happened or give any more details, but i will monitor this time and see if it happen again Otherwise, i fell in love with your miner. i have the same Problem, It got better with windows 1803 and amd driver 18.5.1 now after 3 days, when the gpu Crash, the Windows freeze... |
|
|
|
Doktor, i also have issue to report goes like this have 4 rigs, all 4 of them go from xmr stak to srbminer1.5.8 each rig 6x Vega 18.5.2 all 4 rigs run super stable with srbminer one of the rigs i restart for some reason after like 2000 minutes of uptime other 3 rigs run for like 3000-3500 minutes of uptime and then all crash at approximate the same time the miner stopped saying GPU hashrate 0, restarting miner, but miner could not restart, even by process kill or try to reset PC, it hangs in reset process. Only hard reset help Why would all miners stop at same uptime? Anyway, I reset all so canīt really say what happened or give any more details, but i will monitor this time and see if it happen again Otherwise, i fell in love with your miner. i have the same Problem, It got better with windows 1803 and amd driver 18.5.1 |
|
|
|
|
When I use the function enable and disable vega card, I get the following error: cl_out_of_host_memory when creating clCreateCommandQueue for DeviceID 0 (Thread 0) , does somebody has any idea?
|
|
|
|
how should I enter the command that adl is enabled?
If you don't point option to disable adl it enabled by default. thanks  |
|
|
|
|
how should I enter the command that adl is enabled?
|
|
|
|
my rig have a strange pattern, every 48 hours nontsop mining will get 90 Celcius shutdown , while my GPU not showing any burned effect , anyone know how to fixed this ?
i'm using SRB latest version.
had same issue when running SRB 1.5.1 on windows 1803 update. So when i rollback to 1709 windows 10, everything look fine.
So, if you updated to 1803 probably that's causing the problem, or worse if your gpu's are really getting to 90c. By default if not set "shutdown_temperature", is set to 90c. I will just disable this default setup, so if "shutdown_temperature" is not explicitly set in config, it wont be enabled and no more problems on 1803. i not set the "shutdown_temperature" and the rig make a reboot and his freeze, i have Windows Version 1709 :9 Same for me. Set "shutdown_temperature" or not in config file the result same. My rig alway auto shutdown. My card very cool at 50c. I will test new ver 1.5.6 today Its not set automatically to 90c anymore, so you shouldnt have a prpblem anymore. Report please just run 5 minuties in 1.5.6, when one of gpu hash rate = 0 cause maybe i OC too hight your tool make my rig hang remotely, cant use teamview and vnc. i am going back home to connect my rig to monitor and use mouse to close tool and run again  . Can you fix pls ? I have now the small rig on windows version 1803 updatet and amd driver 18.3.4 installed. miner version 1.5.6 (hbm @ 1100mhz \ 905mV, Vega 64 runs at about 2.05khs) |
|
|
|
my rig have a strange pattern, every 48 hours nontsop mining will get 90 Celcius shutdown , while my GPU not showing any burned effect , anyone know how to fixed this ?
i'm using SRB latest version.
had same issue when running SRB 1.5.1 on windows 1803 update. So when i rollback to 1709 windows 10, everything look fine.
So, if you updated to 1803 probably that's causing the problem, or worse if your gpu's are really getting to 90c. By default if not set "shutdown_temperature", is set to 90c. I will just disable this default setup, so if "shutdown_temperature" is not explicitly set in config, it wont be enabled and no more problems on 1803. i not set the "shutdown_temperature" and the rig make a reboot and his freeze, i have Windows Version 1709 :9 |
|
|
|
Hello, I have the problem in between, the miner complained that he overheated and then want to restart. then the mining rig crashes. I have 5 Vega 64 in the rig and use version 1.5.5.1, do you have an idea? What's weird is that I have a second rig with 3 x Vega 64 and this is crashes at the same time. Sometimes the whole works without problems 3 days...
does it say "critical shutdown, temperature reach 90C" ?? i had same issue when running SRB 1.5.1 on windows 1803 update. So when i rollback to 1709 windows 10, everything look fine. have you checked, maybe it really reached 90c ? No, it doesnt reached 90c, my GPU is 45c |
|
|
|
|
Hello, I have the problem in between, the miner complained that he overheated and then want to restart. then the mining rig crashes. I have 5 Vega 64 in the rig and use version 1.5.5.1, do you have an idea? What's weird is that I have a second rig with 3 x Vega 64 and this is crashes at the same time. Sometimes the whole works without problems 3 days...
|
|
|
|
|
