Basic Debugging of an Application Crash

re: Basic Debugging of an Application Crash

Joel — Sun, 22 Jul 2012 01:34:08 GMT

Excellent information. Easy to understand and thorough! Thank you!

re: Basic Debugging of an Application Crash

Elizabeth Derby — Wed, 15 Jun 2011 22:28:45 GMT

I hav e tried several; tgimes to install my hp d esktop F4400 serious printer to my acer new computer and everythime I treid I get thr that the installer has stopped working due to Application Crash. Is there anything I can do do about it . so can reainstall the disc to it

re: Basic Debugging of an Application Crash

Raji — Thu, 19 Aug 2010 13:03:23 GMT

Please help on the below issue

My application uses twain dll for scanning documents. There are so many users using my application. But for few users my application hangs and getting the error that my application stopped working. The users reported this issue are using either windows vista or windows 7 version. The memory dump shows “System.Runtime.InteropServices.COMException”. Please see below the stack trace taken from the memory dump.

FAULTING_IP:

ntdll!RtlReportCriticalFailure+5b

77a6015d eb1c jmp ntdll!RtlReportCriticalFailure+0x6f (77a6017b)

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)

ExceptionAddress: 00000000

ExceptionCode: 80000003 (Break instruction exception)

ExceptionFlags: 00000000

NumberParameters: 0

FAULTING_THREAD: 000016e0

PROCESS_NAME: NetX360.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

MANAGED_STACK: !dumpstack -EE

OS Thread Id: 0x16e0 (0)

Current frame:

ChildEBP RetAddr Caller,Callee

EXCEPTION_OBJECT: !pe 28dba80

Exception object: 028dba80

Exception type: System.Runtime.InteropServices.COMException

Message: Unknown error.

InnerException: <none>

StackTrace (generated):

SP IP Function

StackTraceString: <none>

HResult: 80004005

MANAGED_OBJECT: !dumpobj 28dbac8

Name: System.String

MethodTable: 6a110a00

EEClass: 69ecd64c

Size: 46(0x2e) bytes

(C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll)

String: Unknown error.

Fields:

MT Field Offset Type VT Attr Value Name

6a112c4c 4000096 4 System.Int32 1 instance 15 m_arrayLength

6a112c4c 4000097 8 System.Int32 1 instance 14 m_stringLength

6a1116e0 4000098 c System.Char 1 instance 55 m_firstChar

6a110a00 4000099 10 System.String 0 shared static Empty

>> Domain:Value 00082978:01db1198 <<

6a111630 400009a 14 System.Char[] 0 shared static WhitespaceChars

>> Domain:Value 00082978:01db1740 <<

EXCEPTION_MESSAGE: Unknown error.

MANAGED_OBJECT_NAME: System.Runtime.InteropServices.COMException

LAST_CONTROL_TRANSFER: from 77a60d68 to 77a6015d

BUGCHECK_STR: APPLICATION_FAULT_ACTIONABLE_HEAP_CORRUPTION_heap_failure_invalid_argument_WRONG_SYMBOLS

PRIMARY_PROBLEM_CLASS: ACTIONABLE_HEAP_CORRUPTION_heap_failure_invalid_argument

DEFAULT_BUCKET_ID: ACTIONABLE_HEAP_CORRUPTION_heap_failure_invalid_argument

STACK_TEXT:

77a6015d ntdll!RtlReportCriticalFailure+0x5b

77a60d68 ntdll!RtlpReportHeapFailure+0x21

77a60e56 ntdll!RtlpLogHeapFailure+0xa1

77a2b0c8 ntdll!RtlSizeHeap+0x69

778212e0 ole32!CRetailMalloc_GetSize+0x21

767f43d9 oleaut32!APP_DATA::FreeCachedMem+0x30

767f3e6c oleaut32!SysFreeString+0x6b

118b1647 VM31bTXP+0x1647

779ee1c4 ntdll!LdrpCallInitRoutine+0x14

779e8dea ntdll!LdrpUnloadDll+0x3d8

779ee8e2 ntdll!LdrUnloadDll+0x46

76aa0979 kernel32!FreeLibrary+0x15

597d6512 twain!CDataSrc::unload+0x22

597d66b9 twain!CDataSrc::SendMessageA+0x81

597d6c1e twain!CDataSrc::identityMsg+0x18

597d6d0d twain!CDataSrc::MessageNoAppCheck+0x47

