NTDLL.DLL - Access Violation

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • souravmallik
    New Member
    • May 2007
    • 11
    #1

    NTDLL.DLL - Access Violation

    Hello,

    I am using MS VC++ 6.0 in a win xp sp2 os. I'm getting a error NTDLL.DLL - 0xC00000005: Access Violation.

    Can any one tell me whats this error means?

    Is there any patch related problem. I'm not getting this error in all the machines. Is it related to the OS that executable is running..


    Please help..

    Thanks & Regards,

    Sourav Mallik.
    Tags: None
    • weaknessforcats
      Recognized Expert Expert
      • Mar 2007
      • 9214
      #2
      Most likely you are making a call to a function in that DLL using an ininitialized pointer.

        Comment

        • souravmallik
          New Member
          • May 2007
          • 11
          #3
          Originally posted by weaknessforcats
          Most likely you are making a call to a function in that DLL using an ininitialized pointer.
          Okya, so what I need to do.. as I'm not calling the function. I can see the dll being referenced from the call stack. But how can I solve it...

          Please help...

            Comment

            • weaknessforcats
              Recognized Expert Expert
              • Mar 2007
              • 9214
              #4
              Someone's calling a function in the DLL.

              At the point of failure, the access violation, can you see the call stack with your debugger?? That might be the clue here.

                Comment

                • Aniths
                  New Member
                  • Aug 2007
                  • 1
                  #5
                  Even i am facing a similar kind of problem.This is my stack info when the exeption occurs.And while debugging, i found that dynamic memory allocation is failing, and it gives an NTDLL access violation.Pls provide me with a solution.


                  NTDLL! 7c91b3fb()
                  NTDLL! 7c96d6aa()
                  NTDLL! 7c949d18()
                  NTDLL! 7c91b298()
                  _heap_alloc_bas e(unsigned int 34608) line 161
                  _heap_alloc_dbg (unsigned int 34560, int 1, const char * 0x00000000, int 0) line 367 + 9 bytes
                  _nh_malloc_dbg( unsigned int 34560, int 0, int 1, const char * 0x00000000, int 0) line 242 + 21 bytes
                  malloc(unsigned int 34560) line 130 + 21 bytes
                  Demod(double * 0x0004c4f0, unsigned long 47520, unsigned short * 0x0003b420, short * 0x0004b458, short * 0x0004b454) line 53 + 21 bytes
                  Dec(double * 0x014a0068, unsigned short 1) line 320 + 55 bytes
                  Rec(double * 0x00550040, unsigned long 51870) line 260 + 14 bytes
                  main_funct() line 69 + 13 bytes
                  main() line 31
                  mainCRTStartup( ) line 206 + 25 bytes
                  KERNEL32! 7c816fd7()

                    Comment

                    • weaknessforcats
                      Recognized Expert Expert
                      • Mar 2007
                      • 9214
                      #6
                      Originally posted by Aniths
                      malloc(unsigned int 34560) line 130 + 21 bytes
                      Demod(double * 0x0004c4f0, unsigned long 47520, unsigned short * 0x0003b420, short * 0x0004b458, short * 0x0004b454) line 53 + 21 bytes
                      It looks like a malloc() on line 130 of the Demod() function. Do you have a code snippet of that area?

                        Comment

                        • thanchu
                          New Member
                          • Dec 2009
                          • 2
                          #7
                          Maybe have leak memory in application

                            Comment

                            • thanchu
                              New Member
                              • Dec 2009
                              • 2
                              #8
                              You should check source code to find any pointer (ex, byte array) having out-of-range memory accesses.

                                Comment

                                Previous template Next
                                Working...