Post
Topic
Board Mining (Altcoins)
Added 2 RX580 GPUS to a 6 RX 580 RIG, now Windows menus open slow if at all.
by
miner_in_bkk
on 08/02/2018, 04:17:32 UTC
Hi Guys,

Have a frustrating problem, which I think I understand the cause of, but cant figure out how to fix it.

Biostar 250 BTC Pro (12 GPU slots)
6 MSI RX 580 8gb
4gb Ram 2133
Celeron 3900
Claymore 10.5
Virtual Memory setting 16384
Windows 10 x64 Pro
AMD Blockchain Driver

I have just received another 6 Gigabyte RX 580 8gb Gaming GPU’s and tried to add 2 GPU’s to the 6 GPU’s and see how problematic this would be before trying to add the full amount of the 6 GPU’s to the one rig.

Order of events.

1. Device Manager saw the 8 – Great.
2. Windows installed automatically the Block Chain Driver. – PATCHED - REBOOT
3. Claymore saw the 8 – Great.
4. Claymore got random GPU “dag creation” errors. - FIXED the error, as I saw a post stating to increase Virtual Memory to 64000. – REBOOT
5. NOTICED THE PROBLEM. Windows takes 15 seconds to open any folder / AMD Radeaon App / Windows Setting / Start Menu wont open. - REBOOT
6. Problem still there. Open Claymore and get 20-22 MHS on the 2 Cards (30.8 on the other 6). Remembered to modd the GPU’s with at least the timing straps @ 1500– did it. But cant flash it – Cant open the CMD with administration rights due to not having access via start menu.
7. Stopped my other rig, and removed a 4gb stick of 2133 ram to add into this rig.
8. Display Menu is now working fine. Flash the Bios. Patcher says nothing to patch. – Reboot.
9. Claymore now getting 30.5-30.8 Mhs with all 8. – YAHOO.
10. Leave it for 30 mins to watch the Miner, now the PROBLEM has come back. All menus / setting menu’s take FOREVER to open up. Could be 2 minutes with several attempts.
11. Tried changing the Virtual Memory but no setting with reboot solves this problem.
12. Removed the two GPU’s, took out the 2nd 4gb RAM and took the Virtual Memory back to 16384 - Rebooted and the problem has now gone.

Allot of miners have success with 10-12 GPU rigs with 4gb. And the problem exists if I have 8gb in the rig, then maybe its not the physical RAM, even though the problem momentarily went away when i added the additional 4gb.

Any ideas ?