CODEWITHSUNDEEP
c#winforms
Binayacharya
Binayacharya

Reputation: 104

C# windows application crashing suddenly without any error message

My application started crashing suddenly without any proper message.

The application was built in ANY CPU and was running on 64 bit machine.

At the time of crash, it was using around 1.5GB of memory.

The project is storing it all operational process in SQLCe4.0 as back-end database and the project size was almost around 2.8 GB.

When I checked Windows event viewer the message was like this :

Problem signature: 
  Problem Event Name: APPCRASH 
  Application Name: MyApp.exe 
  Application Version: 2.7.710.1137 
  Application Timestamp: 51dcf6b1 
  **Fault Module Name: StackHash_6bac** 
  Fault Module Version: 0.0.0.0 
  Fault Module Timestamp: 00000000 
  Exception Code: c0000005 
  Exception Offset: 000000007782000a 
  OS Version: 6.1.7601.2.1.0.256.1 
  Locale ID: 1033 
  Additional Information 1: 6bac 
  Additional Information 2: 6bac59273bcf6f09b20009b5873b0c76 
  Additional Information 3: 2600 
  Additional Information 4: 2600c3cc88a8c9bf041ae82fe9962258

Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline: 

C:\Windows\system32\en-US\erofflps.txt

I am unable to figure out what is the exact cause of failure.

Any help will be appreciated.

Upvotes: 4

Views: 3785

Answers (1)

pabdulin
pabdulin

Reputation: 35255

Exception Code: c0000005 is a ACCESS_VIOLATION, that is your program is trying to access region of memory outside it's own. Fault Module Name: StackHash_6bac means that no module was loaded on fault address:

The answer is that the Windows executive couldn’t identify the module we were in when the application crashed (it uses the instruction pointer to determine what code was executing). In this case, the kernel simply takes a hash of the stack so at least we might be able to identify if we’ve seen this exact crash before. Here’s the answer summarized by an engineer from Microsoft:

In the OS when I try to get a faulting module name it is possible that there is no module laoded (sic) at that address. For example in this case the EIP was zero. So in those cases where a module is not loaded and it is not also in the unloaded module list, I take a stack hash of the stack so that we can identify this crash from other crashes where also the module is not known.

Given all that, most probably you are experiencing some resource leak, which eventually leads to this access violation error.

Upvotes: 6

Related Questions