MFC has stopped working error in Windows 7 32/64 bit

Question

Hi,

We are upgrading the application from VC++ 6.0 to VS2010. The application which is compiled in VS2010 works in Win XP but not working in Windows 7 32/64 bit. When I click the application .exe , it shows “MFC has stopped working”.  Below is the error dialog.

 When I see the win log in control panel, it shows the below error.

Faulting application name: GPS32.EXE, version: 5.0.0.0, time stamp: 0x4f4f5724

Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58

Exception code: 0xc0000374

Fault offset: 0x000ce653

Faulting process id: 0x1ab0

Faulting application start time: 0x01ccf8360bbb75eb

Faulting application path: C:\Program Files\GPS\GPS1400\GPS32.EXE

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: 4a4766ea-6429-11e1-bf83-5485fdadfc0d

Ntdll.dll is present in “C:\Windows\SysWOW64”.  Please help me to resolve the issue.

Regards,

Rani

---

Rani manickam

Answer 1

Have you tried to debug your software project under a Window 7 plattform? If your code is from VC6.0 there are so much possible whings that may happen problems. Also there are a lot changes in the OS since Windows XP.

Visual Studio 2010 has a great remote debugger, there is no need to install VS on all possible targets, only a network connection is eedet and the installation of the remote debuging tools.

 

Answer 2

Rani Manickam wrote:

>

>We are upgrading the application from VC++ 6.0 to VS2010. The application

>which is compiled in VS2010 works in Win XP but not working in Windows 7

>32/64 bit. When I click the application .exe , it shows “MFC has stopped

>working”.  Below is the error dialog.

>

>Faulting application name: GPS32.EXE, version: 5.0.0.0, time stamp: 0x4f4f5724

>Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58

>Exception code: 0xc0000374

>Fault offset: 0x000ce653

 

C0000374 is STATUS_HEAP_CORRUPTION.  You have overwritten heap memory

somewhere.  That is one of the most difficult errors to chase down.  Are

you calling into any custom drivers?  Are you using any system structures

and assuming that their size doesn't change from release to release?

--

Tim Roberts, [e-mail]

Providenza & Boekelheide, Inc.

 

---

Tim Roberts, VC++ MVP Providenza & Boekelheide, Inc.

Answer 3

Hi Tim,

Thanks for your reply.

I will debug my code then i will come back.

Regards,

Rani

---

Rani manickam