setup.exe crash 0xC0000005 @ 2E0075

Wiki Link: [discussion:218777]
logigap
Jul 8, 2010 at 2:28 PM
Edited Jul 8, 2010 at 2:35 PM
 I have a customer that had setup.exe crash on them, and they sent me the dump. Has anyone had setup.exe crash at this offset with the following info? Any ideas are greatly appreciated... This was DNI Version 1.10.8308 FAULTING_IP: setup+2e0075 006e0075 02f8 add bh,al EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 006e0075 (setup+0x002e0075) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 006e0075 Attempt to execute non-executable address 006e0075 DEFAULT_BUCKET_ID: SOFTWARE_NX_FAULT PROCESS_NAME: setup.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000008 EXCEPTION_PARAMETER2: 006e0075 WRITE_ADDRESS: 006e0075 FOLLOWUP_IP: setup+2e0075 006e0075 02f8 add bh,al FAULTING_THREAD: 00001120 PRIMARY_PROBLEM_CLASS: SOFTWARE_NX_FAULT BUGCHECK_STR: APPLICATION_FAULT_SOFTWARE_NX_FAULT LAST_CONTROL_TRANSFER: from 00439713 to 006e0075 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 0647eaa4 00439713 0647eafc 06120bc8 a65cc7da setup+0x2e0075 0647eb34 00439431 0647ed18 00000002 0612d7c4 setup+0x39713 0647eb64 0043916a 0612d008 0612fdd8 06130038 setup+0x39431 0647ebc8 00438ec6 0647ed18 0647ebf0 0647ed00 setup+0x3916a 0647ec08 0043815e 0647ecd4 0647ed10 0647ed00 setup+0x38ec6 0647fe98 00437c5c 06120bc8 06120bc8 0647fef0 setup+0x3815e 0647fea8 00437268 a65cd392 002eeabc 06120b78 setup+0x37c5c 0647fef0 00461e55 06120bc8 a65cd21a 00000000 setup+0x37268 0647ff78 0049250b 002eeabc a65cd2d2 00000000 setup+0x61e55 0647ffb0 004925b0 00000000 7d4dfe37 061307a0 setup+0x9250b 0647ffec 00000000 00492531 061307a0 00000000 setup+0x925b0 STACK_COMMAND: ~2s; .ecxr ; kb SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: setup+2e0075 FOLLOWUP_NAME: MachineOwner MODULE_NAME: setup IMAGE_NAME: setup.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4bf1cfb0 FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_setup.exe!Unknown BUCKET_ID: APPLICATION_FAULT_SOFTWARE_NX_FAULT_setup+2e0075
dblock
Coordinator
Jul 8, 2010 at 3:06 PM
  • What exact OS does the customer have?
  • At what point does it crash?
  • Is there a log file?
  • Does running with /log /logfile install.log produce a log file?
  • Is this repeatable (does it crash every time)?

This output never provides any useful data. Ideally you need symbols and a debugger.

 
logigap
Jul 9, 2010 at 1:07 PM

I deal with crashes and customers a lot, and I am ashamed that I did not provide at least the OS level of this problem.  Sorry DB - I know how frustrating it is to have to ask for obvious stuff.

The version is:

Windows Server 2003 Version 3790 (Service Pack 2) UP Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS

My setup has 3 componenets to install. 

dot net 351 install first (download from net)
then MySQL second (and it crashes on this step, but it didn't install dot net 351 because is was already installed),
and the third component is my code.

I am working with the customer now to get him to rerun the setup with logs this time.  I might have them today or by Monday.

I asked him if it was repeatable earlier, and he hasn't tried it again.  We'll see.

Thanks for your help.  I'll get back to you asap with more info.

 

 
logigap
Aug 3, 2010 at 4:49 PM
Edited Aug 3, 2010 at 4:50 PM

I was not able to reproduce and the user hasn't either...so that's all... probably user error anyway :)

Thanks for your help Db.
icnocop
Developer
May 3, 2012 at 11:57 PM

I believe this is fixed with commit cc629435baa42dc6b6d824acaf9a016994a9c94f on https://github.com/dblock/dotnetinstaller on May 1st, 2012.

Fixed crash when WaitForSingleObject returns nonsignaled member when Start() and End() were called quickly in succession causing pointers to be deleted while a dependent thread is still running.
Sign in to post message or set email notifications