Explorer crashes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I try to move a file/files such as mp3 explorer crashes and says it is writing to a log file,can't find out what is wrong other than write caching has been disabled for controller 0 and 1 but I have write caching turned off for these drives. Am running win2000 pro. , via buss controller with latest updates and sp4 any ideas??? Have scaned for virsues and don't apper to have any. This has been going on for a month. Some times it works fine but then it starts crashing and even after a re-boot it happens.
 
Check and see if there is a User.dmp file created in the \winnt directory.
The file timestamp should match the time of the crash. If there is, I can
tell you how to open it and take a look at what is crashing. If there isn't
(or even if there is, I suppose), look at the Event Logs (Application &
System) and see if any useful information was logged.

It is unlikely to be a driver problem b/c that would generally result in a
blue-screen or system restart. Explorer issues are generally plug-ins that
are misbehaving. You could run a program like Ad-Aware and see if there is
anything installed that you didn't know about.


Pat

Frank said:
When I try to move a file/files such as mp3 explorer crashes and says it
Click to expand...
is writing to a log file,can't find out what is wrong other than write
caching has been disabled for controller 0 and 1 but I have write caching
turned off for these drives. Am running win2000 pro. , via buss controller
with latest updates and sp4 any ideas??? Have scaned for virsues and don't
apper to have any. This has been going on for a month. Some times it works
fine but then it starts crashing and even after a re-boot it happens.
 
Found user.dmp in drwatson dir with the date that explorer crashed. What can I use to read? TIA and thanks for your help.
 
This is where it gets tricky. To read a dump yourself, you use one of the
MS debuggers (explained below). If you are not comfortable reading the
debug yourself, you can open a case w/MS-Support to have the dump read for
you.

But, to do it yourself do the following:
1) Download & Install the debugger pack
(http://www.microsoft.com/whdc/ddk/debugging/default.mspx).
1a) Create a directory called c:\debug
2) Launch WinDBG
3) Open the dump file (Click on File-->Open Crash Dump)
4) Type: ".logopen c:\out1.txt <enter>"

This creates a log file of your typing so that you can post the output if
you want someone in the group to take a look.

5) Type: ".sympath
SRV*c:\debug*http://msdl.microsoft.com/download/symbols<enter>"
6) Type: ".reload <enter>"

This can take a while as symbols are being downloaded from microsoft.com.
You can see the downloaded files in the c:\debug folder you created at 1a.

7) To see the failure type: "kb <enter>" (possible download delay)
8) Type: "!analyze -v <enter>" (possible download delay)

This gives you the thread that failed and runs some basic checks on it.

9) Type: ".logclose <enter>"

If you need help interpreting the log file (or the output), you can post the
output of the log (stored in c:\out1.txt).


Pat




Frank said:
Found user.dmp in drwatson dir with the date that explorer crashed. What
Click to expand...
can I use to read? TIA and thanks for your help.
 
Back
Top