.NET Runtime 2.0 Error faulting module ntdll.dll

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • mpbejo
    New Member
    • Apr 2007
    • 1
    #1

    .NET Runtime 2.0 Error faulting module ntdll.dll

    I have an application developed with VisualBasic 2005 that use .Net Framework 2.0. This application works 24 Hours day, 7 days at week. It works fine but sometimes (every two/three days) the application crash on the event viewer I see:

    .NET Runtime 2.0 Error
    Category: nothing
    ID event: 1000
    Faulting application plate_reader.ex e, version 1.0.0.0, stamp 45f6a516, faulting module ntdll.dll, version 5.1.2600.2180, stamp 41252c01, debug? 0, fault address 0x0001142e.

    The application is a plate reader, the application receive images from a camera, the image is converted to text, on a another pc there is a sql2000 server with a database, the application run a query to find the text on the database, if found the application send, via RS485 (COM3) a command to a module ADAM 4060 that open a "door", if the plate is not recognized it is possible to press a button this signal goes to a module ADAM 4052 and send to the computer via RS485 (COM4) the application intercepts this, and send an alarm to the control room so they can decide to open or not. All this operations are executed by a timer every 250ms. The timer is set to false when starts the commands enad set true to the finish
    Please help me thank You
    Tags: None
    • Killer42
      Recognized Expert Expert
      • Oct 2006
      • 8429
      #2
      I'm going to move this from the VB to the .Net forum, as it seems more appropriate, and I believe you'll find more help there.

      I would like to ask, though... since this sounds like it could be some kind of resource leak, do you know much about the crash? For example...
      • Have you searched for anything which may be created/loaded and not released?
      • Do you know where the program crashes?
      • Is it consistent?
      • Do you have some sort of logging in place (or can you add it without too much drama) to track exactly where the code is when it fails? This might add some overhead in CPU and/or IO, but could help in tracking what's going on.
      • Could you perhaps run the program in the design environment (for two or three days if necessary) to enable debugging if/when it crashes?
      • Have you tried to check for any other similarities between the crashes? For example, perhaps it's always the same "plate".

      I’m afraid I don’t know what debugging facilities are available for VB.Net code.

        Comment

        Previous template Next
        Working...