version 15.0.1 hangs when "done Loading" windows 10 64bit

[bakd247]

I downloaded the latest version of bitcoin core version 15.0.1 and have been syncing the blockchain for the past 2 days.  For some reason every time I start my wallet...the block take FOREVER to verify and then when it says "Done Loading"  all the sudden Bitcoin Core is unresponsive and I have to end the task in task manager in order to do anything...forcing me to go back to an earlier version.

I am running windows 10 64 bit with AMD 6core 3.6GHZ processor and 32 GB of RAM but using a 1TB external HDD...never had problems putting the blockchain on external drives before and using wallets on external drive has been great until now...I usually use External SSD's though...my HDD is a brand new one and was working fine at first...I sysnced up to just under 2 years left and it just hangs every time it is "done Loading"and other programs work fine on it as well so it must be bitcoin-qt...I just start with a batch file telling bitcoin to use the data folder I made as the data directory like always...surely the external drive has nothing do do with it because earlier version work fine...using version 15.0 on the same drive after deleting 15.0.1 just fine and the blocks don't take forever to verify either

PLEASE FIX THIS!!! Or help me fix what I am doing wrong....Thanks in advance

[1713488844]

1713488844

[achow101]

Please post your debug.log file and screenshots of the issue.

During the entire loading phase, Bitcoin Core is doing a lot of computation. It is not surprising that it goes unresponsive and windows things that it has died. Instead of killing the process, let it keep running even when it is unresponsive. Kill it if it doesn't become responsive after a while (a while being several tens of minutes).

Please don't make posts just shouting "Please fix this" because you have failed to provide any relevant information about your problem for anyone to actually diagnose the issue and find either a bug or find what you are doing wrong. You have failed to follow the instructions in the stickied threads at the top of this section.

[bakd247]

I didn't think about even looking at it since it was an issue with windows running the program there would not be anything relevant in the debug.log file anyway...

I saw a post this morning stating that version 15.0.1 has an invalid / unsigned security certificate...which is more than likely why my machine wouldn't let it load....

why do i need to screen shot the loading screen saying Program not responding...there's nothing more to see other than "Program Not Responding"

also...nothing in debug.log...according to it...there is nothing wrong..

[achow101]

I saw a post this morning stating that version 15.0.1 has an invalid / unsigned security certificate...which is more than likely why my machine wouldn't let it load....

That post is wrong. 0.15.0.1 is signed with a valid certificate.

why do i need to screen shot the loading screen saying Program not responding...there's nothing more to see other than "Program Not Responding"

Do it anyways. You may not think that it is relevant, but it does show us where Bitcoin Core is when it crashes. Same with the debug.log file. Post it anyways. Giving us more information will allow us to diagnose the problem faster, even if you think it is irrelevant.

also...nothing in debug.log...according to it...there is nothing wrong..

Post it anyways. Just because you can't see something wrong there does not mean that there is nothing wrong. Often times people will overestimate their ability to understand the log files and miss the actual error. Post the entire thing.

[bakd247]

Here's the debug log....why would the handshake be timing out?   is the HDD maybe not fast enough running off of USB 3.0?   It works great then all the sudden stops working...in versions 15 and 15.01...PLEASE HELP!!!


2017-09-28 12:00:31 UPnP Port Mapping successful.
2017-09-28 12:00:41 Loading addresses from DNS seeds (could take a while)
2017-09-28 12:00:41 235 addresses found from DNS seeds
2017-09-28 12:00:41 dnsseed thread exit
2017-09-28 12:01:23 Pre-allocating up to position 0x1000000 in rev00890.dat
2017-09-28 12:01:24 UpdateTip: new best=000000000000000000523e81acd8d429dc591b8a26f9aecedefd77c5d26f3e27 height=469492 version=0x20000000 log2_work=86.533595 tx=228638231 date='2017-06-03 05:23:07' progress=0.884035 cache=0.9MiB(7284txo)
2017-09-28 12:01:24 GUI: Platform customization: "windows"
2017-09-28 12:01:24 GUI: PaymentServer::LoadRootCAs: Loaded  55  root certificates
2017-09-28 12:01:32 version handshake timeout from 0

[bakd247]

why does it work some times and not respond other times?
the debug log did not show this until now.....so the program not responding is not why the connection is timing out....

