Possibly increase your hash rate?
-
So i had to rebuild one of my mining rigs today and ran into some issues with the hashing speeds.
For those of you that are unaware, i have 5 identical (ish) rigs all running 4* 7970s. All of them hash at a steady 750-760 per card but usually closer to a constant 755. After the rebuild i only got around 600KHs and the hash rate was bouncing all over the place (600-725). I post this because i have seen a number of you posting stats for various cards stating “between 600 - 650” and the like. I feel it should be MUCH more consistent. Maybe you think you’ve maxed your cards but in fact a re-install of the drivers may get you a few more free shares…
How i built my rigs (software wise)
1. Clean install of Windows 7 Pro (SP1)
2. install AMD chipset drivers using “CUSTOM” and excluded the graphics drivers though.
3. Install AMD graphics drivers (13.1) (ye olde faithful)
4. Install network drivers
5. Patch windows with 100 is updates.
6. Install TightVNC (I run them all headless with no dummy plugs)
7. Install cgMiner 3.1.1
8. Run cgMiner with my tuned settings
9. Watch my hashrate plummet! :oKnowing full well this worked fine an hour ago, i started to poke it with a stick.
1. Install 13.4 drivers (no joy)
2. Uninstall all drivers using this http://sites.amd.com/us/game/downloads/Pages/catalyst-uninstall-utility.aspx
3. Re-install 13.1 drivers (no joy)
4. Uninstall all drivers again
5. Re-install latest chipset drivers but this time including the graphics drivers (ie full install)
6. Re-install 13.1 graphics drivers.
7. ran cgMiner and BINGO steady 755 on all cards.I’ll update this post with more conclusive info soon but for now, if you have erratic hashrates, may be worth doing a complete removal of all the drivers, fully patch windows, install the CHIPSET drivers in full then Install the 13.1 graphics drivers.
-
I did somewhat the same to a system last night, CGminer 3.2.0 refused to work until I installed all windows updates and a .net 4 framework (2.11.3 worked while 3.2.0 didn’t) if that helps anyone with a fresh windows install also wondering like I did on Windows 7 Ultimate.
I seem to get less KH with the 13.4 driver than I did with 13.1. so this seems to hold up.
Good work and thanks for sharing.
-
It’s known that 13.4 drivers are lame. Keep with 12.10 to 13.1 and 2.7 SDK.
-
Good thing about mining rigs is I will just re-ghost the base image in 5 min and re-install all the updates connected to the internet.
-
[quote name=“ghostlander” post=“10748” timestamp=“1370634483”]
It’s known that 13.4 drivers are lame. Keep with 12.10 to 13.1 and 2.7 SDK.
[/quote]Why sdk 2.7 when hes using 7xxx series cards?
Its my understanding that 2.8 for 7xxx and 2.6 for previouse gen cards. -
Actually, if you installed latest driver 13.4, system32 and syswow64 will appear 4 files for each folder.
system32(amdocl_as64.exe, amdocl_ld64.exe, amdocl64.dll, OpenCL.dll)
syswow64(amdocl_as32.exe, amdocl_ld32.exe, amdocl.dll, OpenCL.dll)step.1 uninstall all amd software
step.2 delete 8 files
step.3 install back 13.1 full package
step.4 Install skd
step.5 Restart system
job doneThese are the files what cause the conflicts hence why you get incorrect mining speeds due to files left over. Even deleting all files the installers are still leaving these over from uninstall and you need to manually remove them and start fresh and go back to 13.1 or 12.10 and skd 2.8 for 7 series cards and or 2.6 for 50s and 60s gen cards
This is also a problem for Windows 8 as well and will also fix that mining problem. However Windows 8 and mining due to not been able to disable a bunch of stuff and embedded windows desktop session manager removed and added something new like it you cant disable it in windows 8 and that causes one of the biggest problems in 8 for mining.
So this is a fix for both Windows 7 and 8 :)
-
I’m mining perfectly fine on Windows 8 Pro 64bit, never had any problems myself.
I will get my friend to try this fix. Thanks.
-
I have had no issues on Win 8 x64 either
-
Hm! So
[quote name=“crazyearner” post=“10913” timestamp=“1370674873”]
Actually, if you installed latest driver 13.4, system32 and syswow64 will appear 4 files for each folder.system32(amdocl_as64.exe, amdocl_ld64.exe, amdocl64.dll, OpenCL.dll)
syswow64(amdocl_as32.exe, amdocl_ld32.exe, amdocl.dll, OpenCL.dll)step.1 uninstall all amd software
step.2 delete 8 files
step.3 install back 13.1 full package
step.4 Install skd
step.5 Restart system
job doneThese are the files what cause the conflicts hence why you get incorrect mining speeds due to files left over. Even deleting all files the installers are still leaving these over from uninstall and you need to manually remove them and start fresh and go back to 13.1 or 12.10 and skd 2.8 for 7 series cards and or 2.6 for 50s and 60s gen cards
This is also a problem for Windows 8 as well and will also fix that mining problem. However Windows 8 and mining due to not been able to disable a bunch of stuff and embedded windows desktop session manager removed and added something new like it you cant disable it in windows 8 and that causes one of the biggest problems in 8 for mining.
So this is a fix for both Windows 7 and 8 :)
[/quote]Followed this along with the uninstall util described in the OP and magic. It works!
Only weird stuff to mention:
I had to delete the files in system32 and syswow64 via command line as, despite it showing otherwise, i couldnt do it via the windows gui.
I did not have all the files described above, which is curious as I had 13.4 installed and 2.8 sdk installed also.I only had to install the 13.1 drivers, no sdk and it worked. This is all on windows 8 pro x64.
Thanks Crazyearner and Nutnut, i no longer have to switch into linux to mine.
-
Great Stuff!
Once i’ve cleared my shed out, cut the grass etc (ahhh married life…) i’ll cleanup/update the OP etc.
-
Just a heads up for anyone using Windows 8 and about to use the AMD uninstall utility - it may break your Win8. It broke mine. I had no idea why I could not access shares any more, and upon checking, there are numerous problems associated with using the Uninstall Utility and Win8.
So beware if you are going to try that route, make sure you have an image to roll back out, or are sure you know what the fix is. I had to feck with the registry to allow access to my shares once again, but after reading more on it, it seems to break a lot more.
Not sure if there are issues with Win7 though.
I also found that the 13.x drivers were causing problems with my cgminer. It would sometimes just refuse to start properly, giving me a hash of ab out 20-20khash. And everything would lag. No processes running that shouldn’t have been, and it seemed random. A reboot would fix it.
It all seemed ok after I went back to 12, but after writing a frontend for cgminer to access the API stats, I noticed it still happens randomly…
-
[quote name=“gness” post=“11009” timestamp=“1370696842”]
Hm! So
[quote author=crazyearner link=topic=1342.msg10913#msg10913 date=1370674873]
Actually, if you installed latest driver 13.4, system32 and syswow64 will appear 4 files for each folder.system32(amdocl_as64.exe, amdocl_ld64.exe, amdocl64.dll, OpenCL.dll)
syswow64(amdocl_as32.exe, amdocl_ld32.exe, amdocl.dll, OpenCL.dll)step.1 uninstall all amd software
step.2 delete 8 files
step.3 install back 13.1 full package
step.4 Install skd
step.5 Restart system
job doneThese are the files what cause the conflicts hence why you get incorrect mining speeds due to files left over. Even deleting all files the installers are still leaving these over from uninstall and you need to manually remove them and start fresh and go back to 13.1 or 12.10 and skd 2.8 for 7 series cards and or 2.6 for 50s and 60s gen cards
This is also a problem for Windows 8 as well and will also fix that mining problem. However Windows 8 and mining due to not been able to disable a bunch of stuff and embedded windows desktop session manager removed and added something new like it you cant disable it in windows 8 and that causes one of the biggest problems in 8 for mining.
So this is a fix for both Windows 7 and 8 :)
[/quote]Followed this along with the uninstall util described in the OP and magic. It works!
Only weird stuff to mention:
I had to delete the files in system32 and syswow64 via command line as, despite it showing otherwise, i couldnt do it via the windows gui.
I did not have all the files described above, which is curious as I had 13.4 installed and 2.8 sdk installed also.I only had to install the 13.1 drivers, no sdk and it worked. This is all on windows 8 pro x64.
Thanks Crazyearner and Nutnut, i no longer have to switch into linux to mine.
[/quote]No problem glad it helped you theirs another thing for future if cant delete them make sure theirs no amd processes running or can just go in safemode but as you did through cmd line sounds like your permissions where broken or didnt have permission to do but happy you got fixed :)
-
I have also found the best results with 13.1. Wish i found better writes ups after I tried 13.4. I ended up reinstalling windows. wtf
-
Its not very possible.
-
might seem like a dumb question but where can I download the 13.1 drivers?
-
Hi Bob,
Here for 32 bit:
[url=http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista32.aspx]http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista32.aspx[/url]and here for 64 bit:
[url=http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista64.aspx]http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista64.aspx[/url]Note the page says ‘Vista’, but the drivers are for Vista, Windows 7 and Windows 8.
TN
-
Thanks for the download link! Yep, followed first post, 2nd part and went from 720k stable to 744k stable.