XP process Explorer.exe hanged but cannot be killed

[msenquiry]

I am using XPMCE. Sometimes the Explorer will be hanged and cause the whole
screen hanged. I tried to kill the process explorer.exe in the Task Manager
but cannot. Since the whole screen hanged, I tried to start another explorer
but the whole screen still hanging. Then I saw 2 explorer.exe in the Task
Manager but all cannot be killed which make me headache..... I have to
restart my PC finally.

This also happened to my DVD burning program Nero too.....

Anyone know the root cause? Thanks!

 

[Malke]

I am using XPMCE. Sometimes the Explorer will be hanged and cause the whole
screen hanged. I tried to kill the process explorer.exe in the Task Manager
but cannot. Since the whole screen hanged, I tried to start another explorer
but the whole screen still hanging. Then I saw 2 explorer.exe in the Task
Manager but all cannot be killed which make me headache..... I have to
restart my PC finally.

This also happened to my DVD burning program Nero too.....

Anyone know the root cause? Thanks!

What is the malware/virus status of the machine? If you think it is
clean, what programs (and versions) did you use to determine this?

Be sure the computer is clean:
http://www.elephantboycomputers.com/page2.html#Removing_Malware


Malke

 

[msenquiry]

Hi,

I am using both Norton Internet security and Windows defender. The virus
status is clean.

Thanks!

 

[Malke]

Hi,

I am using both Norton Internet security and Windows defender. The virus
status is clean.

I'm sorry but using NIS and WD is not proof that the computer is clean.
You will need to go through at least some of the steps at the link I
already gave you.

If the computer is then found to be truly clean, do clean-boot
troubleshooting to narrow down the culprit(s):

Clean boot in Windows XP - http://support.microsoft.com/kb/310353
Clean-boot advanced troubleshooting in Windows XP -
http://support.microsoft.com/kb/316434
How to Troubleshoot By Using the Msconfig Utility in Windows XP -
http://support.microsoft.com/?id=310560

You also should ask yourself The First Question Of Troubleshooting: what
changed between the time things worked and the time they didn't?

Malke