 Show Posts
|
|
Pages: « 1 [2]
|
JSON: is it really forbidden by the json standard to write rather than ? It may be acceptable by json standard but any json validator fixes the code that way. May be the problem occurs when using 'json.parse' where every single string should be understood as it should be. For example the string starting with "hashrate": should end with a value or a bracket. I maybe wrong ofcourse. |
|
|
|
When i see temps like this... i want to cry.
Yep. That's insanity. |
|
|
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:  Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close. Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen. Hey, I just wanted to report that it seems I've fixed my issue. My X399 Taichi originally came with the 2.00 BIOS version, I just updated to the 2.30 Bridge BIOS and both cards are now working fully. Imagine that… Hopefully this will stop thread_stuck_in_device_driver and video_memory_management_internal BSODs, but eh. Meh, once again I celebrated too early… This time hash on the second GPU started dropping after a couple of hours, and its still around 1k or less, even if I restart my PC. WTH already. I'll see what will happen when I reinstall Windows. How much is the temperature on the cards? It's written - ~70C. HBM must be hell-hot that way. I wonder why does that vega still alive. I'm running my V64 at 40-45C GPU and about 45-50C HBM at 1478/1100 by HWinfo. |
|
|
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed: Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close. Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen. Hey, I just wanted to report that it seems I've fixed my issue. My X399 Taichi originally came with the 2.00 BIOS version, I just updated to the 2.30 Bridge BIOS and both cards are now working fully. Imagine that… Hopefully this will stop thread_stuck_in_device_driver and video_memory_management_internal BSODs, but eh. Meh, once again I celebrated too early… This time hash on the second GPU started dropping after a couple of hours, and its still around 1k or less, even if I restart my PC. WTH already. I'll see what will happen when I reinstall Windows. Maybe increasing swapfile can help. Or reducing intensity. |
|
|
|
|
Didn't find any ready to use jce-monitor and tried to make it myself. Being not much strong in js I've stuck with json syntax error.
Miner seems to send unvalid json with syntax like
"hashrate":
{
instead of
"hashrate": {
and
"gpu_status":
[
{
instead of
"gpu_status": [{
Will try to rewrite it later. Maybe I've missed smth. Or I'll find the way to make json valid to parse strings for html normally.
|
|
|
|
Hi Doc,
I maybe found a Bug in latest Miner and Profit switching. In my config, I set in each the 5 min average hashrate for restart, but when Miner switch from a higher HR Algo (fast) to a slower one (maybe haben) it does not reset the values and restart the Miner with the text that average HR is lower than defined.
Can you please check it? After the Algo switch Miner should load the average HR value and reset the average numbers...
Oliver
Had the same. Solves with --resetmineronalgoswitch when running as admin. |
|
|
|
|
When using algoswitch on moneroocean with "min_rig_speed" set in each config*.txt, the miner doesn't change it after switching. It uses that parameter from the first started config (which is set in batch file).
|
|
|
|
|
Vega 64 V8 (18.6.1 driver)
"worksize": 8, "intensity" : 123, "double_threads" : true, "persistent_memory": true, "bralock": 2
PPT + 1486/878 1100/878
2030 h/s
Don't actually understand what "persistent_memory" and "bralock" does but in some variants it give a less higher hashrate so I've left it here.
V8 really needs more power. It doesn't work with 875mV for me but with 878mV it seems ok.
|
|
|
|
I just checked on my test machines i have win10 v1703 and v1709, also win7 x64. @hesido I will (re) introduce a parameter in 1.6.9, which will probably help you re-gain the hashrate you had. Just have to make the algo switching crash-free first  Well, hurry up, doc, you've got 24 hours! (well actually less 'cause we can't really test at night)... Can someone tell me how I can test CNv8 please? I need some kind of test-pool I can point my hash towards. Try to mine Wownero. It is already at v8. |
|
|
|
|
