This PC is dedicated to running wallets only, nothing has changed. I manually install all updates, no updates where installed recently. I have all ports closed, except from another PC on my network. This PC does not communicate directly with the internet. All PC's on my network are protected with webroot. I am fairly certain there is no infection. As I said, I run multiple wallets on this PC and none of them are having this problem. I did delete the wallet and install a new one, though I did not not delete the data. I did update Firefox a while back, but it was working fine well after that. I really don't want to have to resync the chain, but I will eventually if I dont find a fix. I suppose webroot could have started blocking the wallet at some point, though I haven't found it doing that anywhere. I'll look into that more. With the all the recent 0days coming out with the Hack Team hack, it could be something form that I guess.
Have you tried to run the wallet in a portable mode?
Read more about this, I wrote here:
https://bit.diamonds/community/index.php/topic,100.msg733.html#msg733 That's basically how I run all of my wallets, as I keep the data on a separate hard drive. I just make shortcuts and add the -datadir to the properties of the shortcut. For the sake of it I did try your method and I get the same thing. How did the guy who also have this problem fix it? I ran the wallet in a sandbox and nothing unusual happened, though it did still crash.
Edit: I moved the data dir back to c: and it crashes with the up to date data, if I let it try to resync it runs fine. I did finally get it to throw a runaway exception error. Looks like I am going to have to redownload the whole chain ;(
u are the 3rd guy reporting such behavior in a lot months
so yes there seems to be under very rare situations such a problem
but we didnt get enough info how it did happen and also how it was solved
(one guy as u see in link
https://bitcointalksearch.org/topic/m.11501900solved it somehow by disabling some update services?
sound pretty unrelated and unlogical but if it helped? )
one of the guys gave me logfiles but the wallet was normal working only the frontend/GUI was white and frozen
its just not enough data to be able seek and destroy this rare bug
its not even clear if there is a bug or just a rare case that would affect even the best written wallet
it would be helpful if we at least learn how u fixed it
please give us that feedback once available