Windows XP (explorer.exe) keeps crashing and restarting.

  • Thread starter Thread starter vegetarian108
  • Start date Start date
V

vegetarian108

This is what I get:

AppName: explorer.exe AppVer: 6.0.2800.1221 ModName: nvcpl.dll
ModVer: 6.14.10.5672 Offset: 000270d8

I know nvcpl.dll is an nvidia driver file. And I did get this problem after
uppgrading to nvidia v56.72 recently.

After reading a tip I uninstalled the nvidia display driver completely,
deleted all instances of nvcpl.dll and installed it all again fresh.

But explorer.exe still keeps crashing. Mainly when I do video editing. And
play video (mpeg2 or divx). It doesn't affect the programs running but it
asks for error report and closes all folders so it's annoying enough.

Any tip appreciated / Bill
 
vegetarian108 said:
This is what I get:

AppName: explorer.exe AppVer: 6.0.2800.1221 ModName: nvcpl.dll
ModVer: 6.14.10.5672 Offset: 000270d8

I know nvcpl.dll is an nvidia driver file. And I did get this problem
after uppgrading to nvidia v56.72 recently.

After reading a tip I uninstalled the nvidia display driver
completely, deleted all instances of nvcpl.dll and installed it all
again fresh.

But explorer.exe still keeps crashing. Mainly when I do video editing.
And play video (mpeg2 or divx). It doesn't affect the programs running
but it asks for error report and closes all folders so it's annoying
enough.

Any tip appreciated / Bill
Click to expand...

Two things come to mind: when you say you installed your Nvidia drivers
"fresh", did you use an older version? That might be the way to go.
Also, how much RAM do you have? Perhaps you don't have enough. If you
would like more help, then please include your machine specs -
including the size and speed of your hard drive - in your repost. Don't
forget to tell us what Nvidia card you have and also what you've done
to troubleshoot.

Malke
 
Thanks for the reply.
No I installed the new display drivers v56.72 again. I still prefer it
before my previous one v52.16 which sometimes caused hard crash with
flightsimulator. The explorer.exe crashes happens about 3-5 times / day if
I'm video editing alot. So I can live with that since it's not causing any
damage. But it's a bit annoying.

I have 1 Gbyte ram.
My videocard is ASUS V8440 Deluxe (=video in).
Motherboard is Intel D845GBV with Intel 2.4Ghz pentium 4.
Harddrive is Seagate ST3120022A 120Gbyte. I don't know the speed but it's
fast enough for capturing video without framedrops which in my case is about
3 Mbyte / sek.

I have not done much more than a reinstall of the display and wdm drivers.
The explorer.exe crash happens almost always right after I started a video
with windows mediaplayer 6.4 (the old one) but I haven't tried any other
player.

I looked in the logbook and found this message:
Faulty program explorer.exe, version 6.0.2800.1221, faulty modul nvcpl.dll,
version 6.14.10.5672, faulty adress 0x000270d8. (I translated as best I
could from my swedish version)

I also saw this message that I also think happend for the same reason:
fault-bucket 96141071.

But there where "No more information available" reply if I clicked the "more
info" link.

The settings for the video properties I have set to:
choice of performance is set to QUALITY
Antialiasing is set to 2xQ
Anisotrophic filtering is set to 8x

hope this helps / Bill
 
vegetarian108 said:
Thanks for the reply.
No I installed the new display drivers v56.72 again. I still prefer it
before my previous one v52.16 which sometimes caused hard crash with
flightsimulator. The explorer.exe crashes happens about 3-5 times /
day if I'm video editing alot. So I can live with that since it's not
causing any damage. But it's a bit annoying.

I have 1 Gbyte ram.
My videocard is ASUS V8440 Deluxe (=video in).
Motherboard is Intel D845GBV with Intel 2.4Ghz pentium 4.
Harddrive is Seagate ST3120022A 120Gbyte. I don't know the speed but
it's fast enough for capturing video without framedrops which in my
case is about 3 Mbyte / sek.

I have not done much more than a reinstall of the display and wdm
drivers. The explorer.exe crash happens almost always right after I
started a video with windows mediaplayer 6.4 (the old one) but I
haven't tried any other player.

I looked in the logbook and found this message:
Faulty program explorer.exe, version 6.0.2800.1221, faulty modul
nvcpl.dll, version 6.14.10.5672, faulty adress 0x000270d8. (I
translated as best I could from my swedish version)

I also saw this message that I also think happend for the same reason:
fault-bucket 96141071.

But there where "No more information available" reply if I clicked the
"more info" link.

The settings for the video properties I have set to:
choice of performance is set to QUALITY
Antialiasing is set to 2xQ
Anisotrophic filtering is set to 8x

hope this helps / Bill
Click to expand...

