Windows Vista Forums

APPCRASH - fault module NTDLL.DLL!

  1. #1


    civ2ru Guest

    APPCRASH - fault module NTDLL.DLL!

    Hello,

    First off, I run Vista Home Premium 32-bit. In the past several months I've
    started receiving error messages when my computer recovers from Sleep Mode. I
    don't remember when it started and I can't roll back that far. Various
    programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    working" and most of them indicate ntdll.dll as the faulting module (see
    event viewer logs included below). Please help!
    ----------
    Log Name: Application
    Source: Application Error
    Date: 7/22/2008 11:20:48 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: ...
    Description:
    Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp
    0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
    0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id
    0x824, application start time 0x01c8eb384724f9be.
    ----------
    Log Name: Application
    Source: Application Error
    Date: 8/16/2008 12:27:11 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: ...
    Description:
    Faulting application wmplayer.exe, version 11.0.6001.7000, time stamp
    0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
    0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a, process id
    0x1510, application start time 0x01c8ffc54e67ba00.
    ----------
    Log Name: Application
    Source: Application Error
    Date: 8/9/2008 8:49:01 AM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: ...
    Description:
    Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
    0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8, process id
    0x1538, application start time 0x01c8fa26a95e4d10.

      My System SpecsSystem Spec

  2.   


  3. #2


    meerkat Guest

    Re: APPCRASH - fault module NTDLL.DLL!


    "civ2ru" <civ2ru@xxxxxx> wrote in message
    news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx

    > Hello,
    >
    > First off, I run Vista Home Premium 32-bit. In the past several months
    > I've
    > started receiving error messages when my computer recovers from Sleep
    > Mode. I
    > don't remember when it started and I can't roll back that far. Various
    > programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    > working" and most of them indicate ntdll.dll as the faulting module (see
    > event viewer logs included below). Please help!
    >
    You need to try a System file Check.
    Go to the start button.
    In the Search Panel type... CMD.
    At the top of that column CMD.exe will appear.
    Right click on it, and select Run as Administrator.
    The Command window will appear.

    In the command window type...SFC /scannow
    (note the space between C and /, and the 2 letters n)
    This will perform a system file test, to ensure all your system files
    are OK.
    Then Restart your machine.

    bw..



      My System SpecsSystem Spec

  4. #3


    zachd [MSFT] Guest

    Re: APPCRASH - fault module NTDLL.DLL!


    Event Viewer notes are slightly inferior to the Problem Reports and
    Solutions Center control panel's View Problem History for those crashes.

    The first crash is from your old system pre-upgrade to SP1, likely
    indicating that memory corruption has occurred. There's a variety of
    potential suspects, but since you've upgraded, that's not 100% relevant any
    longer.

    The second crash: are palmusbdirect.dll or slacker.shared.dll on your
    system?

    The third crash: if you use the Problem Reports and Solutions Center to
    check for solutions, you should already be getting a notification here that
    your Office is out of date. Does updating per that help?


    All of the crashes are a little too generic to be analyzed just based upon
    that data. The actual crash DMP files might be interesting to look at, but
    the below data likely could not lead to any direct solution by itself.

    --
    Speaking for myself only.
    See http://zachd.com/pss/pss.html for some helpful WMP info.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --
    "civ2ru" <civ2ru@xxxxxx> wrote in message
    news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx

    > Hello,
    >
    > First off, I run Vista Home Premium 32-bit. In the past several months
    > I've
    > started receiving error messages when my computer recovers from Sleep
    > Mode. I
    > don't remember when it started and I can't roll back that far. Various
    > programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    > working" and most of them indicate ntdll.dll as the faulting module (see
    > event viewer logs included below). Please help!
    > ----------
    > Log Name: Application
    > Source: Application Error
    > Date: 7/22/2008 11:20:48 PM
    > Event ID: 1000
    > Task Category: (100)
    > Level: Error
    > Keywords: Classic
    > User: N/A
    > Computer: ...
    > Description:
    > Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp
    > 0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
    > 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id
    > 0x824, application start time 0x01c8eb384724f9be.
    > ----------
    > Log Name: Application
    > Source: Application Error
    > Date: 8/16/2008 12:27:11 PM
    > Event ID: 1000
    > Task Category: (100)
    > Level: Error
    > Keywords: Classic
    > User: N/A
    > Computer: ...
    > Description:
    > Faulting application wmplayer.exe, version 11.0.6001.7000, time stamp
    > 0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
    > 0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a, process id
    > 0x1510, application start time 0x01c8ffc54e67ba00.
    > ----------
    > Log Name: Application
    > Source: Application Error
    > Date: 8/9/2008 8:49:01 AM
    > Event ID: 1000
    > Task Category: (100)
    > Level: Error
    > Keywords: Classic
    > User: N/A
    > Computer: ...
    > Description:
    > Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    > 0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
    > 0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8, process id
    > 0x1538, application start time 0x01c8fa26a95e4d10.


      My System SpecsSystem Spec

  5. #4


    civ2ru Guest

    Re: APPCRASH - fault module NTDLL.DLL!

    Zach - thank you so much for taking the time to answer!

    Funny you should ask about palmusbdirect.dll - yes, I have that file and
    been getting some crashes on its account as well. Should I try removing it or
    moving to a different folder?

    As for ntdll.dll and Problem Reports and Solutions logs, how about this one?
    Does it shed any more light?
    ----------
    Product
    Windows Media Player

    Problem
    Stopped working

    Date
    8/15/2008 12:10 PM

    Status
    Report Sent

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: wmplayer.exe
    Application Version: 11.0.6001.7000
    Application Timestamp: 47919356
    Fault Module Name: ntdll.dll
    Fault Module Version: 6.0.6001.18000
    Fault Module Timestamp: 4791a7a6
    Exception Code: c0000005
    Exception Offset: 0003d02b
    OS Version: 6.0.6001.2.1.0.768.3
    Locale ID: 1033
    Additional Information 1: bfef
    Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
    Additional Information 3: bfef
    Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863

    Extra information about the problem
    Bucket ID: 649592584

    "zachd [MSFT]" wrote:

    >
    > Event Viewer notes are slightly inferior to the Problem Reports and
    > Solutions Center control panel's View Problem History for those crashes.
    >
    > The first crash is from your old system pre-upgrade to SP1, likely
    > indicating that memory corruption has occurred. There's a variety of
    > potential suspects, but since you've upgraded, that's not 100% relevant any
    > longer.
    >
    > The second crash: are palmusbdirect.dll or slacker.shared.dll on your
    > system?
    >
    > The third crash: if you use the Problem Reports and Solutions Center to
    > check for solutions, you should already be getting a notification here that
    > your Office is out of date. Does updating per that help?
    >
    >
    > All of the crashes are a little too generic to be analyzed just based upon
    > that data. The actual crash DMP files might be interesting to look at, but
    > the below data likely could not lead to any direct solution by itself.
    >
    > --
    > Speaking for myself only.
    > See http://zachd.com/pss/pss.html for some helpful WMP info.
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    > --
    > "civ2ru" <civ2ru@xxxxxx> wrote in message
    > news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx

    > > Hello,
    > >
    > > First off, I run Vista Home Premium 32-bit. In the past several months
    > > I've
    > > started receiving error messages when my computer recovers from Sleep
    > > Mode. I
    > > don't remember when it started and I can't roll back that far. Various
    > > programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    > > working" and most of them indicate ntdll.dll as the faulting module (see
    > > event viewer logs included below). Please help!
    > > ----------
    > > Log Name: Application
    > > Source: Application Error
    > > Date: 7/22/2008 11:20:48 PM
    > > Event ID: 1000
    > > Task Category: (100)
    > > Level: Error
    > > Keywords: Classic
    > > User: N/A
    > > Computer: ...
    > > Description:
    > > Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp
    > > 0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
    > > 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id
    > > 0x824, application start time 0x01c8eb384724f9be.
    > > ----------
    > > Log Name: Application
    > > Source: Application Error
    > > Date: 8/16/2008 12:27:11 PM
    > > Event ID: 1000
    > > Task Category: (100)
    > > Level: Error
    > > Keywords: Classic
    > > User: N/A
    > > Computer: ...
    > > Description:
    > > Faulting application wmplayer.exe, version 11.0.6001.7000, time stamp
    > > 0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
    > > 0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a, process id
    > > 0x1510, application start time 0x01c8ffc54e67ba00.
    > > ----------
    > > Log Name: Application
    > > Source: Application Error
    > > Date: 8/9/2008 8:49:01 AM
    > > Event ID: 1000
    > > Task Category: (100)
    > > Level: Error
    > > Keywords: Classic
    > > User: N/A
    > > Computer: ...
    > > Description:
    > > Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    > > 0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time stamp
    > > 0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8, process id
    > > 0x1538, application start time 0x01c8fa26a95e4d10.
    >
    >
    >

      My System SpecsSystem Spec

  6. #5


    civ2ru Guest

    Re: APPCRASH - fault module NTDLL.DLL!

    Meerkat - thank you for the reply!

    Already tried system scan yesterday and it seemed to have found corrupt
    files it couldn't fix. Ran it again just now and the verdict was "did not
    find any integrity violations". Go figure... Will keep my fingers crossed.

    "meerkat" wrote:

    >
    > You need to try a System file Check.
    > Go to the start button.
    > In the Search Panel type... CMD.
    > At the top of that column CMD.exe will appear.
    > Right click on it, and select Run as Administrator.
    > The Command window will appear.
    >
    > In the command window type...SFC /scannow
    > (note the space between C and /, and the 2 letters n)
    > This will perform a system file test, to ensure all your system files
    > are OK.
    > Then Restart your machine.
    >
    > bw..
    >
    >
    >

      My System SpecsSystem Spec

  7. #6


    zachd [MSFT] Guest

    Re: APPCRASH - fault module NTDLL.DLL!


    I would suspect that either updating or uninstalling that DLL would indeed
    have a positive effect here. Does it?

    --
    Speaking for myself only.
    See http://zachd.com/pss/pss.html for some helpful WMP info.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --
    "civ2ru" <civ2ru@xxxxxx> wrote in message
    news:53D348EE-23E9-494B-8DA2-EDF08040CF02@xxxxxx

    > Zach - thank you so much for taking the time to answer!
    >
    > Funny you should ask about palmusbdirect.dll - yes, I have that file and
    > been getting some crashes on its account as well. Should I try removing it
    > or
    > moving to a different folder?
    >
    > As for ntdll.dll and Problem Reports and Solutions logs, how about this
    > one?
    > Does it shed any more light?
    > ----------
    > Product
    > Windows Media Player
    >
    > Problem
    > Stopped working
    >
    > Date
    > 8/15/2008 12:10 PM
    >
    > Status
    > Report Sent
    >
    > Problem signature
    > Problem Event Name: APPCRASH
    > Application Name: wmplayer.exe
    > Application Version: 11.0.6001.7000
    > Application Timestamp: 47919356
    > Fault Module Name: ntdll.dll
    > Fault Module Version: 6.0.6001.18000
    > Fault Module Timestamp: 4791a7a6
    > Exception Code: c0000005
    > Exception Offset: 0003d02b
    > OS Version: 6.0.6001.2.1.0.768.3
    > Locale ID: 1033
    > Additional Information 1: bfef
    > Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
    > Additional Information 3: bfef
    > Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863
    >
    > Extra information about the problem
    > Bucket ID: 649592584
    >
    > "zachd [MSFT]" wrote:
    >

    >>
    >> Event Viewer notes are slightly inferior to the Problem Reports and
    >> Solutions Center control panel's View Problem History for those crashes.
    >>
    >> The first crash is from your old system pre-upgrade to SP1, likely
    >> indicating that memory corruption has occurred. There's a variety of
    >> potential suspects, but since you've upgraded, that's not 100% relevant
    >> any
    >> longer.
    >>
    >> The second crash: are palmusbdirect.dll or slacker.shared.dll on your
    >> system?
    >>
    >> The third crash: if you use the Problem Reports and Solutions Center to
    >> check for solutions, you should already be getting a notification here
    >> that
    >> your Office is out of date. Does updating per that help?
    >>
    >>
    >> All of the crashes are a little too generic to be analyzed just based
    >> upon
    >> that data. The actual crash DMP files might be interesting to look at,
    >> but
    >> the below data likely could not lead to any direct solution by itself.
    >>
    >> --
    >> Speaking for myself only.
    >> See http://zachd.com/pss/pss.html for some helpful WMP info.
    >> This posting is provided "AS IS" with no warranties, and confers no
    >> rights.
    >> --
    >> "civ2ru" <civ2ru@xxxxxx> wrote in message
    >> news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx

    >> > Hello,
    >> >
    >> > First off, I run Vista Home Premium 32-bit. In the past several months
    >> > I've
    >> > started receiving error messages when my computer recovers from Sleep
    >> > Mode. I
    >> > don't remember when it started and I can't roll back that far. Various
    >> > programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    >> > working" and most of them indicate ntdll.dll as the faulting module
    >> > (see
    >> > event viewer logs included below). Please help!
    >> > ----------
    >> > Log Name: Application
    >> > Source: Application Error
    >> > Date: 7/22/2008 11:20:48 PM
    >> > Event ID: 1000
    >> > Task Category: (100)
    >> > Level: Error
    >> > Keywords: Classic
    >> > User: N/A
    >> > Computer: ...
    >> > Description:
    >> > Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp
    >> > 0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time
    >> > stamp
    >> > 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process
    >> > id
    >> > 0x824, application start time 0x01c8eb384724f9be.
    >> > ----------
    >> > Log Name: Application
    >> > Source: Application Error
    >> > Date: 8/16/2008 12:27:11 PM
    >> > Event ID: 1000
    >> > Task Category: (100)
    >> > Level: Error
    >> > Keywords: Classic
    >> > User: N/A
    >> > Computer: ...
    >> > Description:
    >> > Faulting application wmplayer.exe, version 11.0.6001.7000, time stamp
    >> > 0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time
    >> > stamp
    >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a, process
    >> > id
    >> > 0x1510, application start time 0x01c8ffc54e67ba00.
    >> > ----------
    >> > Log Name: Application
    >> > Source: Application Error
    >> > Date: 8/9/2008 8:49:01 AM
    >> > Event ID: 1000
    >> > Task Category: (100)
    >> > Level: Error
    >> > Keywords: Classic
    >> > User: N/A
    >> > Computer: ...
    >> > Description:
    >> > Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    >> > 0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time
    >> > stamp
    >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8, process
    >> > id
    >> > 0x1538, application start time 0x01c8fa26a95e4d10.
    >>
    >>
    >>

      My System SpecsSystem Spec

  8. #7


    civ2ru Guest

    Re: APPCRASH - fault module NTDLL.DLL!

    How does one UNINSTALL the DLL?

    "zachd [MSFT]" wrote:

    >
    > I would suspect that either updating or uninstalling that DLL would indeed
    > have a positive effect here. Does it?
    >
    > --
    > Speaking for myself only.
    > See http://zachd.com/pss/pss.html for some helpful WMP info.
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    > --
    > "civ2ru" <civ2ru@xxxxxx> wrote in message
    > news:53D348EE-23E9-494B-8DA2-EDF08040CF02@xxxxxx

    > > Zach - thank you so much for taking the time to answer!
    > >
    > > Funny you should ask about palmusbdirect.dll - yes, I have that file and
    > > been getting some crashes on its account as well. Should I try removing it
    > > or
    > > moving to a different folder?
    > >
    > > As for ntdll.dll and Problem Reports and Solutions logs, how about this
    > > one?
    > > Does it shed any more light?
    > > ----------
    > > Product
    > > Windows Media Player
    > >
    > > Problem
    > > Stopped working
    > >
    > > Date
    > > 8/15/2008 12:10 PM
    > >
    > > Status
    > > Report Sent
    > >
    > > Problem signature
    > > Problem Event Name: APPCRASH
    > > Application Name: wmplayer.exe
    > > Application Version: 11.0.6001.7000
    > > Application Timestamp: 47919356
    > > Fault Module Name: ntdll.dll
    > > Fault Module Version: 6.0.6001.18000
    > > Fault Module Timestamp: 4791a7a6
    > > Exception Code: c0000005
    > > Exception Offset: 0003d02b
    > > OS Version: 6.0.6001.2.1.0.768.3
    > > Locale ID: 1033
    > > Additional Information 1: bfef
    > > Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
    > > Additional Information 3: bfef
    > > Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863
    > >
    > > Extra information about the problem
    > > Bucket ID: 649592584
    > >
    > > "zachd [MSFT]" wrote:
    > >

    > >>
    > >> Event Viewer notes are slightly inferior to the Problem Reports and
    > >> Solutions Center control panel's View Problem History for those crashes.
    > >>
    > >> The first crash is from your old system pre-upgrade to SP1, likely
    > >> indicating that memory corruption has occurred. There's a variety of
    > >> potential suspects, but since you've upgraded, that's not 100% relevant
    > >> any
    > >> longer.
    > >>
    > >> The second crash: are palmusbdirect.dll or slacker.shared.dll on your
    > >> system?
    > >>
    > >> The third crash: if you use the Problem Reports and Solutions Center to
    > >> check for solutions, you should already be getting a notification here
    > >> that
    > >> your Office is out of date. Does updating per that help?
    > >>
    > >>
    > >> All of the crashes are a little too generic to be analyzed just based
    > >> upon
    > >> that data. The actual crash DMP files might be interesting to look at,
    > >> but
    > >> the below data likely could not lead to any direct solution by itself.
    > >>
    > >> --
    > >> Speaking for myself only.
    > >> See http://zachd.com/pss/pss.html for some helpful WMP info.
    > >> This posting is provided "AS IS" with no warranties, and confers no
    > >> rights.
    > >> --
    > >> "civ2ru" <civ2ru@xxxxxx> wrote in message
    > >> news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx
    > >> > Hello,
    > >> >
    > >> > First off, I run Vista Home Premium 32-bit. In the past several months
    > >> > I've
    > >> > started receiving error messages when my computer recovers from Sleep
    > >> > Mode. I
    > >> > don't remember when it started and I can't roll back that far. Various
    > >> > programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    > >> > working" and most of them indicate ntdll.dll as the faulting module
    > >> > (see
    > >> > event viewer logs included below). Please help!
    > >> > ----------
    > >> > Log Name: Application
    > >> > Source: Application Error
    > >> > Date: 7/22/2008 11:20:48 PM
    > >> > Event ID: 1000
    > >> > Task Category: (100)
    > >> > Level: Error
    > >> > Keywords: Classic
    > >> > User: N/A
    > >> > Computer: ...
    > >> > Description:
    > >> > Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp
    > >> > 0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time
    > >> > stamp
    > >> > 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process
    > >> > id
    > >> > 0x824, application start time 0x01c8eb384724f9be.
    > >> > ----------
    > >> > Log Name: Application
    > >> > Source: Application Error
    > >> > Date: 8/16/2008 12:27:11 PM
    > >> > Event ID: 1000
    > >> > Task Category: (100)
    > >> > Level: Error
    > >> > Keywords: Classic
    > >> > User: N/A
    > >> > Computer: ...
    > >> > Description:
    > >> > Faulting application wmplayer.exe, version 11.0.6001.7000, time stamp
    > >> > 0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time
    > >> > stamp
    > >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a, process
    > >> > id
    > >> > 0x1510, application start time 0x01c8ffc54e67ba00.
    > >> > ----------
    > >> > Log Name: Application
    > >> > Source: Application Error
    > >> > Date: 8/9/2008 8:49:01 AM
    > >> > Event ID: 1000
    > >> > Task Category: (100)
    > >> > Level: Error
    > >> > Keywords: Classic
    > >> > User: N/A
    > >> > Computer: ...
    > >> > Description:
    > >> > Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    > >> > 0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time
    > >> > stamp
    > >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8, process
    > >> > id
    > >> > 0x1538, application start time 0x01c8fa26a95e4d10.
    > >>
    > >>
    > >>
    >
    >

      My System SpecsSystem Spec

  9. #8


    zachd [MSFT] Guest

    Re: APPCRASH - fault module NTDLL.DLL!


    I don't have it on my system so I don't know what software it came with. By
    the file name, "Palm" may be the relevant software provider. If you check
    the File Properties on the DLL, that may indicate why provided it to you,
    which may lead you to people who know how to better trouble-shoot it or know
    what install package was installed to your system that included it. Since I
    never installed that file, you would unfortunately be in a better position
    to know how it got there which directly correlates to what install package
    you might at this time want to try temporarily uninstalling.

    Of course, you could also just rename or remove the DLL, but that's an
    inferior plan.

    --
    Speaking for myself only.
    See http://zachd.com/pss/pss.html for some helpful WMP info.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --
    "civ2ru" <civ2ru@xxxxxx> wrote in message
    news:41049AC0-C270-4EA2-977C-5B7408845F1E@xxxxxx

    > How does one UNINSTALL the DLL?
    >
    > "zachd [MSFT]" wrote:
    >

    >>
    >> I would suspect that either updating or uninstalling that DLL would
    >> indeed
    >> have a positive effect here. Does it?
    >>
    >> --
    >> Speaking for myself only.
    >> See http://zachd.com/pss/pss.html for some helpful WMP info.
    >> This posting is provided "AS IS" with no warranties, and confers no
    >> rights.
    >> --
    >> "civ2ru" <civ2ru@xxxxxx> wrote in message
    >> news:53D348EE-23E9-494B-8DA2-EDF08040CF02@xxxxxx

    >> > Zach - thank you so much for taking the time to answer!
    >> >
    >> > Funny you should ask about palmusbdirect.dll - yes, I have that file
    >> > and
    >> > been getting some crashes on its account as well. Should I try removing
    >> > it
    >> > or
    >> > moving to a different folder?
    >> >
    >> > As for ntdll.dll and Problem Reports and Solutions logs, how about this
    >> > one?
    >> > Does it shed any more light?
    >> > ----------
    >> > Product
    >> > Windows Media Player
    >> >
    >> > Problem
    >> > Stopped working
    >> >
    >> > Date
    >> > 8/15/2008 12:10 PM
    >> >
    >> > Status
    >> > Report Sent
    >> >
    >> > Problem signature
    >> > Problem Event Name: APPCRASH
    >> > Application Name: wmplayer.exe
    >> > Application Version: 11.0.6001.7000
    >> > Application Timestamp: 47919356
    >> > Fault Module Name: ntdll.dll
    >> > Fault Module Version: 6.0.6001.18000
    >> > Fault Module Timestamp: 4791a7a6
    >> > Exception Code: c0000005
    >> > Exception Offset: 0003d02b
    >> > OS Version: 6.0.6001.2.1.0.768.3
    >> > Locale ID: 1033
    >> > Additional Information 1: bfef
    >> > Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
    >> > Additional Information 3: bfef
    >> > Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863
    >> >
    >> > Extra information about the problem
    >> > Bucket ID: 649592584
    >> >
    >> > "zachd [MSFT]" wrote:
    >> >
    >> >>
    >> >> Event Viewer notes are slightly inferior to the Problem Reports and
    >> >> Solutions Center control panel's View Problem History for those
    >> >> crashes.
    >> >>
    >> >> The first crash is from your old system pre-upgrade to SP1, likely
    >> >> indicating that memory corruption has occurred. There's a variety of
    >> >> potential suspects, but since you've upgraded, that's not 100%
    >> >> relevant
    >> >> any
    >> >> longer.
    >> >>
    >> >> The second crash: are palmusbdirect.dll or slacker.shared.dll on your
    >> >> system?
    >> >>
    >> >> The third crash: if you use the Problem Reports and Solutions Center
    >> >> to
    >> >> check for solutions, you should already be getting a notification here
    >> >> that
    >> >> your Office is out of date. Does updating per that help?
    >> >>
    >> >>
    >> >> All of the crashes are a little too generic to be analyzed just based
    >> >> upon
    >> >> that data. The actual crash DMP files might be interesting to look
    >> >> at,
    >> >> but
    >> >> the below data likely could not lead to any direct solution by itself.
    >> >>
    >> >> --
    >> >> Speaking for myself only.
    >> >> See http://zachd.com/pss/pss.html for some helpful WMP info.
    >> >> This posting is provided "AS IS" with no warranties, and confers no
    >> >> rights.
    >> >> --
    >> >> "civ2ru" <civ2ru@xxxxxx> wrote in message
    >> >> news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx
    >> >> > Hello,
    >> >> >
    >> >> > First off, I run Vista Home Premium 32-bit. In the past several
    >> >> > months
    >> >> > I've
    >> >> > started receiving error messages when my computer recovers from
    >> >> > Sleep
    >> >> > Mode. I
    >> >> > don't remember when it started and I can't roll back that far.
    >> >> > Various
    >> >> > programs - explorer.exe, wmplayer.exe, outlook.exe and others -
    >> >> > "stop
    >> >> > working" and most of them indicate ntdll.dll as the faulting module
    >> >> > (see
    >> >> > event viewer logs included below). Please help!
    >> >> > ----------
    >> >> > Log Name: Application
    >> >> > Source: Application Error
    >> >> > Date: 7/22/2008 11:20:48 PM
    >> >> > Event ID: 1000
    >> >> > Task Category: (100)
    >> >> > Level: Error
    >> >> > Keywords: Classic
    >> >> > User: N/A
    >> >> > Computer: ...
    >> >> > Description:
    >> >> > Faulting application Explorer.EXE, version 6.0.6000.16549, time
    >> >> > stamp
    >> >> > 0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time
    >> >> > stamp
    >> >> > 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9,
    >> >> > process
    >> >> > id
    >> >> > 0x824, application start time 0x01c8eb384724f9be.
    >> >> > ----------
    >> >> > Log Name: Application
    >> >> > Source: Application Error
    >> >> > Date: 8/16/2008 12:27:11 PM
    >> >> > Event ID: 1000
    >> >> > Task Category: (100)
    >> >> > Level: Error
    >> >> > Keywords: Classic
    >> >> > User: N/A
    >> >> > Computer: ...
    >> >> > Description:
    >> >> > Faulting application wmplayer.exe, version 11.0.6001.7000, time
    >> >> > stamp
    >> >> > 0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time
    >> >> > stamp
    >> >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a,
    >> >> > process
    >> >> > id
    >> >> > 0x1510, application start time 0x01c8ffc54e67ba00.
    >> >> > ----------
    >> >> > Log Name: Application
    >> >> > Source: Application Error
    >> >> > Date: 8/9/2008 8:49:01 AM
    >> >> > Event ID: 1000
    >> >> > Task Category: (100)
    >> >> > Level: Error
    >> >> > Keywords: Classic
    >> >> > User: N/A
    >> >> > Computer: ...
    >> >> > Description:
    >> >> > Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    >> >> > 0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time
    >> >> > stamp
    >> >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8,
    >> >> > process
    >> >> > id
    >> >> > 0x1538, application start time 0x01c8fa26a95e4d10.
    >> >>
    >> >>
    >> >>
    >>
    >>

      My System SpecsSystem Spec

  10. #9


    zachd [MSFT] Guest

    Re: APPCRASH - fault module NTDLL.DLL!


    This second crash bucket also is most correlated to palmusbdirect.dll. What
    are the file properties of that file?
    Is oehook.dll on your system?

    --
    Speaking for myself only.
    See http://zachd.com/pss/pss.html for some helpful WMP info.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --
    "civ2ru" <civ2ru@xxxxxx> wrote in message
    news:53D348EE-23E9-494B-8DA2-EDF08040CF02@xxxxxx

    > Zach - thank you so much for taking the time to answer!
    >
    > Funny you should ask about palmusbdirect.dll - yes, I have that file and
    > been getting some crashes on its account as well. Should I try removing it
    > or
    > moving to a different folder?
    >
    > As for ntdll.dll and Problem Reports and Solutions logs, how about this
    > one?
    > Does it shed any more light?
    > ----------
    > Product
    > Windows Media Player
    >
    > Problem
    > Stopped working
    >
    > Date
    > 8/15/2008 12:10 PM
    >
    > Status
    > Report Sent
    >
    > Problem signature
    > Problem Event Name: APPCRASH
    > Application Name: wmplayer.exe
    > Application Version: 11.0.6001.7000
    > Application Timestamp: 47919356
    > Fault Module Name: ntdll.dll
    > Fault Module Version: 6.0.6001.18000
    > Fault Module Timestamp: 4791a7a6
    > Exception Code: c0000005
    > Exception Offset: 0003d02b
    > OS Version: 6.0.6001.2.1.0.768.3
    > Locale ID: 1033
    > Additional Information 1: bfef
    > Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
    > Additional Information 3: bfef
    > Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863
    >
    > Extra information about the problem
    > Bucket ID: 649592584
    >
    > "zachd [MSFT]" wrote:
    >

    >>
    >> Event Viewer notes are slightly inferior to the Problem Reports and
    >> Solutions Center control panel's View Problem History for those crashes.
    >>
    >> The first crash is from your old system pre-upgrade to SP1, likely
    >> indicating that memory corruption has occurred. There's a variety of
    >> potential suspects, but since you've upgraded, that's not 100% relevant
    >> any
    >> longer.
    >>
    >> The second crash: are palmusbdirect.dll or slacker.shared.dll on your
    >> system?
    >>
    >> The third crash: if you use the Problem Reports and Solutions Center to
    >> check for solutions, you should already be getting a notification here
    >> that
    >> your Office is out of date. Does updating per that help?
    >>
    >>
    >> All of the crashes are a little too generic to be analyzed just based
    >> upon
    >> that data. The actual crash DMP files might be interesting to look at,
    >> but
    >> the below data likely could not lead to any direct solution by itself.
    >>
    >> --
    >> Speaking for myself only.
    >> See http://zachd.com/pss/pss.html for some helpful WMP info.
    >> This posting is provided "AS IS" with no warranties, and confers no
    >> rights.
    >> --
    >> "civ2ru" <civ2ru@xxxxxx> wrote in message
    >> news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxx

    >> > Hello,
    >> >
    >> > First off, I run Vista Home Premium 32-bit. In the past several months
    >> > I've
    >> > started receiving error messages when my computer recovers from Sleep
    >> > Mode. I
    >> > don't remember when it started and I can't roll back that far. Various
    >> > programs - explorer.exe, wmplayer.exe, outlook.exe and others - "stop
    >> > working" and most of them indicate ntdll.dll as the faulting module
    >> > (see
    >> > event viewer logs included below). Please help!
    >> > ----------
    >> > Log Name: Application
    >> > Source: Application Error
    >> > Date: 7/22/2008 11:20:48 PM
    >> > Event ID: 1000
    >> > Task Category: (100)
    >> > Level: Error
    >> > Keywords: Classic
    >> > User: N/A
    >> > Computer: ...
    >> > Description:
    >> > Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp
    >> > 0x46d230c5, faulting module ntdll.dll, version 6.0.6000.16386, time
    >> > stamp
    >> > 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process
    >> > id
    >> > 0x824, application start time 0x01c8eb384724f9be.
    >> > ----------
    >> > Log Name: Application
    >> > Source: Application Error
    >> > Date: 8/16/2008 12:27:11 PM
    >> > Event ID: 1000
    >> > Task Category: (100)
    >> > Level: Error
    >> > Keywords: Classic
    >> > User: N/A
    >> > Computer: ...
    >> > Description:
    >> > Faulting application wmplayer.exe, version 11.0.6001.7000, time stamp
    >> > 0x47919356, faulting module ntdll.dll, version 6.0.6001.18000, time
    >> > stamp
    >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x0003d13a, process
    >> > id
    >> > 0x1510, application start time 0x01c8ffc54e67ba00.
    >> > ----------
    >> > Log Name: Application
    >> > Source: Application Error
    >> > Date: 8/9/2008 8:49:01 AM
    >> > Event ID: 1000
    >> > Task Category: (100)
    >> > Level: Error
    >> > Keywords: Classic
    >> > User: N/A
    >> > Computer: ...
    >> > Description:
    >> > Faulting application OUTLOOK.EXE, version 11.0.5510.0, time stamp
    >> > 0x3f1380f0, faulting module ntdll.dll, version 6.0.6001.18000, time
    >> > stamp
    >> > 0x4791a7a6, exception code 0xc0000005, fault offset 0x000658c8, process
    >> > id
    >> > 0x1538, application start time 0x01c8fa26a95e4d10.
    >>
    >>
    >>


      My System SpecsSystem Spec

  11. #10


    civ2ru Guest

    Re: APPCRASH - fault module NTDLL.DLL!

    Paul - thank you for your input! I have checked out the link. I haven't got
    the ntdll.dll error in the last few days, so I'm hopeful than SFC/scannow
    fixed the corrupted memory module...

    "Paul Montgomery" wrote:

    > On Mon, 18 Aug 2008 08:30:01 -0700, civ2ru
    > <civ2ru@xxxxxx> wrote:
    >

    > >How does one UNINSTALL the DLL?
    >
    > Check this before you go doing anything else:
    >
    > http://pcsupport.about.com/od/fixthe...a/ntdlldll.htm
    >

      My System SpecsSystem Spec

Page 1 of 2 12 LastLast

APPCRASH - fault module NTDLL.DLL!
Similar Threads
Thread Forum
faulting module ntdll.dll Vista General
Access violation ... in module ntdll.dll Vista General
APPCRASH - OLE32.DLL fault module Vista performance & maintenance
APPCRASH - OLE32.DLL fault module General Discussion
ntdll.dll fault Vista General