I actually have 2 questions:
1. The first is understanding what can cause the faulty behavior (that crashed my app)
2. Given that I don't want to ask the forum each time I have these kind of errors, is there a troubleshooting guide\ error map that I can try to find the answers there? (what is the responsibility of kernelbase.dll anyway - that might interrupt with my app)
So the error I received in the event log is :
Faulting application name: TestingForm.vshost.exe, version: 10.0.30319.1, time stamp: 0x4ba2084b
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0xe06d7363
Fault offset: 0x0000b727
Faulting process id: 0x1d04
Faulting application start time: 0x01cc0b2a35966cd1
Faulting application path: C:\Users\user\Documents\Visual Studio 2010\Projects\AutoTrade\TestingForm\bin\Debug\TestingForm.vshost.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: c715828a-77eb-11e0-96a6-1c6f65864702
* I am running on 64bit OS, and the application running as 32bit(compiled on x86).
* The application was running for 2 days
* I am also using "logmein" to checkout the machine once in a while.
Any help is welcome.
-ASunday, May 08, 2011 8:24 AM
According to event log, the crashed application is "xxx.vshost.exe" which is hosting process. Well, the VS host process is always used to improves debugger performance. Have you tried to run "xxx.exe" instead of "xxx.vshost.exe"?
Paul Zhou [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Tuesday, May 24, 2011 6:41 AM
This is a know issue of 64 system running a 32 bit compiled application. If your issue is specific to a 64 bit system. You can compile your application with “Any CPU” option which should resolve your issue solve.
There is hot fix from Microsoft as well @ http://support.microsoft.com/kb/2077754 - I am not sure if that will help you.
Starting from .net 4.0, to handle exceptions that indicate a corrupted/Faulty process state you can use HandleProcessCorruptedStateExceptionsAttribute.
Friday, October 19, 2012 5:52 AM
- Proposed as answer by Wegsley Sunday, November 25, 2012 10:52 AM