Hey, Bill. What comes to my mind is "overheating". Either that, or
perhaps you have a faulty video card. I'm not familiar with Asus V8440
Deluxe - is that a high-end graphics card as opposed to the more
familiar Nvidia gaming cards? Open up the computer and run it open.
Make sure it is clean in there. Observe all the fans carefully,
including any on the video card. Feel the ambient temperature (without
touching any of the components, please!). Or you can install
Motherboard Monitor which is a good sensor program. Another thought is
power supply. Is your power supply a good one? Hefty enough to handle
all that hardware?

Malke
 
Thanks Malke.

First of all I forgot to say that I've done all the important updates on
microsoft windows-update.

I dont think it's overheating cause this morning I got a crash after having
the computer on for just 5 minutes and the only thing I did was playing some
mpeg2 and divx video files with mplayer2. No editing at all. And I have
already an extra fan running. Also I did clean the box out recently and
checked that all fans where running. If it's the power-supply, well I guess
I'll have to wait and see then if it start showing some more serious errors
soon.

On these links I just found 2 others that has had the exact same error:

http://techrepublic.com.com/5208-6239-0.html?forumID=49&threadID=152570
http://forums.anandtech.com/messageview.cfm?catid=34&threadid=1311725&enterthread=y

But they had no definite answers either.

/ Bill
 
vegetarian108 said:
Thanks Malke.

First of all I forgot to say that I've done all the important updates
on microsoft windows-update.

I dont think it's overheating cause this morning I got a crash after
having the computer on for just 5 minutes and the only thing I did was
playing some mpeg2 and divx video files with mplayer2. No editing at
all. And I have already an extra fan running. Also I did clean the box
out recently and checked that all fans where running. If it's the
power-supply, well I guess I'll have to wait and see then if it start
showing some more serious errors soon.

On these links I just found 2 others that has had the exact same
error:

http:/ techrepublic.com.com/5208-6239-0.html?forumID=49&threadID=152570
messageview.cfm?catid=34&threadid=1311725&enterthread=y

But they had no definite answers either.
Click to expand...

Based on this information, I'd suspect one or all of: 1) bad RAM; 2)
faulty processor; 3) failing video card; 4) bad motherboard; 5) bad
power supply - not necessarily in that order. What I *don't* think it
is: software. Time for major hardware diagnosis. If you don't have the
facilities for that (spare parts, extra machines, lots of time, etc.)
then take the box to a good local computer repair shop (not a BestBuy
or CompUSA type of store) and have them do the diagnosis/fix.

Good luck,

Malke
 
Malke, I think I can exclude the hardware bit. It pops up more questions
from people that has exactly the same problem and all have exactly the same
version of explorer.exe and nvcpl.dll. So right now I'm waiting for a reply
on another thread in this conference "Explorer.exe crashes all the time
Event ID 1000" to see what they might come up with.

/ Bill
 
vegetarian108 said:
Malke, I think I can exclude the hardware bit. It pops up more questions
from people that has exactly the same problem and all have exactly the same
version of explorer.exe and nvcpl.dll. So right now I'm waiting for a reply
on another thread in this conference "Explorer.exe crashes all the time
Event ID 1000" to see what they might come up with.

/ Bill
Click to expand...


Hi Bill... I think this issue has something to do with the new nvidia
drivers.
I've verified with both mplayer2.exe and wmplayer.exe.

Explorer.exe crash randomly when I try to launch a movie using the
"open with" command.

Same problem shows up using "mplayer classic".

Since I've just formatted and reinstalled all the stuff, I just
disabled the Nvidia Display Driver Services from the Services
Administration Panel (start|run|services.msc)

Everything seems to work fine now.

Hope this little workaround will help to fix the problem or to find a
better solution.

Sorry for the bad english.

Cheers
 
Hi.
Thank you for the reply. I have now disabled Nvidia Display Driver Services
to see if it makes a difference. So far I had disabled the error-reporting
and unchecked "tell me about serious errors" under
(right click) this computer / properties / advanced / error reporting. That
made it just restart the desktop in the background without any pop-up window
to confirm. That made me hardly notice the crashes at all.

But I'll let you know after a day or so if the explorer.exe crashes has
stopped.
Cheers / Bill
 
vegetarian108 said:
Thank you for the reply. I have now disabled Nvidia Display Driver Services
to see if it makes a difference. So far I had disabled the error-reporting
and unchecked "tell me about serious errors" under
(right click) this computer / properties / advanced / error reporting.
Click to expand...

If you have installed a new set of drivers like that and suspect them of
causing trouble, roll back to the previous ones. You should be able to
do that from Control Panel - System - Hardware - Device Manager. Find
the device and double click; on the Drivers page click 'Roll Back'
 
Million thanks zerohops!
I think disabling "Nvidia Display Driver Services" did it! I have not had
any explorer.exe crash yet. And i did enable error reporting again so i
should have seen if there was a crash. What is that service for? Everything
seems to work as before.

Thank you Alex for your tip but the problem seems to be fixed for me at
least now.

Happy again / Bill
 
Back
Top