Discussion Locked

How to examine dump file in Win2K?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A previous question was asked and answered on looking at dump file on NT using DUMPEXAM.EXE. Anybody knows how to look at the content on Win2K? I can see it (name: Mini081301-01.dmp size: 64 KB) at c:\winnt\minidump but Word display characters when reading this file. How do I read this file to find out what the problem is?
(Detail on the cause of the dump file: I run Win2K on my laptop. When I try to install PacBell DSL 'Enternet' software to establish my Internet access, the welcome screen comes on for 3 seconds followed by the blue screen. A message says the debug feature is writing a physical core dump file and the laptop reboot itself. The reboot does not complete but freezes at the Win2K window. I have to disconnect from its power tocold boot and the system is OK afterwards. I'm trying to see if the dimp file will tell me (1) if I could turn off the debug feature so it will allow me to install the DSL software, or (2) if there is a specific component on the DSL software the Win2K dislike, or (3) if there is a configuration setting on the laptop I could alter to prevent the dump.)
Help!

8 replies

by james_randy

Win2K's "Dr. Watson" feature can help you read the dump log files. Go to Windows Help, Dr. Watson, for info on how to use it.

Regards,

jr

by dyingforhelp

Thank you so much for the prompt reply! I'll transfer the dump file to a floppy and try it out tomorrow!
Will keep you posted. . .
(For those who might be interested to find out the PACBELL-DSL software/ Win2K conflict problem, I'll post the rememdy when I find out more from Microsoft or other source of help.)
Thank you, jr!!

by kdurichek

I took classes in windows 2000 and we discussed the dump file and no offense, but all the teachers told us the only way find out what was in the dump was to send it in to microsoft for their guys to interpret and tell what it meant for a price. If Dr. Watson can help read those files I'd like to see the paperwork on it.

by oldchewie

This is from MS web page:

One of the options for generating dump files in Windows 2000 is the Small Memory Dump (64 KB) option. You can read small memory dump files by using Dumpchk.exe. Information obtained from the dump file can provide a basicstarting point for troubleshooting the cause of the problem.

The debugging tools are supplied with the Windows 2000 Customer Support and Diagnostics Tools CD-ROM. The support CD-ROM is included with Windows 2000 Server and Windows 2000 Advanced Server. You can find a downloadable version of the tools and symbols at the following Microsoft Web site:

http://www.microsoft.com/windows2000/downloads/tools/symbols/default.asp

Hope this helps!

by dyingforhelp

Thank you, 'Bruski'! You're right on regarding the Dumpchk.exe utility.
In my case, the small dump file was not enough to debug the problem. So I have to generate the big dump file (select 'write large dump file', 34 MB, reinvent the problem) and send it to MS for help!
Thanks anyway!!

This discussion is closed to new replies.