-
November 19th, 2009, 07:07 PM
#1
Application run well in Intel proccesor but it don't run in AMD processor
Hi people:
I have a windows application make in Visual C++ run well in Intel Proccesor but it crash in another same Windows XP OS with AMD Proccesor.
Any suggetions?
Tia,
jetm
-
November 19th, 2009, 07:32 PM
#2
Re: Application run well in Intel proccesor but it don't run in AMD processor
Originally Posted by jetm
I have a windows application make in Visual C++ run well in Intel Proccesor but it crash in another same Windows XP OS with AMD Proccesor.
Any suggetions?
Based on your input – stay away from AMD…
Seriously, what do you say in response to “My app crashed. Any suggestions?”
Did you try to debug this app on AMD?
Vlad - MS MVP [2007 - 2012] - www.FeinSoftware.com
Convenience and productivity tools for Microsoft Visual Studio:
FeinWindows - replacement windows manager for Visual Studio, and more...
-
November 19th, 2009, 07:40 PM
#3
Re: Application run well in Intel proccesor but it don't run in AMD processor
I'd be surprised if the processor is the reason for the crash.
-
November 19th, 2009, 11:04 PM
#4
Re: Application run well in Intel proccesor but it don't run in AMD processor
Originally Posted by jetm
Hi people:
I have a windows application make in Visual C++ run well in Intel Proccesor but it crash in another same Windows XP OS with AMD Proccesor.
Any suggetions?
Maybe it isn't the processor. It could be that the first computer faces east, while the other faces west.
Seriously, why are you blaming the processor? Maybe your app has a bug.
Regards,
Paul McKenzie
-
November 20th, 2009, 05:40 AM
#5
Re: Application run well in Intel proccesor but it don't run in AMD processor
Victor Nijegorodov
-
November 20th, 2009, 12:59 PM
#6
Re: Application run well in Intel proccesor but it don't run in AMD processor
That is the part when App crash:
Loaded "MIDIMAP.DLL" at address 0x77BD0000 by thread 1. Successfully hooked module.
DllMain(0x77BD0000, DLL_PROCESS_ATTACH, 0x00000000) in "MIDIMAP.DLL" called by thread 1.
DllMain(0x77BD0000, DLL_PROCESS_ATTACH, 0x00000000) in "MIDIMAP.DLL" returned 1 (0x1) by thread 1.
LoadLibraryW("midimap.dll") returned 0x77BD0000 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "DriverProc") called from "WINMM.DLL" at address 0x76B43034 and returned 0x77BD1317 by thread 1.
LoadLibraryW("midimap.dll") called from "WINMM.DLL" at address 0x76B43384 by thread 1.
LoadLibraryW("midimap.dll") returned 0x77BD0000 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "DriverProc") called from "WINMM.DLL" at address 0x76B43034 and returned 0x77BD1317 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "modMessage") called from "WINMM.DLL" at address 0x76B43AFA and returned 0x77BD2995 by thread 1.
LoadLibraryW("midimap.dll") called from "WINMM.DLL" at address 0x76B43384 by thread 1.
LoadLibraryW("midimap.dll") returned 0x77BD0000 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "DriverProc") called from "WINMM.DLL" at address 0x76B43034 and returned 0x77BD1317 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "midMessage") called from "WINMM.DLL" at address 0x76B43AFA and returned NULL by thread 1. Error: The specified procedure could not be found (127).
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "modMessage") called from "WINMM.DLL" at address 0x76B43AFA and returned 0x77BD2995 by thread 1.
LoadLibraryW("midimap.dll") called from "WINMM.DLL" at address 0x76B43384 by thread 1.
LoadLibraryW("midimap.dll") returned 0x77BD0000 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "DriverProc") called from "WINMM.DLL" at address 0x76B43034 and returned 0x77BD1317 by thread 1.
GetProcAddress(0x77BD0000 [MIDIMAP.DLL], "midMessage") called from "WINMM.DLL" at address 0x76B43AFA and returned NULL by thread 1. Error: The specified procedure could not be found (127).
Second chance exception 0xC0000005 (Access Violation) occurred in "LOCAL.EXE" at address 0x004DB996 by thread 1.
Thread 3 exited with code -1073741819 (0xC0000005).
Thread 2 exited with code -1073741819 (0xC0000005).
Exited "LOCAL.EXE" (process 0xC50) with code -1073741819 (0xC0000005) by thread 1.
-
November 20th, 2009, 01:07 PM
#7
Re: Application run well in Intel proccesor but it don't run in AMD processor
Originally Posted by jetm
That is the part when App crash:
Those errors have nothing to do with the processor.
If you read these messages, they clearly state that there are functions missing from WINMM.DLL and other DLL's that you are trying to access. Maybe on one computer the version of those DLL's are different than on the other computer.
And yes, your app has a bug (or at least a deficiency) -- it doesn't know what to do if the versions of the DLL's do not have those functions. It assumes those functions exist and just goes into hyperspace trying to call those non-existent functions. You should have a test if those functions are there or not -- if they are not there, log a message and exit gracefully, not hard crash.
Regards,
Paul McKenzie
Last edited by Paul McKenzie; November 20th, 2009 at 01:10 PM.
-
November 20th, 2009, 02:49 PM
#8
Re: Application run well in Intel proccesor but it don't run in AMD processor
I installed a clean and same Windows XP in a two PC with Intel and AMD processor severally, work fine in Intel but it don't AMD.
p.d: I don't have the source of Software.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|