 Show Posts
|
|
Pages: [1] 2 »
|
|
Does this run well on win10 pro?
|
|
|
|
 TRC has been added to blockmunch.club!- Web Address: BlockMunch.club
- Current Fee: 0.25%
Example Config: -a sha256 -o stratum+tcp://blockmunch.club:3333 -u 1DVq1c5TLnvZXZWNGM8L4mtrYJXzmcrsw4 -p c=TRC https://blockmunch.club/explorer/TRC Join the Block Munch Club! Pool is on the latest wallet version available!Pool is now up and ready to mine! I don't see any hashrate on any of the pools including this new one. Is it due to waiting for the fork to complete? Or is there another reason no one is mining? |
|
|
|
Here's a process that worked for me, with some brainstorming, my business partner tested this out successfully through trial and error:
So if your GPUs are getting code 43 - and you don't have the option to roll back the drivers follow the steps below from 1 to 8.
If you do have the option to roll back the drivers, and the error disappears, skip to step 5 in order to block all future AMD device driver updates.
1- Reboot in safe mode and run DDU, uninstall drivers without restarting option selected.
2- Disable GPUs under device manager, then restart - alternatively, keep ethernet disconnected so it does not update GPUs - or if you're paranoid, do both and that should stop all attempts to install device drivers.
3- Install crimson 16.9.2 or your choice of driver version. This one is working well for me after other members posted about it, gave it a shot.
4- Don't restart after installing drivers, and make sure the box to automatically update drivers is unchecked.
5- Launch CMD prompt box as administrator - type gpedit and press enter
6- Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions >prevent installation of devices that match any of these device id's
7 - get hardware device id for gpu from device manager > device properties > details. (I believe it's the same for all similar cards) add it under enabled list, save, reboot, start mining again.
---
I also ran into a problem where one of my flashed bios cards would crash on driver install since this update, so if you keep having problems, maybe start testing with process of elimination.
Thank you for the step by step directions... I had been troubleshooting all day long and part of today but to no avail. This worked perfectly. You're welcome, it was a long and sleepless night for me as well, however I should note that I no longer recommend skipping step 1 to 4 if you can roll back the driver - it seems it has a more dependable result if DDU is always used to uninstall the drivers and help block future updates. I crossed it out of my original post. |
|
|
|
|
Here's a process that worked for me, with some brainstorming, my business partner tested this out successfully through trial and error:
So if your GPUs are getting code 43 - and you don't have the option to roll back the drivers follow the steps below from 1 to 8.
If you do have the option to roll back the drivers, and the error disappears, skip to step 5 in order to block all future AMD device driver updates. This doesn't always work. From my testing, it is best to always remove the drivers using DDU, and installing the previous ones manually.
1- Reboot in safe mode and run DDU, uninstall drivers without restarting option selected.
2- Disable GPUs under device manager, then restart - alternatively, keep ethernet disconnected so it does not update GPUs - or if you're paranoid, do both and that should stop all attempts to install device drivers.
3- Install crimson 16.9.2 or your choice of driver version. This one is working well for me after other members posted about it, gave it a shot.
4- Don't restart after installing drivers, and make sure the box to automatically update drivers is unchecked.
5- Launch CMD prompt box as administrator - type gpedit and press enter
6- Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions >prevent installation of devices that match any of these device id's
7 - get hardware device id for gpu from device manager > device properties > details. (I believe it's the same for all similar cards) add it under enabled list, save, reboot, start mining again.
---
I also ran into a problem where one of my flashed bios cards would crash on driver install since this update, so if you keep having problems, maybe start testing with process of elimination.
|
|
|
|
i think i will do a fresh win 10 install anyway and install 16.9.2 driver and disable all kinds of updates possible...slowly thinking about installing simplemining OS for the rx series...
Fresh install didn't do it for me either, tried on two rigs.. |
|
|
|
|
Pixel patcher worked for my rig only running 2 GPUs, I tried on two of my 6x GPU rigs, and windows would be unable to restart afterwards, repair fails, I would have to boot in safe mode, uninstall display drivers, and back to square one.
I stayed up all night, only managed to get half my hashrate up. Need some sleep, I think I might say goodbye to windows.
I even tried switching my dual bios to the unmodded ones and same code 43 stuck around
|
|
|
|
|
I spoke too soon,
I tried cleaning with DDU, installing older version, but the error code does not go away for all the cards. After running the patcher, it is often causing the rigs to have start up errors.
I have to start in safemode, uninstall display drivers again, and reinstall, but I get faced with code 43, even when using an older amd installer.
|
|
|
|
|
@Walrusbonzo - I just spent all night trying to troubleshoot, this patch seemed to have done the trick on the first rig - thank you!
Only reason I chose win10 was for good hashrate, dual mining for amd specifically.. hate the updates as much as the next guy.
|
|
|
|
|
Same thing happened to me and someone else I know. Win10 update broke something really badly.
If you're lucky, you will have option to roll back to previous driver in device manage, I was able to fix 2 rigs this way. But some others it did not fix all cards, and even after reinstalling windows, or reseting windows, both scenarios have not solved the issue.
|
|
|
|
|
@philipma1957
I'm looking forward to seeing whats comes out of lightningasic, but so far I noticed the 1-5 month waiting time time they gave you for barebones. I guess I could still try 6x GPU server rigs with 1060 cards as well if power consumption isn't too high.
|
|
|
|
|
Any experience with 1060 Zotac or evga mini single fan? Contemplating between that or evga gaming dual fan. Seems like the obvious choice would be a dual fan card unless blower style but maybe they use less power.
|
|
|
|
|
Thanks @minerx117 - some really cool stuff here. Once I build my first nvidia rigs, I will be testing this out and supporting. Just discovering these multi-pools, these can end up being critical to remaining as profitable as possible in case of bad times
|
|
|
|
|
I'm hoping it gets delayed, but if not, I won't panic and sell my GPUs right away. Test out other coins and see what works, trade to BTC.
|
|
|
|
|
Hi, this service is something I am looking for, specifically for the Portugal channels, can you send me a list?
Thanks
|
|
|
|
|
The 4 Mh/s seems to be a common occurrence, I've read others say that you simply connect a screen to fix the issue, but often a machine reboot or even just restarting the miner can be enough to fix it.
I'm also seeing some cards drop hash like that, I will be spending more time on individually testing them, and running different clock speeds instead of syncing them all.
|
|
|
|
|
@ecohash @Marvell1 @yslyung
Regarding Gigabyte 470 4GB G1's just wanted to share some info on my experience - I had a similar issue with heat rising around 75-80c. After testing a few different settings and setups, I realized the issue in my case stemmed from having the cards in a case.
If the card was blowing up hot air against a card just under it, it would cause the top card to get hot, while the bottom card kept normal temps. Open air solved the heat issue and they run at around 62c now,
|
|
|
|
|
@xxcsu @evakka
Thanks guys I'm going to try all of that as soon as I have the time. Priority is to run my business, and almost all my free time is going into mining. I currently have 4 GPUs running on each system, stable for more than 24h, and considering this may take more than a few hours, I'll start testing when I my other boards arrive to minimize downtime on mining.
I did already test with no GPUs or risers connected, and I did test 3 different power outlets since I had to move stuff around to start with.
I never though of removing SSD drive will certainly try that. I also did not try to boot with 1 dimm, because I usually only do that when I get crashes, no boot or to run mem tests.
Will do all of that + try a different PSU until I find something that works.
@evakka
When you suggest to use simplemining.net - are you suggesting that it will read 7 GPUs with no BIOS settings changes?
|
|
|
|
|
@evakka + @xxcsu
Ok so they are two separate systems with identical components, I will try to add pictures next time. Running Win10 pro 64 - no crashes or blue screens. Sometimes when I would first launch multi-gpu, windows would start installing display drivers and one of those might crash but system is stable.
@xxcsu - I know they are not plug and play, which is why I need the BIOS to simply work, it does not matter what I have or don't have connected, the BIOS acts the same with just CPU and SSD attached, on two identical systems.. so I think there might be an answer to this, question is can I find it.
For both MSI M5 refurb motherboards, I have identical but separate components, running simultaneously - NO parts have been mixed.
Kingston DDR4 2x4gb 2133 x2
Corsair 120gb SSD x2
Pentium G4400 CPU x2
EVGA 1300 G2 x2
GPUs in #1: 3x RX 470 Nitro+ and 1x RX 470 Ref
GPUs in #2: 4x RX470 Nitro+
Using quality risers from Hawkfish007 and did the basic virtual memory increase tweak.
Again, I did not use the same PSU on both ever, did not mix any cables, power strips, they have been built and connected separately, even running in different rooms and circuits.
|
|
|
|
|
