Win7 64bit since last patch Tues now crashes
This is from 0.3.14-win32-setup.exe. Previously I was running (up until an hour ago) a version of bitcoin.exe from Jul-2010 (which also was crashing) and the crash reports look similar. So I upgraded to see if the problem has been fixed.
To clarify what I am saying any starting of the EXE immediately reports the crash. So when I login I see the Win7 crash report and if I manually try to start it the same. The dialog beyond the crash report is “The application was unable to start correctly (0xc0000005). Click OK to close the application.”
Please also try to tag the application .EXE with the version information if possible, as you can see it is 0.0.0.0.
Code:
Have tried turning off Windows Defender, Real Time checking and excluding “C:\Program Files (x86)\bitcoin” but this made no difference.
As another recent thread indicates their problem was fixed or potential solution in this way.
This thread below is the closest match. I can say the crash started the moment I rebooted after October 2010 patch Tuesday, windows update (which were only applied a few days ago).
http://bitcointalk.org/index.php?topic=991.0
FYI - I was not overclocking or otherwise buggering about with anything in ways I’m not meant to. Which the above thread OP claims to have done. Also My Wallet.dat looks fine, none of the AppRoaming files have been modified since I rebooted after installing the 23 updates all in one go.
Quote from: Odin on October 22, 2010, 09:24:38 PM
Fault Module Name: mingwm10.dll
This is the important clue. I believe it’s saying it crashed in that. Maybe there are other versions of it to try. mingwm10.dll is just a simple placeholder thing that satisfies some callback requirement for multithreaded apps.
Is anyone else running OK on Windows 64-bit?
I have no problems with the official Bitcoin and 64-bit Windows 7.
Ok good to know others are able to run it ok.
Unfortunately bitcoin is not a critical application for me and need to spend my time on other things. If however there is a debugging build of the application which can provide line numbers for the crashed code (0xc0000005 - ACCESS VIOLATION) then I’d be happy to run it to identify the line causing the problem.
The only thing I can think of is to see if there are other versions of mingwm10.dll you can get. mingwm10.dll is a tiny little DLL that came with the MinGW compiler that you need when you build for multi-thread. I don’t know exactly what it does, but it probably just says something like “yes Windows, see I’m in a DLL like you insisted.”
The end of your debug.log file might show the last thing it was doing before it crashed.