all other crypto core wallets work just fine...internet connection is fine...all incoming connections aloud...it worked one time...started syncing then all the sudden stopped getting blocks....and stayed that way for about an hour...the whole time saying it was still syncing.....

so i restarted it...and I had to restart it 6 times to get it to say handshake time out....

I have been doing this for over 2 years now and I know what the debug log is for so there is obviously a problem with windows updates and bitcoin 15...i have 14 working on linux just fine...and it loads everytime with no problems at all

[jackg]

why does it work some times and not respond other times?
the debug log did not show this until now.....so the program not responding is not why the connection is timing out....

all other crypto core wallets work just fine...internet connection is fine...all incoming connections aloud...it worked one time...started syncing then all the sudden stopped getting blocks....and stayed that way for about an hour...the whole time saying it was still syncing.....

so i restarted it...and I had to restart it 6 times to get it to say handshake time out....

I have been doing this for over 2 years now and I know what the debug log is for so there is obviously a problem with windows updates and bitcoin 15...i have 14 working on linux just fine...and it loads everytime with no problems at all

There's probably a stability issue with Windows 10 stopping your system from working correctly. Is any other program running when the core is other than system programs? Try closing all of them and see if your core starts working.

Also you could try checking eventlogs for any antivirus or firewalls that may be interfering with your connection and causing a timeout (also any VPN or tor could potentially cause issues).

[achow101]

Here's the debug log

Post all of it. The little snippet you posted is irrelevant.

....why would the handshake be timing out?

The peer that Bitcoin Core tried to connect to that time did not respond to the version message. This is normal behavior; sometimes nodes just aren't online when you try to connect to them.

[bakd247]

everything else is normal syncing behavior too....THERE IS NOTHING IN THE DEBUG LOG and I know what I am talking about....
and it is very relevant what I posted because that is the very last line of the debug log...everything else is just regular loading and syncing and exiting...been through all of it.,..this is a windows problem and not a bitcoin problem

BTW I really don't feel like permanently posting my external ip on this site so sorry but not posting the whole thing.....

sorry if that sounds rude but I have never gotten help from this forum and have always had to figure out bitcoin for my self....funny that the newest bitcoin software is the only software that my machine has problems with though...and the older version work just fine...

Makes me wonder if bitcoin is susceptible to the HeartBleed OpenSSL memory leak...only because it uses a 2010 library by default

[bakd247]

thank you jackg   that is the most relevant response ever ..windows update called my miner a trojan the other day so it makes me wonder a lot about the "exceptions"...what if I were to download a bootstrap.dat from someone and rescan...think that would work...anyone know of any verifiable places I could get a semi recent copy so I only have to sync a little bit...
anyways..I am doing a lot of rescanning and reloading of programs....memory diagnostics...the whole 9 yards..so I will post my findings...thanks agian

just figured out the external HDD was 47% fragmented...might have a lot to do with it...I am use to only running SSD's and it being a new HDD that had never even occurred to me....my diagnostics skillz seem to be lagging...lol   
working and waiting on that and much more to be sure...and keeping fingers crossed...

[achow101]

everything else is normal syncing behavior too....THERE IS NOTHING IN THE DEBUG LOG and I know what I am talking about....

You haven't demonstrated that you know what you are talking about.

and it is very relevant what I posted because that is the very last line of the debug log...everything else is just regular loading and syncing and exiting...been through all of it.,..this is a windows problem and not a bitcoin problem

There can be errors up in the log that get hidden by the verbosity of the sync that can indicate problems that cause a crash later on. In general, having more people looking at the issue makes it more likely that someone will find the problem. But not providing any information (e.g. debug.log file or crash logs or screenshots or whatever) makes that hard to do because then all people have to go off of is your word, and that may not necessarily be understood properly and will include your own biases as to what you think the problem is.

How about you provide some other information then? How about the Windows crash logs?

BTW I really don't feel like permanently posting my external ip on this site so sorry but not posting the whole thing.....

Then redact your IP address. Do a find and replace and replace your IP address with [redacted]. It isn't hard to do.

Makes me wonder if bitcoin is susceptible to the HeartBleed OpenSSL memory leak...only because it uses a 2010 library by default

It's statements like these that tell me you don't know what you are talking about.

