Re: APPCRASH - fault module NTDLL.DLL!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F0AD34B6-E015-471D-95CC-7AF4AD004336@xxxxxxxxxxxxxxxx
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.



.

Relevant Pages

  • Re: APPCRASH - fault module NTDLL.DLL!
    ... This second crash bucket also is most correlated to palmusbdirect.dll. ... As for ntdll.dll and Problem Reports and Solutions logs, ... working" and most of them indicate ntdll.dll as the faulting module ... Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp ...
    (microsoft.public.windows.vista.general)
  • Re: APPCRASH - fault module NTDLL.DLL!
    ... This second crash bucket also is most correlated to palmusbdirect.dll. ... As for ntdll.dll and Problem Reports and Solutions logs, ... working" and most of them indicate ntdll.dll as the faulting module ... Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp ...
    (microsoft.public.windows.vista.general)
  • Re: APPCRASH - fault module NTDLL.DLL!
    ... As for ntdll.dll and Problem Reports and Solutions logs, ... The second crash: are palmusbdirect.dll or slacker.shared.dll on your ... working" and most of them indicate ntdll.dll as the faulting module ... Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp ...
    (microsoft.public.windows.vista.general)
  • Re: APPCRASH - fault module NTDLL.DLL!
    ... Speaking for myself only. ... The second crash: are palmusbdirect.dll or slacker.shared.dll on your ... > working" and most of them indicate ntdll.dll as the faulting module ... > Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp ...
    (microsoft.public.windows.vista.general)