marks1976 (OP)
|
|
May 18, 2012, 08:56:05 PM |
|
Upon upgrading to bitcoin-qt 0.6.2 I am receiving a Visual C++ runtime error. I am using windows 7. I tried reinstall and still no luck. I deleted all files except wallet.dat in the folder. Once I started bitcoin client again gets started and fails syncing the blockchain at block#168514. This problem is something new since it was running up until yesterday. Prior to that no problem.
|
|
|
|
|
|
|
|
|
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
gmaxwell
Moderator
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
May 18, 2012, 10:17:11 PM |
|
fails syncing the blockchain at block#168514.
What do you mean by "fails"? It's not unusual for it to stop and wait until the next block on the network is found during syncup. The reason you were unable to start until you deleted your database is probably because your software was not cleanly shutdown before upgrading.
|
|
|
|
marks1976 (OP)
|
|
May 18, 2012, 10:20:39 PM |
|
Fails due to the fact of the C++ Runtime error. 168514 is not the most recent block. The bitcoin client only gets to block 168514 before the runtime error. It updates only until about 80 days ago. Block chain loads fine until that point.
|
|
|
|
gmaxwell
Moderator
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
May 18, 2012, 11:23:27 PM |
|
Fails due to the fact of the C++ Runtime error. 168514 is not the most recent block. The bitcoin client only gets to block 168514 before the runtime error. It updates only until about 80 days ago. Block chain loads fine until that point.
Did you really delete _all_ the files except the wallet.dat, including the database directory and _db.000 files?
|
|
|
|
marks1976 (OP)
|
|
May 19, 2012, 12:11:13 AM |
|
Fails due to the fact of the C++ Runtime error. 168514 is not the most recent block. The bitcoin client only gets to block 168514 before the runtime error. It updates only until about 80 days ago. Block chain loads fine until that point.
Did you really delete _all_ the files except the wallet.dat, including the database directory and _db.000 files? I removed the files yes I have them still backed up. I tried clean install of bitcoin 0.6.2 and loads everything back to the same spot. I can put those files back but was giving me the error when the files were there.
|
|
|
|
gmaxwell
Moderator
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
May 19, 2012, 12:43:06 AM |
|
I removed the files yes I have them still backed up. I tried clean install of bitcoin 0.6.2 and loads everything back to the same spot. I can put those files back but was giving me the error when the files were there.
Do you have a bitcoin.conf or start with any special arguments like telling it to connect to a single particular node or use a proxy? How many connections do you have when the node is running? Are you running low on disk space?
|
|
|
|
marks1976 (OP)
|
|
May 19, 2012, 12:48:23 AM |
|
I removed the files yes I have them still backed up. I tried clean install of bitcoin 0.6.2 and loads everything back to the same spot. I can put those files back but was giving me the error when the files were there.
Do you have a bitcoin.conf or start with any special arguments like telling it to connect to a single particular node or use a proxy? How many connections do you have when the node is running? Are you running low on disk space? Windows 7 machinewith no special arguments. I start bitcoin-qt and says it loads all info. Then when it loads it makes 12 connections last time and when it tries to get the rest of block info C++ Runtime error.
|
|
|
|
gmaxwell
Moderator
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
May 19, 2012, 12:53:55 AM |
|
I removed the files yes I have them still backed up. I tried clean install of bitcoin 0.6.2 and loads everything back to the same spot. I can put those files back but was giving me the error when the files were there.
Do you have a bitcoin.conf or start with any special arguments like telling it to connect to a single particular node or use a proxy? How many connections do you have when the node is running? Are you running low on disk space? Windows 7 machinewith no special arguments. I start bitcoin-qt and says it loads all info. Then when it loads it makes 12 connections last time and when it tries to get the rest of block info C++ Runtime error. Can you paste the text of the runtime error along with the last dozen or so lines from your debug.log file?
|
|
|
|
marks1976 (OP)
|
|
May 19, 2012, 02:08:50 AM |
|
Microsoft Visual C++ Runtime Library.
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more info.
SetBestChain: new best=000000000000037a05e0 height=168683 work=247872594564066802392 ProcessBlock: ACCEPTED received block 00000000000005e856fe SetBestChain: new best=00000000000005e856fe height=168684 work=247878505827495506778 ProcessBlock: ACCEPTED received block 00000000000002fbfe20 SetBestChain: new best=00000000000002fbfe20 height=168685 work=247884417090924211164 ProcessBlock: ACCEPTED received block 00000000000009885595 SetBestChain: new best=00000000000009885595 height=168686 work=247890328354352915550 ProcessBlock: ACCEPTED received block 000000000000031e08a4 SetBestChain: new best=000000000000031e08a4 height=168687 work=247896239617781619936 ProcessBlock: ACCEPTED received block 00000000000008b17bd1 SetBestChain: new best=00000000000008b17bd1 height=168688 work=247902150881210324322 ProcessBlock: ACCEPTED received block 0000000000000494ddd4 SetBestChain: new best=0000000000000494ddd4 height=168689 work=247908062144639028708 ProcessBlock: ACCEPTED received block 0000000000000bd35884 SetBestChain: new best=0000000000000bd35884 height=168690 work=247913973408067733094 ProcessBlock: ACCEPTED received block 00000000000009c94c88 SetBestChain: new best=00000000000009c94c88 height=168691 work=247919884671496437480 ProcessBlock: ACCEPTED received block 0000000000000552dcf9 SetBestChain: new best=0000000000000552dcf9 height=168692 work=247925795934925141866 ProcessBlock: ACCEPTED received block 000000000000030d3dc5 SetBestChain: new best=000000000000030d3dc5 height=168693 work=247931707198353846252 ProcessBlock: ACCEPTED received block 000000000000046a1cea SetBestChain: new best=000000000000046a1cea height=168694 work=247937618461782550638 ProcessBlock: ACCEPTED received block 0000000000000aa72f3f SetBestChain: new best=0000000000000aa72f3f height=168695 work=247943529725211255024 ProcessBlock: ACCEPTED received block 000000000000042fada4 SetBestChain: new best=000000000000042fada4 height=168696 work=247949440988639959410 ProcessBlock: ACCEPTED received block 0000000000000110f179
************************ EXCEPTION: 22DbRunRecoveryException DbEnv::txn_checkpoint: DB_RUNRECOVERY: Fatal error, run database recovery C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe in ThreadDumpAddress()
|
|
|
|
gmaxwell
Moderator
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
May 19, 2012, 03:09:38 AM |
|
************************ EXCEPTION: 22DbRunRecoveryException DbEnv::txn_checkpoint: DB_RUNRECOVERY: Fatal error, run database recovery C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe in ThreadDumpAddress()
When you deleted everything did you also delete addr.dat? If not then I suspect you have a failing disk.
|
|
|
|
marks1976 (OP)
|
|
May 19, 2012, 06:16:28 AM |
|
Yes I did delete addr.dat. I tried to restore it with no luck.
|
|
|
|
Schleicher
|
|
May 19, 2012, 04:00:44 PM |
|
Things you could try: see if the daemon version is crashing too run a memory test run a hard disk test
|
|
|
|
someguy123
|
|
May 19, 2012, 04:29:16 PM |
|
Things you could try: see if the daemon version is crashing too run a memory test run a hard disk test
I'd recommend all of these. But also just to be sure, you should backup your wallet and see if bitcoin runs fine with a blank wallet. If it does, your wallet could be corrupt and might need fixed.
|
|
|
|
|