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
