1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Error Message-"Run a DLL as an App has encountered a problem"

Discussion in 'Windows XP' started by mm0047, 2005/02/11.

Thread Status:
Not open for further replies.
  1. 2005/02/11
    mm0047

    mm0047 Inactive Thread Starter

    Joined:
    2004/06/02
    Messages:
    23
    Likes Received:
    0
    On startup I am now getting an error message - "Run a DLL as an App has encountered a problem and needs to close" - in the Microsoft Error window that allows the user to send an error report (or not). The machine appears to complete the startup process fine, and this message appears toward the process end. I have not added or removed any new software.

    Is there a clue to determining what is causing the error, and if so what is it?

    V/R,

    Mike
     
    mm0047,
    #1
  2. 2005/02/11
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Have you changed the hard drive? This refers to that message in that respect.

    I would run System File Checker ....

    Start > Run > sfc /scannow - note the space and have your XP CD handy. SFC will run and exit without any closing dialogue. To see which files. if any, have been replaced look in Event Viewer.
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2005/02/11
    mm0047

    mm0047 Inactive Thread Starter

    Joined:
    2004/06/02
    Messages:
    23
    Likes Received:
    0
    Thank you for your reply. I have not changed or worked with the hard drive in any way.

    I ran the System File Checker, but I have never used Event Viewer. How do I get there, and what should I look for once I do?

    V/R,

    Mike
     
    mm0047,
    #3
  5. 2005/02/11
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Did that fix the problem?

    To get to Event Viewer ....

    My Computer icon > right click > manage > Event Viewer > System

    This opens the Event Viewer for the System - see thumbnail (I use Classic View in XP - not Luna).

    For the most part the event messages are informative - double click on a message to open - you should see at least two stating that SFC started and SFC finished. In between there may be other messages relating to files replaced.

    While you are in Event Viewer look for any error messages flagged with a yellow exclamation mark or red x - these may give a clue as to the source of the problem on boot. Probably best to boot up - if the message appears go straight to Event Viewer and see if there is an error message flagged as above - look in both System and Application.

    If there are any relevant messages, double click on them to open and on the icon below the up/down arrows to copy to clipboard. You may paste them here.
     
    PeteC,
    #4
  6. 2005/02/11
    mm0047

    mm0047 Inactive Thread Starter

    Joined:
    2004/06/02
    Messages:
    23
    Likes Received:
    0
    Thanks again for your reply.

    (1) The SFC did not cure the problem.

    (2) I checked the log. The closest item I can find to SFC are 2 entries that tell me "Windows File Protection scan was started" and "Windows File Protection Scan completed successfully." There are no entries between the the two.

    (3) Here is the only Error message I have (Red "X "):

    Event Type: Error
    Event Source: DCOM
    Event Category: None
    Event ID: 10010
    Date: 2/11/2005
    Time: 3:23:17 PM
    User: MIKE1\Mike
    Computer: MIKE1
    Description:
    The server {001000AF-2DEF-0103-10B6-DC5BA692C858} did not register with DCOM within the required timeout.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Also, the Application log had this error message:

    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1000
    Date: 2/11/2005
    Time: 5:12:00 PM
    User: N/A
    Computer: MIKE1
    Description:
    Faulting application rundll32.exe, version 5.1.2600.2180, faulting module x10net.dll, version 2.0.0.40, fault address 0x000155b0.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 72 75 6e ure run
    0018: 64 6c 6c 33 32 2e 65 78 dll32.ex
    0020: 65 20 35 2e 31 2e 32 36 e 5.1.26
    0028: 30 30 2e 32 31 38 30 20 00.2180
    0030: 69 6e 20 78 31 30 6e 65 in x10ne
    0038: 74 2e 64 6c 6c 20 32 2e t.dll 2.
    0040: 30 2e 30 2e 34 30 20 61 0.0.40 a
    0048: 74 20 6f 66 66 73 65 74 t offset
    0050: 20 30 30 30 31 35 35 62 000155b
    0058: 30 0d 0a 0..





    Hope this helps.

    V/R,

    Mike
     
    Last edited: 2005/02/11
    mm0047,
    #5
  7. 2005/02/12
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    That's OK - no files were replaced.

    The Application Log error message holds the key to your problem ....
    Do you have an ATI Remote Control associated with an ATI video card? x10net.dll is a library file associated with that. See these Google hits and work through them if that is the case ....

    http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLD,GGLD:2004-18,GGLD:en&q=x10net.dll

    Reinstalling the software may solve the problem.
     
    PeteC,
    #6
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...