Author

Topic: I'm an idiot! :) (Read 593 times)

donator
Activity: 1218
Merit: 1015
May 29, 2014, 07:04:41 PM
#7
Thanks for the prods. I think I've found the issue after seeing a couple other programs fail similarly. Doesn't appear to be an issue with Core at all.

I wasn't expecting to reinstall W7 (mobo fried). All I had was a USB stick with some form of W7 on it. Turns out it was 32-bit, so I have 2.72GB out of 16GB RAM usable. Now I need to find a 64-bit version of W7 and have a windows.old.old Roll Eyes Cheesy

Will lock thread now unless it turns out to be something else. Thanks again!
hero member
Activity: 508
Merit: 500
May 29, 2014, 06:44:55 PM
#6
22h behind when opening, updated to 20h behind before hanging.
That's what makes me believe it didn't have a problem with the difference in the Windows clock. I think it shouldn't have synced at all if it did..

Used old blockchain files from before reinstalling Windows.
Corrupted files?
donator
Activity: 1218
Merit: 1015
May 29, 2014, 06:40:11 PM
#5
Did it sync up to 20 hours, or it was 20 hours behind when you opened it after the system reinstall? Just curious... because if the former, I don't see why it would stop at -20 when the discrepancy is far less(seems pretty arbitrary).
22h behind when opening, updated to 20h behind before hanging. Used old blockchain files from before reinstalling Windows.
hero member
Activity: 508
Merit: 500
May 29, 2014, 06:36:02 PM
#4
Did it sync up to 20 hours, or was it 20 hours behind when you sarted it after the system reinstall? Just curious... because if the former, I don't see why it would stop at -20 when the discrepancy is far less(seems pretty arbitrary).
donator
Activity: 1218
Merit: 1015
May 29, 2014, 06:27:58 PM
#3
Spoiler!

Was a result of switching over PCs to a newly installed OS. Time was set for 6:29pm when it was 6:19pm. Oddly enough, that was while it was set to Pacific time while I'm in Eastern. Going by debug file, Core correctly guessed my time zone and noted a 179 minute discrepency (which isn't quite right, either), which I find really odd, though less than the useless hard hang. Tongue

In case I attracted a dev... why does Core go from a loading splash screen to being invisible (less tray icon) and unclickable for ~5 minutes on loading?

ETA: Actually... I take it back. It may be out of space.... I'll see if it does it again. I still have windows.old on it -- wasn't a fresh install, and haven't sorted through what I need and don't on the SSD, though datadir is set to a separate hard drive... don't think it ran out of space, but I'll wait to confirm.
hero member
Activity: 508
Merit: 500
May 29, 2014, 06:23:15 PM
#2
Ran out of space? Because that would be sorta funny.
If not...

!hint
donator
Activity: 1218
Merit: 1015
May 29, 2014, 06:06:07 PM
#1
Has been hanging on this screen for ~15 minutes. Will provide hints as requested.

Jump to: