Bootstrap will not make your sync faster with current Bitcoin Core version 
He already download Bootstrap.dat. So syncing locally will be faster than syncing while downloading.
Yeah dude you right its not working with Bitcoin Core version v0.10.1 (64-bit)..Is there anyother way?
You can add some nodes that have a fast connection by hand. Close bitcoin core. Hit Win + R and enter:
Code:
c:\Program Files\Bitcoin\bitcoin-qt.exe -connect=185.45.192.129
This will limit your connection to a single node. Once your node is fully synced, close and start normally. Keep in mind that sync speed still depends on your CPU, HDD(SSD) speed and the speed of your internet connection. If a node is not reachable or no longer accepting outside connection, start with another IP.
list of nodes:
Code:
last updated 2015.04.24
-------------------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------------------
185.45.192.129 - Amsterdam, NL, EU - anon - 2x1000 mbit/s - node.cryptowatch.com - yes
94.23.146.127 - NL, EU - Mitchełł[5] - 200 mbit/s - /status - no
213.165.91.169 - Germany, EU - shorena - 100 mbit/s - yes - no
191.236.50.217 - Virgina, US - grue - 100 mbit/s - no - no
-------------------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[3] be down!!
-------------------------------------------------------------------------------------------------------------
5.9.90.133 2 - Falkenstein, DE, EU - zvs - 500 mbit/s - no - no
84.200.34.113 2 - Freinsheim, DE, EU - Newar - 1000 mbit/s - yes - no
23.92.214.123 2 [4] - Rochester, USA - Newar - 100 mbit/s - no - no
-------------------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[4] Runs BTCD (alternative full node implementation with GO)
[5] I dont want you search for those ł's on your keyboard, have a link
https://bitcointalk.org/index.php?action=profile;u=113670
-------------------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------------------
185.45.192.129 - Amsterdam, NL, EU - anon - 2x1000 mbit/s - node.cryptowatch.com - yes
94.23.146.127 - NL, EU - Mitchełł[5] - 200 mbit/s - /status - no
213.165.91.169 - Germany, EU - shorena - 100 mbit/s - yes - no
191.236.50.217 - Virgina, US - grue - 100 mbit/s - no - no
-------------------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[3] be down!!
-------------------------------------------------------------------------------------------------------------
5.9.90.133 2 - Falkenstein, DE, EU - zvs - 500 mbit/s - no - no
84.200.34.113 2 - Freinsheim, DE, EU - Newar - 1000 mbit/s - yes - no
23.92.214.123 2 [4] - Rochester, USA - Newar - 100 mbit/s - no - no
-------------------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[4] Runs BTCD (alternative full node implementation with GO)
[5] I dont want you search for those ł's on your keyboard, have a link
https://bitcointalk.org/index.php?action=profile;u=113670