thank you jackg   that is the most relevant response ever ..windows update called my miner a trojan the other day so it makes me wonder a lot about the "exceptions"...what if I were to download a bootstrap.dat from someone and rescan...think that would work...anyone know of any verifiable places I could get a semi recent copy so I only have to sync a little bit...

Don't use a bootstrap.dat. That's way slower than just resyncing the whole blockchain from scratch.

If you have an antivirus software, make sure that it isn't deleting anything in the Bitcoin Core data directory. Check Windows defender too.

[bakd247]

if you say so....I read the whole damn thing and there is nothing relevent in there..I do know how to read...believe it or not.......

it may not be hard to do but it is very time consuming to do something that is irrelevant in the first place...

like I said this is not a problem with bitcoin...it is a problem with the drive and windows syncing

So I reformatted the HDD and reinstalled and all works fine...had nothing to do with the debug log file...

why not try just NOT responding since you have no idea what the issue could be related to in the first place....

[bakd247]

"Don't use a bootstrap.dat. That's way slower than just resyncing the whole blockchain from scratch."

This statement proves you don't know what your talking about

Plus the debug.log will never say anything about a fragmented hard disk...which is what the problem was....the chain kept syncing on top of fragmented disk space so the drive kept thinking it was already full when it was over half way fragmented and I had to run diagnostics and de-fragment it numerous times because it kept saying there was still 1% fragmented...

0% fragments and full disk optimization was the fix....had nothing to do with debug.log file

works faster than ever now...

[cr1776]

"Don't use a bootstrap.dat. That's way slower than just resyncing the whole blockchain from scratch."

This statement proves you don't know what your talking about

...

For others reading this,  downloading Bootstrap.dat has been much slower for many versions now compared to a regular sync and is not recommended. Regardless of what is stated above, bootstrap.dat is a bad idea.

[jackg]

"Don't use a bootstrap.dat. That's way slower than just resyncing the whole blockchain from scratch."

This statement proves you don't know what your talking about

Plus the debug.log will never say anything about a fragmented hard disk...which is what the problem was....the chain kept syncing on top of fragmented disk space so the drive kept thinking it was already full when it was over half way fragmented and I had to run diagnostics and de-fragment it numerous times because it kept saying there was still 1% fragmented...

0% fragments and full disk optimization was the fix....had nothing to do with debug.log file

works faster than ever now...

That's good to hear that your problem is now fixed (I should probably try to defrag mine and see if I can get a better speed from it).


I'm curious to find if explorer.exe (Windows Explorer) said that the drive was full? Or if you had to use a utility program to analyse the drive.

If you're looking for a copy of bootstrap.dat then I know one of the core devs Jeff Garzik (JGarzik) here made one but I'm not sure how up to date it is. Although it is considered to be slower unless you have a dial up modem (although I've never actually tried it). It is possibly less secure in case you download something with it but that risk is fairly minimal. Also, if you have antivirus installed, make the bitcoin data folder a blind-spot/quarenteened area from it. As someone apparently added virus signatures to transactions (either for fun or as a way of hijacking the chain) - if you need any help with this, search for tutorials unless you use Symantec's Norton  or just the regular windows utility av software as I have a copy of those and know how they functions.

[HCP]

"Don't use a bootstrap.dat. That's way slower than just resyncing the whole blockchain from scratch."

This statement proves you don't know what your talking about

Plus the debug.log will never say anything about a fragmented hard disk...which is what the problem was....the chain kept syncing on top of fragmented disk space so the drive kept thinking it was already full when it was over half way fragmented and I had to run diagnostics and de-fragment it numerous times because it kept saying there was still 1% fragmented...

0% fragments and full disk optimization was the fix....had nothing to do with debug.log file

works faster than ever now...

That's complete rubbish. File fragmentation does not cause the system to think a disk is full, regardless of how fragmented it is... All fragmentation does is impact on read and write speeds as the drive head has to constantly readjust to read the scattered fragments or find the empty sectors that it can write too.

And it has been a well known fact for several versions that bootstrap.dat IS slower than resyncing from scratch...
https://github.com/bitcoin-dot-org/bitcoin.org/issues/846
https://bitcoin.org/en/release/v0.10.0#faster-synchronization


"It's better to remain quiet and be thought a fool, than to open your mouth and remove all doubt"