It's not consistent. It appears to be reading a time that is frozen on or about May 20th, but it sometimes only reads it for a couple of random minutes before it finds the correct time somewhere. Even changing the BIOS way off and back doesn't make the problem go away. Even when I find the right time on May 20th, within 5 minutes of setting the time, I'm back looking at the message as the world turns under my stuck in time computer. The only thing that confuses me, is why the bitcoin client is the only program that is reading a bad date/time. My BIOS is right, my Windows is right. I wrote a little c# program that loops around and displays DateTime.Now and never see anything but the correct time. It's got to be a hardware issue, but not like anyone I've ever seen before.
before spending your money on a new computer, you can try a linux live cd to check if the issue is isolated to windows ...or not, if you need a excuse for a gaming machine  . |
|
|
|
Ok, you don't need all vendors to be compromised at once and who said anything about them being 'hacked'. Governments can easily coerce any large company into signing anything.
that's the point. It's highly unlikely that every software vendor is hacked. of course they can coerce the companies, but it would be very hard for the "government" to frame anyone. Even with a wallet backup, you can have your client patched to steal your password and coins the next time you make a transaction.
bitcoin builds can be audited by anyone. plus with hardware wallets, it would be very hard to "patch" anything. You know, there is software that "encrypts" the binary so that it does a self-check if the binary has been modified. I think it was a Themida based protection.
bitcoin is open source, you can always build your own copy without protection. Why the conspiracy theories? In the US the gov could do it the same as they did with online poker - make it so it's illegal for banks to send money to bitcoins and to not allow US firms to accept them. If we can't do wires, dwolla, moneygram, etc it becomes exceedingly hard to buy / sell bitcoins. It wouldn't shut it down entirely yet without the convenience of being able to use them the appeal would rapidly bring the value down and no real value as an online exchange medium.
because it's human nature to think that "someone" is out to get you. it's easy and reassuring to point the finger at a powerful authority, such as the US government. |
|
|
|
Yes, I'm leaning toward motherboard issues also. It looks like my wife is going to get a pretty robust (though slightly used) gaming machine. Time for me to go shopping again. I always get the new computer  if the time sample is always off by a consistent amount, try setting the BIOS time forwards/backwards to compensate for it. In your case, try setting it back 38941 minutes. |
|
|
|
As I said, the only time this ever happens is with the bitcoin client running. So obviously it's not a hardware issue. Also, I'm not much of a programmer, but I thought in Windows, the OS is the only thing allowed to run in kernel mode, with the application using Windows API calls for kernel mode needs. Either way, the BSOD that is happening clearly correlates to the bitcoin client, so don't tell me it's impossible for that to happen. Maybe it's making an API call in a weird way or something.
Correlation does not imply causation. Even if bitcoin does make a faulty API call, the driver is not supposed to bluescreen. If it does, it's still the driver's fault. Also, please update to the latest version before filing an issue, as there might be various fixes. |
|
|
|
there's definitely something wrong with your computer. Here are my timesamples: Line 90: 2013-06-17 04:01:26 Added time data, samples 103, offset -1 (+0 minutes)
Line 109: 2013-06-17 04:01:37 Added time data, samples 104, offset -4 (+0 minutes)
Line 778: 2013-06-17 13:49:29 Added time data, samples 105, offset +3 (+0 minutes)
Line 786: 2013-06-17 13:49:30 Added time data, samples 106, offset +0 (+0 minutes)
Line 1092: 2013-06-17 13:50:14 Added time data, samples 107, offset +0 (+0 minutes)
Line 1099: 2013-06-17 13:50:15 Added time data, samples 108, offset -1 (+0 minutes)
Line 1105: 2013-06-17 13:50:15 Added time data, samples 109, offset +1 (+0 minutes)
Line 1125: 2013-06-17 13:50:21 Added time data, samples 110, offset +1 (+0 minutes)
Line 1131: 2013-06-17 13:50:22 Added time data, samples 111, offset +1 (+0 minutes)
Line 1138: 2013-06-17 13:50:23 Added time data, samples 112, offset +0 (+0 minutes)
Line 1152: 2013-06-17 13:50:26 Added time data, samples 113, offset +3 (+0 minutes)
Line 1637: 2013-06-17 13:57:56 Added time data, samples 114, offset +2 (+0 minutes)
Line 2047: 2013-06-17 23:27:54 Added time data, samples 2, offset +0 (+0 minutes)
Line 2052: 2013-06-17 23:27:55 Added time data, samples 3, offset +0 (+0 minutes)
Line 2116: 2013-06-17 23:28:26 Added time data, samples 4, offset +0 (+0 minutes)
Line 2174: 2013-06-17 23:28:39 Added time data, samples 5, offset -1 (+0 minutes)
Line 2185: 2013-06-17 23:28:42 Added time data, samples 6, offset +1 (+0 minutes)
Line 2245: 2013-06-17 23:28:51 Added time data, samples 7, offset +3 (+0 minutes)
Line 2402: 2013-06-17 23:29:15 Added time data, samples 8, offset -1 (+0 minutes)
Line 2405: 2013-06-17 23:29:15 Added time data, samples 9, offset +5 (+0 minutes)
Line 2473: 2013-06-17 23:29:21 Added time data, samples 10, offset -1 (+0 minutes)
Line 2595: 2013-06-17 23:29:38 Added time data, samples 11, offset +0 (+0 minutes)
Line 2638: 2013-06-17 23:29:54 Added time data, samples 12, offset +1 (+0 minutes)
Line 2687: 2013-06-17 23:30:36 Added time data, samples 13, offset +2 (+0 minutes)
Line 2755: 2013-06-17 23:31:36 Added time data, samples 14, offset +1 (+0 minutes)
Line 2826: 2013-06-17 23:33:09 Added time data, samples 15, offset +1 (+0 minutes)
Line 2860: 2013-06-17 23:33:40 Added time data, samples 16, offset +2 (+0 minutes)
Line 2865: 2013-06-17 23:33:41 Added time data, samples 17, offset +3 (+0 minutes)
Line 2945: 2013-06-17 23:35:06 Added time data, samples 18, offset +152 (+2 minutes)
Line 2997: 2013-06-17 23:36:03 Added time data, samples 19, offset +0 (+0 minutes)
Line 3033: 2013-06-17 23:36:36 Added time data, samples 20, offset +0 (+0 minutes)
Line 3367: 2013-06-17 23:41:55 Added time data, samples 21, offset +0 (+0 minutes)
Line 3730: 2013-06-17 23:48:17 Added time data, samples 22, offset +1 (+0 minutes)
Line 3851: 2013-06-17 23:50:21 Added time data, samples 23, offset +0 (+0 minutes)
Line 3867: 2013-06-17 23:50:37 Added time data, samples 24, offset +0 (+0 minutes)
Line 4319: 2013-06-17 23:54:40 Added time data, samples 25, offset +1 (+0 minutes)
Line 5037: 2013-06-18 00:01:34 Added time data, samples 26, offset +4 (+0 minutes)
Line 6266: 2013-06-18 00:09:12 Added time data, samples 27, offset -15 (+0 minutes)
Line 7156: 2013-06-18 00:14:41 Added time data, samples 28, offset -7 (+0 minutes)
Line 7173: 2013-06-18 00:14:47 Added time data, samples 29, offset +1 (+0 minutes)
Line 7321: 2013-06-18 00:16:29 Added time data, samples 30, offset +22 (+0 minutes)
Line 7712: 2013-06-18 14:26:51 Added time data, samples 2, offset +2 (+0 minutes)
Line 7762: 2013-06-18 14:27:09 Added time data, samples 3, offset -1 (+0 minutes)
Line 7764: 2013-06-18 14:27:09 Added time data, samples 4, offset +247 (+4 minutes)
Line 7767: 2013-06-18 14:27:09 Added time data, samples 5, offset -3 (+0 minutes)
Line 7776: 2013-06-18 14:27:10 Added time data, samples 6, offset +1 (+0 minutes)
Line 7840: 2013-06-18 14:27:22 Added time data, samples 7, offset +0 (+0 minutes)
Line 7913: 2013-06-18 14:27:30 Added time data, samples 8, offset +15 (+0 minutes)
Line 8057: 2013-06-18 14:27:50 Added time data, samples 9, offset +3 (+0 minutes)
Line 8069: 2013-06-18 14:27:51 Added time data, samples 10, offset +2 (+0 minutes)
Line 8109: 2013-06-18 14:27:56 Added time data, samples 11, offset +3 (+0 minutes)
Line 8229: 2013-06-18 14:28:03 Added time data, samples 12, offset +3 (+0 minutes) I'm guessing you're getting trolled by every peer you're connected to, or your system clock is malfunctioning. Why is the line this: if (nOffset != 0 && abs64(nOffset) < 5 * 60)
fMatch = true;
and not this: if (abs64(nOffset) < 5 * 60)
fMatch = true;
I believe Schleicher is right. nOffset is in seconds, and it's easy to be under one second by time syncronisation. So if every nOffset is Zero, the second comparison with "abs64(nOffset) < 5 * 60" is never checked. I cannot explain the output of debug.log. those lines are only executed if there is a time difference. therefore nOffset can't be zero. |
|
|
|
If you use OSX, Windows, or any Linux with 'auto-update' then the government has a ready-made backdoor through which they could delete all traces of Bitcoin and their wallets from most computers.
They could send a 'stealth' update through normal channels, most computers would install it. Then on some specified date all bitcoin related files would be deleted including the client.
It would probably be an 'unpopular' move, but the government would probably find a way to make it look like a security breach by hackers rather than an intentional attack by government. They may even 'frame' someone and lock them up so people don't keep looking for the real attacker.
Highly unlikely. All updates by major software vendors are signed, and the signing keys are stored in specially designed hardware. It would be highly unlikely that ALL software vendors had their signing keys compromised. Even if you were smart enough to have an off-line backup the vast majority would not.
LOL, who doesn't keep backups? It's going to be easier than ever with deterministic wallets. All 'trust' in the safety of bitcoin wallets would be destroyed taking the value of bitcoin with it.
No, people will just learn to BACKUP THEIR WALLETS. |
|
|
|
You first have to import the signing key first. In this case, import: -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: SKS 1.1.3
mQENBFD1gzgBCADGVp8wVMk0viUTR3FBzCfdGGULYcyiKFNdGlKxORyrdWJF6/g5JuYPU0NX
CRJ7hqX4hopOiID+oxE7p/vP/i/Sm6B6xZMq8bJ+PiJ2h8ZqnourgL8tkAqlDV+zLana+XeQ
PsPhJPeARAQDtl5QhQbvWm0idMyd1zuWdt4OVIYnhJ7w7Mw0CdUmBbkTc1P23J8vwqiyyuHq
V3JimkNJLm4vyWGFig6ElgRMbV5YWci41OTH3x8qkWHFdB1h0ODP/28bBwpVVXqnObrp/Lsr
9aQSP5VujGIL/cOdel/7xD2Dc5qS/HXYZgJUk6x2WkLmO47NSpW6rone3W2A82gkKRwXABEB
AAG0H0FuaW1hemluZyA8YW5pbWF6aW5nQGdtYWlsLmNvbT6JATgEEwECACIFAlD1gzgCGwMG
CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJECJFMARpVQb95i8IAISo2NvZW8Zln4ivuo5l
6PirIrzSIlec3Xa/xmkgrHTfBVT3WYeGp54NkEcpgarD1qjt5ZFF7wExn9WLErGlsIkPmegO
Zjx2mn3ZyB+Y5y0cJeGPM72aD0Z3jaBi+htv37GMb2mV6yO700dG1x3vwS1YYyRLgR6pVwlR
w+0l+5B/5zHsKdRvpRcuTpmrg8rtgTxZOsRyORn6ck6w7lUbno3+1XMBTFTbVf4/SymMU3Wl
9eru2agYRfkB3puXd8DMYlSzZiiUWTHV6bOsB0N001sJtmFf6KmM1xF8Q/eqMlWevS2sd0XG
OWFQu4RGyAJqN7h1Z3cym278WVCMhYzJn/S5AQ0EUPWDOAEIAMzeN8NjFRB53Fid/IagQxxQ
ZeD1Y9cn9S6fJ+nEoZWMPQ+iVCictH3gmqm+eZ0qOrqSTxkXgyIh7Uiu2lwjm7nmeBK328k2
ei1e3bpp0I2oMiShVAehxbXx5Jh29nlPDS8US/xehj6WnUeojR2qXVOSAtK7+V7taSyigOpY
r/+5fcq+/8Z+d+NaVp97MUmoH5LVNU2jCR+qyIM07qX2G4Vx+hU4tjc79Kl6m1equ6/sHwnk
mMIsGvLHZG+Pq+1wHIZwt1p39MhFvob9B2RFqbFtihTal36D0NBQMdlp9PtKtQZSQR5hWsmW
G+m17/vyux7ZtwnTRbR+p/adFx6fsTcAEQEAAYkBHwQYAQIACQUCUPWDOAIbDAAKCRAiRTAE
aVUG/aARB/9pYfkB4rDe4OulrUXBusTxOGKm1yPjZaXveOqQkD8/2Vwxu7tYFMVMLDKYtvxp
mrUdb6oz9s8XrTkMIW7ZM3FmhNQhxsfEj9g6UGJnCXcf+Zw9wbqmzONNCupfN5wPOtoGd+KF
UR5dVl3+BsUoIEcAcPR5AdP9gbqDSbrDyuk8+j1CfiLVAQXud3u2rkt8GWbTJ/LzKtF1UM0X
3YnE7fxi61DDgX6A1EJfss3aFj2lwmb38Yp041WKik2ZZEQpyQ8rXeYG8Wl0wSEYaMPDedEH
RDoIAYRshRHglZYCD80LF7c31koGLGzVWio3erJgUYUwhy1QUltdVL+5PcVyUlm1
=T2Ag
-----END PGP PUBLIC KEY BLOCK----- then use the file manager in gpg4win to verify the file. |
|
|
|
I recommend you make a backup after every transaction you make, because of hidden change addresses that you don't normally see.
No need for that, with the default keypool of 100 pre-generated addresses a backup only after every 100 transactions is required. Actually, 100 <= (sent transactions + generated addresses) |
|
|
|
|
It's impossible for user mode applications to cause bluescreens. Only code running as kernel mode can. You should update your drivers to the latest version and check for hardware damage or overheating.
|
|
|
|
You are being very vague about what's wrong. All you're telling us is "I can't get anything to run". Can you include specific error messages? I am running 4 PCs from home doing this.
Would that amount of traffic be considered a Denial of service attack?
It's highly unlikely that you're being attacked. I cannot connect at all and I am thinking this may be an issue.
My configs ARE correct
It's possible that the pool you have configured is down. ps. STOP USING COMMAS AS ELLIPSIS. |
|
|
|
|
Yes, but it would be a hard fork. Also, since "coins" are stored as integers, all existing coins will effectively increase in count. For example, if it was altered to support 8 more decimal places, present day "satoshi" will be 10^8 units.
|
|
|
|
|
b-but it doesn't have a liquid nitrogen generator!
|
|
|
|
|
Even with a cheap gpu (less than $200), you can get more than 200x hash power. decide for yourself.
|
|
|
|
it's not passive, there are microcontrollers on the board.  |
|
|
|
grue, I did what you said there were two wallet.dat files I put them in folders on desktop, saved the wallet.dat file in %appdata%\bitcoin to flashdrive and deleted.
added wallet.dat file and put each one from desktop, both bitcoin qt wont start now says wallet.dat corrupt,salvage failed.
tried to install original wallet.dat from flashdrive and same result...
I appriciate everyones help today, thanks.....I got to go until tommorrow, check back then.
It sounds like you misread the directions. It's very unlikely for multiple copies of wallet.dat to all be corrupt, and even less likely for a fresh, working backup to be corrupt as well. I can use teamviewer and attempt a fix, but if you think you followed the instructions correctly, it's best to check this: https://bitcointalk.org/index.php?topic=25091.0 |
|
|
|
They are mining with you machine until there is no ROI and then ship to you.
FUD more |
|
|
|
Seriously, I will be ignoring your PM's if anything goes wrong on this tx.
Looking at your post history... you sir, are a troll. Congratulations  oh what's wrong, someone came to ruin your party? better call them a troll, that will show everyone how legit you are. ps. fixed your broken quotes |
|
|
|
|
1. open c:\windows.old\ with windows explorer
2. in the search box to the right, type in "wallet.dat"
3. copy (don't cut) all matching files to a folder on your desktop
4. open windows explorer and type in "%appdata%\bitcoin\" in the address bar
5. if wallet.dat already exists, make a backup of it
6. delete everything in the folder
7. paste one of the wallet file from step 3
8. start bitcoin-qt, check if there is non zero balance. unconfirmed balance is OK. you do not need to rescan
9. repeat step 6 to 8 until you found your coins.
If you need additional help, I can VNC/teamviewer.
|
|
|
|
prevents conversations to be taken out of context(by making it necessary to read an entire thread to understand the flow of the conversation.
how exactly does removing nested quotes add more context? if anything, it reduces context and forces users to guess what each other is talking about. |
|
|
|
|
Show Posts