597d6e14 twain!CDataSrc::IDataSrc+0xd0

597d58f6 twain!CDsm::registerDS+0x1b7

597d5ca3 twain!CDsm::registerDirDSs+0x163

597d5c87 twain!CDsm::registerDirDSs+0x147

597d5dc7 twain!CDsm::findAndRegisterDSs+0x85

597d5ed9 twain!CDsm::findClosestDefaultDS+0xcc

597d634d twain!CDsm::identityMsg+0x17e

597d6404 twain!CDsm::Message+0x91

597d8ec6 twain!DSM_Entry+0x102

0540605c unknown+0x0

119792d3 unknown+0x0

11979255 unknown+0x0

68991eab System_Windows_Forms_ni+0xa51eab

68120317 System_Windows_Forms_ni+0x1e0317

68136d71 System_Windows_Forms_ni+0x1f6d71

68136d1a System_Windows_Forms_ni+0x1f6d1a

68136b74 System_Windows_Forms_ni+0x1f6b74

68140207 System_Windows_Forms_ni+0x200207

Please advise when such exception happens...

re: Basic Debugging of an Application Crash

Dave — Wed, 11 Aug 2010 20:22:19 GMT

I have no time for MS Auto Updates.

After the override they did a couple of years ago to seemingly call WGA a "critical update" and override my settings to download, I have figured out a way to kill auto updates.

However, that does not seem to prevent XP Pro SP3 from trying every time I shut down, and sometimes in between, from doing an auto update.

Can you tell me how to extiguish any attempts by the OS from trying to auto update my computer?

You can't kill the update engines, as they are simply re-written into the system.

Tried that.

Killing permissions doesn't work, either.

All I want is to be able to go to the Auto Update Log File and see NOTHING attempted.

This is my computer, and I do NOT want MS trying to do what I tell it not to.

I get:

2010-08-10 00:00:50:204 436 c2c Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0700) ===========

2010-08-10 00:00:50:204 436 c2c Misc = Process: \??\C:\WINDOWS\SYSTEM32\winlogon.exe

2010-08-10 00:00:50:204 436 c2c Misc = Module: C:\WINDOWS\SYSTEM32\wuaueng.dll

2010-08-10 00:00:50:204 436 c2c Shutdwn FATAL: WUAutoUpdateAtShutdown failed, hr=80240FFF

which is realy weird as I shut down and was asleep an hour before that occurred.

I can't kill winlogon, and can't kill wuaueng, either.

Thank you.

re: Basic Debugging of an Application Crash

qwertylesh — Thu, 29 Oct 2009 13:08:51 GMT

Hi molotov

thank you immensely for the reply, many months ago albeit (sorry for such a late reply).

Next time I need to find the dump path, i'll check the LocalDump string as mentioned in the url you have provided. :)

kind regards.

qwertylesh

re: Basic Debugging of an Application Crash

molotov — Sat, 15 Aug 2009 02:44:59 GMT

Hi qwertylesh,

For Vista SP1+, check this out:

WER Settings @

http://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx

re: Basic Debugging of an Application Crash

qwertylesh — Wed, 12 Aug 2009 15:07:42 GMT

Hi MS Performance Team,

Your article does not mention (or ive missed it) an alternate path for the log or crash dump file for Vista users. Since all the user account paths are modified, the default path mentioned in the article only leads to a dynamic shortcut which disallows access without permissions modification.

I tried looking myself and will keep doing so, the closest path I can find is Drive:\Users\Name\AppData\Local\Microsoft\Windows\WER

However, still could not find more information or a crash dump (for my crashed application)

If you know please let me know it will be of great assistance to me.

qwertylesh

re: Basic Debugging of an Application Crash

Clark — Mon, 22 Jun 2009 12:43:00 GMT

This is awesomely helpful for a Windbg newbie!

Thank you!

Troubleshooting Server Hangs - Part One

Ask the Performance Team — Tue, 25 Sep 2007 17:04:24 GMT

Following on from our post on troubleshooting a basic application crash , it's time to start troubleshooting

Erasing drwtsn32.log

fx — Sat, 08 Sep 2007 13:22:50 GMT

I'd like to know what would happen if we delete the drwtsn32.log. Mine is actually 2.7Go (hum...it crashes sometimes) and I'm not able to visualize it anymore. SO the question is : may I delete this file.

Thank you so much for your reply,