0

I'm getting the following error for my application on some machines. I'm wandering what the best methods are for debugging this issue - nothing is being logged so it looks like the fault is happening outside my codebase (no doubt caused by something I've done!)

Log Name: Application Source: Application Error Date: 25/01/2012 2:23:29 PM Event ID: 1000 Task Category: (100) Level: Error Keywords:
User: N/A Computer:
Description: Faulting application name:, version: 2.0.0.64, time stamp: 0x4f1f54ed Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e2111c0 Exception code: 0xe0434f4d Fault offset: 0x0000d36f Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13

Improve this question
4
  • 1
    support.microsoft.com/kb/911816 Commented Jan 25, 2012 at 9:19
  • If these machines reliably (not 5% of the time) generate this error, have you tried attaching a remote debugger on these machines? (if at all possible) This should give you atleast an idea as to where the problem might be. Also some more details wouldn't hurt, what does this app do, are you using P/Invokes, COM or are you perhaps hosted in another application, release or debug builds etc etc. Commented Jan 25, 2012 at 10:02
  • 1
    This is what happens when an app crashes because of an uncaught managed exception. The most common reason for a managed app to crash of course. Improve your error handling by writing an event handler for AppDomain.CurrentDomain.UnhandledException and log the value of e.ExceptionObject.ToString(). Almost always good enough to pin-point the problem. Commented Jan 25, 2012 at 14:09
  • Thanks Hans - the first two lines of code are the following: AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException); Application.ThreadException += new ThreadExceptionEventHandler(Application_ThreadException); I can't think of why it's not catching it. Commented Jan 25, 2012 at 14:49

1 Answer 1

Reset to default
1

Error code 0xe0434f4d is for CLR exceptions.

To debug, you may learn about crash dumps and WinDbg. Below is an example for ASP.NET, but if you know how to capture a crash dump for other kinds of .NET applications, the dump analysis workflow is the same,

http://blogs.msdn.com/b/tess/archive/2008/02/08/net-debugging-demos-lab-2-crash.aspx

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.