Windows Forum·65,707 discussions

MFC42.DLL – error

Locked

We installed two control systems last week with windows XP PRO as the OS. We are running our developed application under C++. The system is not beta but we did some changes to the code to accommodate some requests for the client.

We have two systems running side by side and we are noticing different errors. For one unit which had an isolated problem we opened the event log and two application errors were present:

module MFC42.DLL, address 0x00006A4C, and some are in an unknown module. MFC42 is the Microsoft Foundation Class, we assume.

The application hangs during an idle state and the client needs to close the application and reopen to initialize. Do you know of a way to use that address to pinpoint which function is causing the crash? We would welcome suggestions to troubleshoot this error.

The common error is caused 20% of the time when a function button is pressed. This was added while onsite. The application gets the standard windows error “We are sorry but….this application needs to close”. The client opened the details and the following information was present:

MDK MFC Application

MDK MFC Application has encountered a problem and needs to close.

Error Signature:

AppName: mdk.exe AppVer 1.0.0.1

ModName: mfc42.dll

ModVer: 6.2.4131.0

Offset: 00006a4c

Error report contents are:

Exception Information

Code: 0xc0000005

Flags: 0x00000000

Record: 0x0000000000000000

Address: 0x0000000073dd6a4c

System Information

I did not record the system info regarding the CPU.

Module 1

MDK.exe

Image Base: 0x00400000

Image Size: 0x00000000

Check Sum: 0x00000000

Time Stamp: 0x45ae8087

It looks like what is common is the mfc42.dll. If some can help, this would help us alot.

best regards,

Pierre

Topic

Clarifications

In reply to MFC42.DLL – error

Clarifications

Yes I can.

In reply to MFC42.DLL – error

Such types of errors are mostly application errors which have certain kind of implications in-built in them when they are designed. The best way to deal such a problem is to debug with windows debugger and pinpoint the exact location of the function causing this problem. The information you have specified is not sufficient to debug just by answering on this thread. You have to have WinDbg installed on your site, attach it to your MDK application and when it hangs, closely monitor the exceptions being produced in the WinDbg Command window. You can actually see the exact location of the problem. All you have to do is provide WinDbg the path of your source files, the program database files and the symbols files which you can pick from the Microsoft symbol server too.
I suggest you point this problem to someone skilled in debugging windows applications using WinDbg or Visual Studio 6.0 debugger.
For me, I am too involved in such skills as I am VC++ 6.0 with MFC programmer but it is not feasible for me to look into it as I am geographically located in India. I hope this direction would be quite helpful to you.

Regards,
Nitin

[Author]

Replies