After almost 10 days of trying all kinds of combinations and testing with RTX 3060 I can easily conclude:
Hiveos is, at least in its current state, almost unusable for mining.
The main thing I notice: It works completely neatly, but after turning it off and on, so the completely identical configuration and settings of everything Hiveos behaves completely differently, reports an error and closes in a loop without starting mining. How to characterize it if not as a semi-finished product. Proper startup has nothing to do with settings but with sheer luck whether it will work or not. Which times it works from the first, and most often it doesn’t. That’s about it.
You have a problem thats all. I didnt have any problem so far and i restarted many times and i changed oc settings many times and miners and all kinds of tests. Now when i restart it works every time the same way.
My position is based on how Hiveos works. Take Excel for example. How you should rate if as, it functioned as Hiveos, When it fell out of work three times in five hours. And that happens with Hiveos to everyone.
it doesnt happen to me. it runs fine for days if i dont mess things with the rig.
I installed my first hive OS a few hours ago. Restarted it a couple of time, it went without a itch.
Do you turn it off using the shutdown icon like in windows? Have you tried it on an alternate motherboard? What type of hard disk are you using as your rig’s system disk?
I tried on both ways, by the icon and by the switcher. My MB is Asus Prime Z490-P. If it is wrong the question is which is right then. HD is Gigabyte SSD 128 GB. And the question for example is what will be with Windows which MB and HD are in use.
Mh, I don’t know then how to guide you further - I’m very novice. I may suggest the obvious such as whether you are using stable versions instead of beta.
Have you attempted to upgrade to the hive OS latest stable build (you can do it in one-click from interface)
Rig works all night for 8 hours ok and then suddenly starts falling out every 3 minutes and comes back after 2 minutes. And so constantly.
Message:
“TREX: Can’t find nonce with device [ID = 1, GPU # 2], cuda exception: CUDA_ERROR_LAUNCH_FAILED, try to reduce overclock to stabilize GPU state”
My OC is core -200 mem 1700. Miner T-Rex pool Hiveon, mining ETH
Version is 0.6-206@210722 (the latest)
Have you tried another miner?
At what speed are you mining?
Which card is this with 1700 memory clock. Also use absolute core clock not bastract. Search for better OC settings. You card is crashing due to this
Or it overheats after 8 hour of work
Really funny that you made such conclusion when most users including professional miners all use HiveOS without issues. How many hardware do you have? Maybe 1 board and 1 3060. So most likely is your hardware issue.
In fact I have enaugh hardware considering I’m not a professional miner. (4 rigs with total of 20 GPU). Until now having tried all the combinations and I concluded that the only ok combination is with Lolminer and Hiveon pool. With 4 pcs of RTX 3060 I get 150 MH/s and this is only combination which is stabile for a days. All other combinations (other miners) fall within a few minutes or one hour especially the T-rex miner when I tried fan glitch from NBMiner and Nanopool . I got 0% fan and when I changed Flightsheet to T- Tex it becomes unstable after a minute or two or does not connect at all .
So that’s my conclusion whether someone liked it or not
Hmm, seems like you are trying to get stable with a couple of 3060s with the glitch method. I do not think HiveOS was designed specifically to glitch LHR cards, therefore I think the assessment was unfair. Try to run 3060s without glitch, if they are still not stable then perhaps the community here could help.
First of all the cards are not LHR
Why are you trying to glitch them if not LHR?
you are just doing it wrong. hiveos works great.
show us your settings.
stop bashing hiveos for your incompetence. unbelievable what you write.
as a start for example with ergo:
nvidia driver 460.39 (THIS IS THE ONLY ONE FOR 3060s V1 working correctly, blame nvidia not hive.)
nbminer 37.3
core 1550 mem 2500 power 130
124.x mh/s
all 3060s are LHR. v2 a bit more locked than v1.
First of all the termin LHR existed a month or two ago. Prior to that, no GPU was an LHR. The term was introduced by Nvidia along with a restriction on the GPU for mining.
The question is how the Glitch works on a real LHR GPU. Whether it works or not