faulting module ntdll.dll

  • Thread starter Thread starter Joe D
  • Start date Start date
J

Joe D

Hi

Explorer has encountered a problem and needs to close. I click on ok and get
a blue screen for a few seconds if it hasn't foze then everything goes back
to being ok.
This happens frequently when opening folders or after using cdrom and it
seems to be random.
I have found a couple of other users with the same problem but I cannot find
a fix as yet.
I am running XP home with all the updates and have updated all my drivers. I
have even tried cleaning the inside of my computer with air in a can, lol
and checking cables.

This is the error log.

Faulting application explorer.exe, version 6.0.2800.1221, faulting module
ntdll.dll, version 5.1.2600.1217,

fault address 0x00007ec4. <what does this
bit mean?

Do I need to replace the dll.

Joe
 
I am also having the problem and searched and searched
and can't find an answer. There seems to be alot of
people with the same problem. I get the error in all
different places, especially in the control panel. I
contacted my OEM since the computer is only a week old
and they suggested doing a restore. Just after I got all
the hardware and some programs installed!! I did what
they suggested and the problem went away UNTIL I did the
Windows Update! That is apparently the problem. There is
something wrong with one of their updates. I remembered
that the problem started before after I installed the
updates and installed one other program. This time I just
installed the updates and the problem started again. I
was scared to not install the updates since there were so
many security issues that I was warned about and I was
afraid to not install them but they did cause the
problem. Rolling the system back to an earlier date does
NOT solve the problem because I was told to try that the
first time and I tried it the second time after restoring
the system. So it looks like the only thing to do again
to make the error go away is to do a full recovery again
but to not install Microsofts updates. If you find a
solution let me know because I have searched all over the
net and there is allot of people with the problem but no
answers. Good luck!
 
quadgram said:
I am also having the problem and searched and searched
and can't find an answer. There seems to be alot of
people with the same problem. I get the error in all
different places, especially in the control panel. I
contacted my OEM since the computer is only a week old
and they suggested doing a restore. Just after I got all
the hardware and some programs installed!! I did what
they suggested and the problem went away UNTIL I did the
Windows Update! That is apparently the problem. There is
something wrong with one of their updates. I remembered
that the problem started before after I installed the
updates and installed one other program. This time I just
installed the updates and the problem started again. I
was scared to not install the updates since there were so
many security issues that I was warned about and I was
afraid to not install them but they did cause the
problem. Rolling the system back to an earlier date does
NOT solve the problem because I was told to try that the
first time and I tried it the second time after restoring
the system. So it looks like the only thing to do again
to make the error go away is to do a full recovery again
but to not install Microsofts updates. If you find a
solution let me know because I have searched all over the
net and there is allot of people with the problem but no
answers. Good luck!
Click to expand...

Hi Quadgram

Thanks for your reply.
It is good to know I am not the only one with the problem. Now MS might get
their finger out of their arses and do something with all the error reports
they'll be getting. :-)

I think you are right about the problem being related to updates as I think
the problem is with service pack2 updates and hot fixes as the ntd.dll that
is faulty is from sp2 updates / hot fixes and cannot be removed. I am going
to clean install xp and try only to update to SP1 and other updates around
SP1 only. MS must have been in a rush to get the hot fixes out. lol. I am
aware that trying this will leave my computer vulnerable to attack etc.

If I find a fix I will post it. :-))

Thanks again.

Joe D
 
Hi Quadgram

I have managed to stop explorer from crashing by clean installing XP home
from disc and only installing up to SP1 and intalling IE updates as well as
installing media player 9 with update as well as messenger 4.7 etc. I don't
want to install any SP2 stuff as "I" think that the problem is the SP2
ntdll. Although this could have been corrupted with hot fixes further up the
line. Who cares, it works! I realise this is not safe as I don't have the
security patches but I will take my chances as the crashes were doing my
head in.
So far so good for now. I will keep you posted. lol
I'm still on a mission!!! lol.

Off topic a bit here with my new discovery.
If you are going clean install XP yourself I advise you to fix the swap file
(if you use one) as soon as you have installed XP. This will fix it to the
beguining of the disk or partition that you apply it to. I have set mine
with the initial size the same as the max size right after I installed XP
and before I installed anything else. To set it go to start/control
panel/system/advanced tab/performance settings/advanced/virtual memory
change/custom size and make the initial the same as the max size. Do this to
any partitions you have that need a swap file. Then carry on with installing
drivers updates and proggy's and stuff.

The good bit is when you come to defragment the drive(s) after installing
everything you will see a nice lump of green at the beguining of the defrag
bar. :-) That is the swap file all neatly arranged so your HD doesn't have
to thrash about all over the platters swapping. The swaped files can't be
moved with defrag so if you don't fix them straight away they will become
fragmented as they are written and they stay fragmented unless you reset
them. But then they won't be at the beguining of the disk!

I'll see how XP explorer copes with Photoshop and Cubase SX next.

Keep you posted. Over and out. lol.

Joe D
 
Back
Top