Author

Topic: Having two issues... am new, cant ask technical forum. (Read 923 times)

hero member
Activity: 767
Merit: 500
Have you set up a separate worker account for each of the cards. If you don't they will be getting duplicate shares and you will see rejected shares.

Will
member
Activity: 69
Merit: 10
For the first issue, what PSU do you have? Are they crossfired? Sounds like they're not getting enough power or overheating.

Second issue I don't quite understand. Are you solomining on it or poolmining? If the latter you don't need the bitcoin server running. If it's the former then I believe 3.23 has issues with it, use 3.21 instead.
full member
Activity: 168
Merit: 100
Ugh, I feel terrible about doing this, but I haven't seen any rules against it... so... well... bump?

I really wish this could get scooted to the appropriate forum.
full member
Activity: 168
Merit: 100
Ok, so I've been participating in Bitcoin mining for almost a month now and it's been going smoothly on my desktop rig (NVidia Card).

I had a new rig come in recently (Windows 7 x64, Radeon 5830 x2 OC to 900Mhz, Phenom II dual) so I decided to run a server on my desktop and have my new rig connect to it.
All seems to be going well - the hash speeds are as expected, temp is fine, no connection issues - but after a few days of running I noticed that guiminer reported that of the ~5k shares that each video card had submitted, only about 200 from each were accepted.  I reset the numbers and only ran one instance of a miner (just using one card) and after 500+ shares, all of them were accepted.
TLDR (issue #1): Using two video cards on one rig to connect to my desktop rejects over 80% of the shares from each card.


The second issue is setting up a Bitcoin server on my new rig so that it can connect to itself instead of across the network.  My older desktop is running Bitcoin 3.21 and the server mode works fine.  My new rig running 3.23 gives me "Connection error" warnings in guiminer.  Worse still is that as soon as a client tries to connect to the 3.23 server, the bitcoin.exe process spikes to full load and no amount of waiting fixes it.
TLDR (issue #2): New rig runs Bitcoin 3.21 as a server fine, but on client connect with Bitcoin 3.23, process CPU usage maxes out and goes unresponsive.


Any advice or help is appreciated.  I'm a fairly technical person, so feel free to get nitty gritty.
Also, I apologize for gluing two issues in one thread (and in the Newbie board at that!) but I don't have access to the appropriate forum.

Thanks in advance!
Jump to: