Access violation ... in module ntdll.dll

[Guest]

I am using Microsoft Vista Business edition. When I try to run an
application (my own) written for Windows XP, I get the message "Access
violation at address 7749B15F in module 'ntdll.dll'. Write of address
00000014". Any help, please?

 

[Guest]

Have you tried running your application in XP SP2 compatibility mode?

 

[Richard Urban]

http://search.microsoft.com/results...l&qsc0=0&FORM=QBME1&l=1&mkt=en-US&PageType=99

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Andrew McLaren]

I am using Microsoft Vista Business edition. When I try to run an
application (my own) written for Windows XP, I get the message "Access
violation at address 7749B15F in module 'ntdll.dll'. Write of address
00000014". Any help, please?

Hi Lames

When you say "your own" application - do you mean you wrote it yourself? If
so in what langauge? and what version Compiler did you use?

I hate to say it; but by far the most common cause of acccess violations is
a programming error. It's interesting that the application ran okay on XP
and crashes on Vista; but that doesn't necessarily mean Vista is at fault.
Often more recent versions demand greater accuracy from executing code; so
tha subtle bugs which went unnoticed before now hit the woodwork.

It's possible there's a bug in Vista - but it won't be in Ntdll.dll - that
is some of the most heavily exercised code on teh planet, a the very heary
of Windows.

If you wrote the app in C or C++, it's probably a bug in your own code. If
you're using some higher-level langauge, it may be a bug in the language
runtime.

If you wrote the app yourself you are probably familiar with debugging
techniques; if you use Visual Studio, see:
http://msdn2.microsoft.com/en-us/library/sc65sadd(VS.80).aspx
and the Access Violation section is here:
http://msdn2.microsoft.com/en-us/library/ac8kbaeh(vs.71).aspx

If you run the application under a debugger, you should be able to catch the
AV and debug it interactively.

Let us know how you get on ...

 

[Peter Foldes]

James

Did you try debugging your program . Does it also re-creates the same issue on another computer. Most likely scenarios would be a bad string in your program that does not recognize the newer GUI in Vista or a compability issue within Vista.

 

[Guest]

Thanks Mick - already have done that.