Search content
Sort by
Showing 20 of 35 results by tomlev5
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
I would like to try ethminer + pill on nvOC. Is there an easy way to do this on V0019-2.0 (I have access to the rig on ssh)? Or is it best that I burn V19-2.1beta on a HDD?
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
Hello guys.
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
Sorry to hear that you have problems with 19-2.0. It is generally more stable but it is possible that it might perform worse on certain configurations. If you could provide more details we might be able to troubleshoot and help.
1) I don't remember the structure of v0019. I don't even remember if the small FAT partition was mounted correctly. It's quite an old version and won't be easy to guide you without installing v0019 on a rig just to see the structure. Basicly, you would need to copy 1bash from FAT partition to your /home folder then run it through dos2unix to convert it.
2) Although it is quite easy to upgrade to the latest version of the driver, it is not easy to downgrade since PPA repo keeps the latest driver only. If you can find the .deb package of an older driver you can install it manually with dpkg
You can get the driver version with this:
Code:
nvidia-smi -i 0 -q|grep "Driver Version"|cut -f 2 -d ":"|cut -f 2 -d " "
I think we can mount the small fat partition on v19 SSD installs and copy 1bash with following :
Code:
sudo mkdir -p /media/m1/12D3-A869/
sudo mount /dev/sda1 /media/m1/12D3-A869
cp '/media/m1/12D3-A869/1bash' '/home/m1/1bash'
dos2unix /home/m1/1bash
sudo mount /dev/sda1 /media/m1/12D3-A869
cp '/media/m1/12D3-A869/1bash' '/home/m1/1bash'
dos2unix /home/m1/1bash
Thanks papampi. I will try this code next time I go to the rigs.
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
Hello guys.
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
Sorry to hear that you have problems with 19-2.0. It is generally more stable but it is possible that it might perform worse on certain configurations. If you could provide more details we might be able to troubleshoot and help.
1) I don't remember the structure of v0019. I don't even remember if the small FAT partition was mounted correctly. It's quite an old version and won't be easy to guide you without installing v0019 on a rig just to see the structure. Basicly, you would need to copy 1bash from FAT partition to your /home folder then run it through dos2unix to convert it.
2) Although it is quite easy to upgrade to the latest version of the driver, it is not easy to downgrade since PPA repo keeps the latest driver only. If you can find the .deb package of an older driver you can install it manually with dpkg
You can get the driver version with this:
Code:
nvidia-smi -i 0 -q|grep "Driver Version"|cut -f 2 -d ":"|cut -f 2 -d " "
Thanks, I got nvOC_v0019 nvidia driver version: 384.59
My configuration is ASRock H110 Pro BTC+ with 13 1080tis (different versions of tis). I will try to change the configuration (move some GPUs to antoher machine) and then try to trubleshoot.
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
Hello guys.
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
I was using nvOC_v0019 for a couple of months and then I switched to nvOC v0019-2.0.
I like all the new features of nvOC v0019-2.0 but I have problems with stability.
The nvOC_v0019 lasted around 10 days without freezes but nvOC v0019-2.0 lasts only a day or two and then freezes. I went back to nvOC_v0019 and stability improved.
I use SSH to access the miner.
I have two questions:
1) Can you help me with a command that will copy 1bash from 8MB windows partition to the right place, that it will be used on startup (nvOC_v0019 has a problem that it doesn't copy 1bash on first start with HDD)
2) I suspect that the problem with nvOC v0019-2.0 is in newer drivers. Fullzero also wrote that vBASIC uses an older Nvidia Driver. Can anybody give me some instructions that will uninstall nvidia drivers in nvOC v0019-2.0 and then install older drivers?
I would use the vBASIC, but it really lacks a lot of features ...
Fullzero, can you please tell me which driver version do you use in vBASIC and which version in nvOC_v0019?
Whitch command can I use to get Nvidia driver version?
I have two rigs both mining ZCL on Supernova and this has happened twice that both rigs will freeze within a minute of eachother. I saw the first time while being connected via teamviewer that the server "disconnects" briefly within the miner and that watchdog will then re-start the 3main, get hung up and freeze. I assume this is what happened again. I would point to a hardware issue, but both separately going down at the same time with no telegram errors? Too much of a coincidence. I don't have any of the cards overclocked at this point, both systems were up for almost two days before the last freeze.
This keeps happening over and over again. I am going to try a new mining pool, but I've liked SuperNova. I have zero issues with it on my personal desktop with two 1070 Ti's on windows and using Awesome Miner.
Any thoughts would be great.
Hello urnzwy! Do you have Asrock H110 Pro Btc+ motherboard?This keeps happening over and over again. I am going to try a new mining pool, but I've liked SuperNova. I have zero issues with it on my personal desktop with two 1070 Ti's on windows and using Awesome Miner.
Any thoughts would be great.
I have two rigs with this motherboard. When one freezes the other one looses the internet connection.
I got error "Access denied", but I didn't change the password.
if it's still miner1, you should really change it. (passwd m1)
Also, use command history
This'll show you if anything has been done during the "access denied" period.
The miner is hidden behind a firewall so i am OK with this default password ...
Hello guys.
Today i tried to log into the rig (both rigs) through SSH with m1 / miner1.
I got error "Access denied", but I didn't change the password.
Does somebody know what could be the problem?
Is there some other standard password for nvOC?
EDIT: Now I have successfully logged in. I don't know what was wrong before, but it wasn't a typo (I tried many times on both rigs with the same keyboard as now)
Today i tried to log into the rig (both rigs) through SSH with m1 / miner1.
I got error "Access denied", but I didn't change the password.
Does somebody know what could be the problem?
Is there some other standard password for nvOC?
EDIT: Now I have successfully logged in. I don't know what was wrong before, but it wasn't a typo (I tried many times on both rigs with the same keyboard as now)
Hi!
Previously I was using HDDRawCopy to burn nvOC image to USB key. After the image was copied, all I had to do, was to copy my prepared 1bash file to 9MB fat partition and the USB key was ready to go for any rig (Both rigs used the same image and the same settings).
Now I read that nvOC is more stable on HDD (or SSD) so I used HDDRawCopy to burn nvOC image to HDD.
I have edited 1bash in 9MB fat partition, but now the file wasn't automatically copied to /home/m1/1bash (Like it was on USB key).
My 1bash stayed on the /dev/sda1 partition (9MB fat partition).
Sorry I am a complete linux newbie so I have to ask this:
What command would copy my 1bash from /dev/sda1 partition to /home/m1/1bash?
Papampi, leenoox, how do you guys deploy settings to multiple rigs (I guess you use some different method)?
Previously I was using HDDRawCopy to burn nvOC image to USB key. After the image was copied, all I had to do, was to copy my prepared 1bash file to 9MB fat partition and the USB key was ready to go for any rig (Both rigs used the same image and the same settings).
Now I read that nvOC is more stable on HDD (or SSD) so I used HDDRawCopy to burn nvOC image to HDD.
I have edited 1bash in 9MB fat partition, but now the file wasn't automatically copied to /home/m1/1bash (Like it was on USB key).
My 1bash stayed on the /dev/sda1 partition (9MB fat partition).
Sorry I am a complete linux newbie so I have to ask this:
What command would copy my 1bash from /dev/sda1 partition to /home/m1/1bash?
Papampi, leenoox, how do you guys deploy settings to multiple rigs (I guess you use some different method)?
If you use the nvOC v0019-2.0 Shrinked Image, it should copy 1bash from 9mb and auto expand after first boot.
Code:
Image size: 11 GB
ZIP size: 3.8 GB
Auto Expand to full size on first boot
Fixed copy 1bash from fat partition to SSD/HDD on first boot
SHA256: ACCA9787169E6E722ED74FB02DBE1C44E7760CEB537CB79D4C61C7FFF8AD3057
ZIP size: 3.8 GB
Auto Expand to full size on first boot
Fixed copy 1bash from fat partition to SSD/HDD on first boot
SHA256: ACCA9787169E6E722ED74FB02DBE1C44E7760CEB537CB79D4C61C7FFF8AD3057
Papampi, i tested the shrinked image and it works for me. Copy of 1bash from fat partition to HDD on first boot succeeded and nvOC works flawlessly.
Thanks for your help.
I have some problems with stability, but I think there is something wrong with my hardware. Will have to check the logs.
Which log should I look at if the rig freezes?
Hi!
Previously I was using HDDRawCopy to burn nvOC image to USB key. After the image was copied, all I had to do, was to copy my prepared 1bash file to 9MB fat partition and the USB key was ready to go for any rig (Both rigs used the same image and the same settings).
Now I read that nvOC is more stable on HDD (or SSD) so I used HDDRawCopy to burn nvOC image to HDD.
I have edited 1bash in 9MB fat partition, but now the file wasn't automatically copied to /home/m1/1bash (Like it was on USB key).
My 1bash stayed on the /dev/sda1 partition (9MB fat partition).
Sorry I am a complete linux newbie so I have to ask this:
What command would copy my 1bash from /dev/sda1 partition to /home/m1/1bash?
Papampi, leenoox, how do you guys deploy settings to multiple rigs (I guess you use some different method)?
Previously I was using HDDRawCopy to burn nvOC image to USB key. After the image was copied, all I had to do, was to copy my prepared 1bash file to 9MB fat partition and the USB key was ready to go for any rig (Both rigs used the same image and the same settings).
Now I read that nvOC is more stable on HDD (or SSD) so I used HDDRawCopy to burn nvOC image to HDD.
I have edited 1bash in 9MB fat partition, but now the file wasn't automatically copied to /home/m1/1bash (Like it was on USB key).
My 1bash stayed on the /dev/sda1 partition (9MB fat partition).
Sorry I am a complete linux newbie so I have to ask this:
What command would copy my 1bash from /dev/sda1 partition to /home/m1/1bash?
Papampi, leenoox, how do you guys deploy settings to multiple rigs (I guess you use some different method)?
If you use the nvOC v0019-2.0 Shrinked Image, it should copy 1bash from 9mb and auto expand after first boot.
Code:
Image size: 11 GB
ZIP size: 3.8 GB
Auto Expand to full size on first boot
Fixed copy 1bash from fat partition to SSD/HDD on first boot
SHA256: ACCA9787169E6E722ED74FB02DBE1C44E7760CEB537CB79D4C61C7FFF8AD3057
ZIP size: 3.8 GB
Auto Expand to full size on first boot
Fixed copy 1bash from fat partition to SSD/HDD on first boot
SHA256: ACCA9787169E6E722ED74FB02DBE1C44E7760CEB537CB79D4C61C7FFF8AD3057
Hi!
Previously I was using HDDRawCopy to burn nvOC image to USB key. After the image was copied, all I had to do, was to copy my prepared 1bash file to 9MB fat partition and the USB key was ready to go for any rig (Both rigs used the same image and the same settings).
Now I read that nvOC is more stable on HDD (or SSD) so I used HDDRawCopy to burn nvOC image to HDD.
I have edited 1bash in 9MB fat partition, but now the file wasn't automatically copied to /home/m1/1bash (Like it was on USB key).
My 1bash stayed on the /dev/sda1 partition (9MB fat partition).
Sorry I am a complete linux newbie so I have to ask this:
What command would copy my 1bash from /dev/sda1 partition to /home/m1/1bash?
Papampi, leenoox, how do you guys deploy settings to multiple rigs (I guess you use some different method)?
Previously I was using HDDRawCopy to burn nvOC image to USB key. After the image was copied, all I had to do, was to copy my prepared 1bash file to 9MB fat partition and the USB key was ready to go for any rig (Both rigs used the same image and the same settings).
Now I read that nvOC is more stable on HDD (or SSD) so I used HDDRawCopy to burn nvOC image to HDD.
I have edited 1bash in 9MB fat partition, but now the file wasn't automatically copied to /home/m1/1bash (Like it was on USB key).
My 1bash stayed on the /dev/sda1 partition (9MB fat partition).
Sorry I am a complete linux newbie so I have to ask this:
What command would copy my 1bash from /dev/sda1 partition to /home/m1/1bash?
Papampi, leenoox, how do you guys deploy settings to multiple rigs (I guess you use some different method)?
Hi!
I am waiting on the next stable release with v0019. v0019-1.4 was BETA and I don't know about v0019-2.0, is v0019-2.0 a stable release?
Does v0019-2.0 have all auto-updates disabled? (I would prefer to have automatic driver updates and automatic system updates disabled, I am afraid they will bring instability)
I am waiting on the next stable release with v0019. v0019-1.4 was BETA and I don't know about v0019-2.0, is v0019-2.0 a stable release?
Does v0019-2.0 have all auto-updates disabled? (I would prefer to have automatic driver updates and automatic system updates disabled, I am afraid they will bring instability)
I think an 80 plus platinum PSU efficiency is around 92%
6x120 watt is on verge of your PSU limit and it's natural to give up and lose GPU.
Either lower your power limit or use higher PSU
6x120 watt is on verge of your PSU limit and it's natural to give up and lose GPU.
Either lower your power limit or use higher PSU
I think there is some confusion here. Only 6 risers are powered by the EVGA. ALL cards (6+2) are powered by the 1400W PSUs. 7 (6+2) on one 1400W, 6 (6+2) powered by the other 1400W. The X-11 breakout boards are connected via a Molex to the mobo so all PSUs power on/off at the same time.
I think it is best to power a GPU and its riser from the same PSU.
So are we at a crossroads?
Why did some run off to the discord channel? Was some need not being met here?
Hopefully fullzero will be back at some point to "get the band back together".
Why did some run off to the discord channel? Was some need not being met here?
Hopefully fullzero will be back at some point to "get the band back together".
nvOC has a fork !
Yes, fullzero is busy with personal life and we are going to continue updating and making nvOC as good as we can.
Hopefully when he get time he will check and release an official update
Great work on the project guys. Its nice to see so much cooperation.
To prevent automatic updates in the future:
use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:
To:
and /etc/apt/apt.conf.d/20auto-upgrades
to
D
ps: Seriously, why was this ON?
use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:
Code:
APT::Periodic::Update-Package-Lists "1";
To:
Code:
APT::Periodic::Update-Package-Lists "0";
and /etc/apt/apt.conf.d/20auto-upgrades
Code:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::Unattended-Upgrade "1";
to
Code:
APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";
APT::Periodic::Unattended-Upgrade "0";
D
ps: Seriously, why was this ON?
Very nice suggestion Doodkeen,
This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,
So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.
Thank you all.
Yep, please feel free and provide the valuable feedback, so that we can make nvOC even better.
Coming to the error, no one expected this sort of failure on this scale!! Hope we identify these sort of issues bit earlier.
I think the problem is while Nvidia driver was updating wdog restarted the rig because of low utilization and that cause a miss configured Nvidia driver,
I think solution is to prevent wdog from restarting the rig if dpkg is running.
Papampi, you are absolutely right I think solution is to prevent wdog from restarting the rig if dpkg is running.
I had this happen to 2 of my rigs. I will change all the update settings for -1.4 except security updates. My bad.
- disable automatic downloads of updates (drivers, system, nvOC)
- disable automatic installation of updates (drivers, system, nvOC)
I have a rig behind a firewall and absolutely no important data on a nvOC rig, so all I care is about stability.
And stability is more fragile because of USB key usage.
The logging is disabled by default, so there would be no writing to the USB key if I would disable updates.
The nvOC is pretty stable even now, but I think that disabling all updates would help with the stability of the system.
Of course I would also periodically update USB key with the whole image of nvOC, but only every month or so, when you publish the new version of stable nvOC.
I have disabled all updates on -1.4; it does have logs. I will work on a global long variable implementation ( LOGS="ON" or OFF ) for the next version
Thank you for the time you take, to consider these requests.
To prevent automatic updates in the future:
use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:
To:
and /etc/apt/apt.conf.d/20auto-upgrades
to
D
ps: Seriously, why was this ON?
use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:
Code:
APT::Periodic::Update-Package-Lists "1";
To:
Code:
APT::Periodic::Update-Package-Lists "0";
and /etc/apt/apt.conf.d/20auto-upgrades
Code:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::Unattended-Upgrade "1";
to
Code:
APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";
APT::Periodic::Unattended-Upgrade "0";
D
ps: Seriously, why was this ON?
Very nice suggestion Doodkeen,
This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,
So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.
Thank you all.
Yep, please feel free and provide the valuable feedback, so that we can make nvOC even better.
Coming to the error, no one expected this sort of failure on this scale!! Hope we identify these sort of issues bit earlier.
I think the problem is while Nvidia driver was updating wdog restarted the rig because of low utilization and that cause a miss configured Nvidia driver,
I think solution is to prevent wdog from restarting the rig if dpkg is running.
Papampi, you are absolutely right I think solution is to prevent wdog from restarting the rig if dpkg is running.
I had this happen to 2 of my rigs. I will change all the update settings for -1.4 except security updates. My bad.
- disable automatic downloads of updates (drivers, system, nvOC)
- disable automatic installation of updates (drivers, system, nvOC)
I have a rig behind a firewall and absolutely no important data on a nvOC rig, so all I care is about stability.
And stability is more fragile because of USB key usage.
The logging is disabled by default, so there would be no writing to the USB key if I would disable updates.
The nvOC is pretty stable even now, but I think that disabling all updates would help with the stability of the system.
Of course I would also periodically update USB key with the whole image of nvOC, but only every month or so, when you publish the new version of stable nvOC.
fullzero, you mentioned active cooling for 1080tis with 133 CFM 120mm fans.
Im interested in this solution, but Im not sure if I will be able to put it together. Can you please share some details.
Do you remove original fans and cover so that only the cooler fins remain?
How do you mount fans?
How do you power the fans?
Im interested in this solution, but Im not sure if I will be able to put it together. Can you please share some details.
Do you remove original fans and cover so that only the cooler fins remain?
How do you mount fans?
How do you power the fans?
I leave the shroud (GPU fans and casing) on; although if you were super exacting it would probably be best to remove these; not worth the time IMO.
The way my open frames are (see one of the demo videos); I just zip tie them to the front (blowing into the 1080tis) and power them via a 3x fan to molex adapter / then molex to whatever is available with the rigs PSU. I get fans from Hawkfish007 https://bitcointalk.org/index.php?action=profile;u=352509; he includes the 3x fan to molex adapters with the fans.
I couldn't see this setup on the demo videos; I watched v0014demo, v0018demo and v0019demo. I think there are no 1080tis in these videos, but I think I get the picture.
Did anybody had to replace a failed original fan on a 1080ti?
I think a good way would be to remove all fans and their casing and somehow mount a high pressure fan (Like Corsair SP120 High Static Pressure 2350 U/min).
Some original fans on 1080tis are of low quality and will probably fail soon.
Does anybody have some experience with these type of modifications?
fullzero, you mentioned active cooling for 1080tis with 133 CFM 120mm fans.
Im interested in this solution, but Im not sure if I will be able to put it together. Can you please share some details.
Do you remove original fans and cover so that only the cooler fins remain?
How do you mount fans?
How do you power the fans?
Im interested in this solution, but Im not sure if I will be able to put it together. Can you please share some details.
Do you remove original fans and cover so that only the cooler fins remain?
How do you mount fans?
How do you power the fans?
What could cause my OS/miner to freeze? I got it running but can't stay up for long. I'm sure my OC settings are fine because I started very low.
It looks like there are lots of possible reasons for a freeze:1) overclock,
2) bad riser,
3) adapter cable to the riser,
4) power cable to the riser,
5) bad GPU,
6) PCIe slots on the motherboard are touching
I am not sure how to diagnose which one ...
I have Asrock H110 Pro and the neighbour risers are touching among themselves. I am not sure if this is a problem? The board is working without restart for a couple of days, but not allways.