Copy your wallet.dat to a safe place, then delete %AppData%\Bitcoin. If you still get crashes, do that again and uninstall/reinstall.
gethashespersec returns 0 because bitcoind is not hashing using the CPU. It doesn't know the hash rate of connected clients.
Thanks for that! I have backed up my wallet.dat already, and I simply installed 0.3.21 over 0.3.20 I will try re-installing and see if that fixes anything? So far so good though with bitcoind.exe ~24 hours of no failures. I think it might have something to do with the GUI.
|
|
|
Perhaps I am not explaining myself properly.
You know when you are mining and using bitcoin.exe (or linux equivalent) as your server... it will sometimes say "Hey! You have generated 50 coins! But you have to wait 120 transactions before they 'Mature' so you can use them!"
All I am wondering is if that is shown in the bitcoind.exe listtransactions command? Or are generated blocks only shown after they have matured?
|
|
|
You don't need the -server argument when using bitcoind, as that is all bitcoind does. When you use server with bitcoin.exe, it enables JSON-RPC, which allows you to make all the same API calls while also using the GUI.
I don't understand why you executed bitcoind over and over and over again. Running it once starts the daemon which runs in the background.
My apologies, please allow me to explain! I begain running it more than once because that command line became that way over the course of a few hours. Forgive me for not wiping it clean before I posted the screenshot There is only one copy of bitcoind.exe running on my computer - all I wanted to know is if it is indeed working as a server - and if it does so by default, then I guess you answered my question BitterTea, +1 thanks!
|
|
|
I know when bitcoin.exe (not bitcoin d.exe) is running, it doesn't count your un-verified generated blocks until 120 blocks have passed, but it shows that you have generated something. Would bitcoin d.exe show me un-verified blocks by typing bitcoind listtransactions and simply read ~17 (or less than 120) verifications? Or will I have to wait for the entire 120 blocks to see what I've got coming to me? I would just run bitcoin.exe if it wasn't crashing on me all the time!
|
|
|
X needs to be running, but in most cases a monitor does not need to be plugged into the graphics card.
I was wondering this same thing... So you can't run your miners from simply a command line state? You need to be running some sort of desktop?
|
|
|
Open your task mangler and kill any extra running copies of bitcoind. If that fails, reboot your computer.
Whoa whoa whoa, wait a sec!?! I only have one copy of bitcoind.exe running, I am just saying that is what my command line looks like. No error codes or messages whatsoever after 12 hours now... just want some clarification that it's even working properly!?
|
|
|
So I have been having some problems with my bitcoin.exe suddenly.I have a few miners setup running ubuntu 11.04 and I was running the bitcoin server off of my windows 7 64 bit machine (quite smoothly for almost a week straight) until earlier today when I started receiving error messages related to bitcoin.exe My question is, if I run bitcoind.exe -server and connect my miners as usualy, will everything still work as expected? Am I wasting my time running bitcoind.exe for mining? It has looked like this for the past few hours since I started running it: My miners are showing hashes per second and not any "RPC Cannot connect" values... I just want some confirmation that they are indeed working?! Can you give me some reassurance, bitcoiners?!
|
|
|
Not to be sexist or anything, but of all the people I have told about bitcoin only guys have thought it was cool. I might as well be talking about a FPS video game. Do we have any female traders here?
My girlfriend is actually quite interested in it. She's not tech savvy at all either, but when I mentioned that it is "increasing in value", she wanted to learn more
|
|
|
Don't OC, if the manufacturers could squeeze out a greater clock rate without risking a high rate of failure they would have.
Not entirely true. The manufacturers didn't make these cards for hashing bitcoins, they made them for playing video games. A bit of tweaking to adjust them for bitcoins is almost common sense!
|
|
|
Hello, So I've installed my ATI HD 5870, installed catalyst and the SDK. Its shared on my mobo with an internal graphic card ATI 3000HD and i'm using the 3000 for my monitor while wanting to use 5870 for mining headless. I run the poclbm script and get the following: No device specified or device not found, use -d to specify one of the following
AMD Phenom(tm) II X4 955 Processor"
Mind you that when I right click on the system tray and see the catalyst context menu, it shows both my cards. When I go to the info though catalyst shows the 5870 as "disabled" while window's device manager shows it not disabled. Suggestions? Ideas? Windows 7, 64bit. Thanks much! -schone Try re-starting, and plugging a monitor cable into both of the outlets.
|
|
|
Yes, you need to plug in dummy connectors to all outlets when running a windows system. Don't ask me why.
All I know is that this is not the case when it comes to Ubuntu.
+1 for Linux!
|
|
|
If you are running it for mining, you can go into the daemon folder and run bitcoind.exe - just be sure to copy your libeay32.dll file from your bitcoin folder to the daemon folder.
|
|
|
Well, I just want to use it as a way to pay off the difrence between my current grafics card and a 5770. It would not take that long to get that many bitcoins if running 24/7.
That's the spirit.
|
|
|
A blue screen... I assume you're running windows?! Try ubuntu, never witnessed that on linux.
|
|
|
I too am interested in this.
If I take my wallet.dat file from my windows computer and copy it over to my linux laptop... will I have dual access to the exact same account?
What would happen when I send money from one computer? Would the other one be notified?
|
|
|
Annnnnnnnnd it just did it again. Problem signature: Problem Event Name: APPCRASH Application Name: bitcoin.exe Application Version: 0.0.0.0 Application Timestamp: 4db847a6 Fault Module Name: bitcoin.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4db847a6 Exception Code: 40000015 Exception Offset: 004988a5 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 5059 Additional Information 2: 50594bacf91ee35dd61f657f5dc0cc38 Additional Information 3: e6ca Additional Information 4: e6cac0980bcc580bd64be67830b7f436 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Going to try re-starting now and see if that fixes anything. Edit: NOPE :S It seems my computer has suddenly developed an affliction with bitcoin.exe I am running bitcoind.exe -server right now, but how do I know that it is actually working?! I can see that my miners are hashing, but when I enter bitcoind gethashespersec I see 0.. Is it going to spit out a message or something once I generate a block? (bitcoind.exe?)
|
|
|
It's very, very, very hard to get a lot of people to collude without cheating and with no enforcement.
"Oh sure, I'll only accept transactions with a fee of 1 BTC". Then accept anything over a bitcent.
Exactly. There is no honor among thieves.
|
|
|
I'm generating around 50/day, but I'm selling off every 200-300 to ensure that my hardware is all paid off rather than holding it for speculation. Depending on difficulty jumps, all my 5 rigs should be paid for in about 5 weeks.
I'm still unsure about what the difficulty change will be AFTER this one due to the OCN thread causing a big spike in computing power during this difficulty, which is already starting to die down. The damage has already been done by it regarding the next jump, but I have a feeling the following jump will be minor (< 5%), or even a drop.
What if the difficulty goes through the roof, and you have sold all of your bitcoins to pay for your rig? Then you'll just be left with a bunch of video cards and nobody to sell them to I suggest you hold on to them for at least a few more months.
|
|
|
I upgraded to the latest bitcoin version 0.3.21 - run the bitcoin.exe -server command, and this time bitcoin was only up and running for about 30 minutes before I saw the exact same error message again (attached). And then the following (similar) code was produced in the "Details" drop down box on the next window: Problem signature: Problem Event Name: APPCRASH Application Name: bitcoin.exe Application Version: 0.0.0.0 Application Timestamp: 4db847a6 Fault Module Name: bitcoin.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4db847a6 Exception Code: 40000015 Exception Offset: 004988a5 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 5059 Additional Information 2: 50594bacf91ee35dd61f657f5dc0cc38 Additional Information 3: e6ca Additional Information 4: e6cac0980bcc580bd64be67830b7f436
Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt My Specifications: Windows 7 Ultimate 32 bit 4GB Ram 3.0GHz CPU There are also 4 mining cards connecting to it 24/7... and when I re-start bitcoin.exe -server manually, POCLBM still reads "problem connecting to RPC client" on every card... I am forced to re-start bitcoin.exe -server while the miners are not running, and then start the miners. My bitcoin server had been running flawlessly for about 3-4 days straight before this error occured. I have not installed or removed any programs in the last week or two either. Any ideas?
|
|
|
|