Dumpfile error

[Guest]

I'm experimenting with a command line tool, <dumpchk.exe Dumpfile.dmp> but I
get the following error:

debugclient cannot open Dumpfile error 80070002

I've read that there may be a problem with the path but what path is that
relating to? The actual path where bug files are stored? If this is the case
can someone give me an example of the path where these files are usually
stored.

 

[Wesley Vogel]

Make sure that dumpchk.exe is in %windir%\system32.

In a command prompt type:
dumpchk /?
Hit your Enter key.

If you see this...
Usage: DumpCheck [y <sympath>] <Dumpfile>
the path is OK.

I got this error because I have no *.dmp files...

C:\>dumpchk.exe Dumpfile.dmp
Loading dump file Dumpfile.dmp
**** DebugClient cannot open DumpFile - error 80070002

I got the very same error when I deleted dumpchk.exe from %windir%\system32.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

I got the Usage: DumpCheck [y <sympath>] <Dumpfile>
answer even though the file is in c:\program files\support tools

I don't have any stop errors so I guess i won't see a dump file.

Thanks for the help.

Make sure that dumpchk.exe is in %windir%\system32.

In a command prompt type:
dumpchk /?
Hit your Enter key.

If you see this...
Usage: DumpCheck [y <sympath>] <Dumpfile>
the path is OK.

I got this error because I have no *.dmp files...

C:\>dumpchk.exe Dumpfile.dmp
Loading dump file Dumpfile.dmp
**** DebugClient cannot open DumpFile - error 80070002

I got the very same error when I deleted dumpchk.exe from %windir%\system32.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I'm experimenting with a command line tool, <dumpchk.exe Dumpfile.dmp>
but I get the following error:

debugclient cannot open Dumpfile error 80070002

I've read that there may be a problem with the path but what path is that
relating to? The actual path where bug files are stored? If this is the
case can someone give me an example of the path where these files are
usually stored.

 

[Wesley Vogel]

Do a Search for *.dmp.

%systemroot%\MEMORY.DMP is the default.

To check the path to dump files...
Right click My Computer | Properties | Advanced tab | Under Startup and
Recovery | Settings button | Under Dump file:

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I got the Usage: DumpCheck [y <sympath>] <Dumpfile>
answer even though the file is in c:\program files\support tools

I don't have any stop errors so I guess i won't see a dump file.

Thanks for the help.

Make sure that dumpchk.exe is in %windir%\system32.

In a command prompt type:
dumpchk /?
Hit your Enter key.

If you see this...
Usage: DumpCheck [y <sympath>] <Dumpfile>
the path is OK.

I got this error because I have no *.dmp files...

C:\>dumpchk.exe Dumpfile.dmp
Loading dump file Dumpfile.dmp
**** DebugClient cannot open DumpFile - error 80070002

I got the very same error when I deleted dumpchk.exe from
%windir%\system32.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I'm experimenting with a command line tool, <dumpchk.exe Dumpfile.dmp>
but I get the following error:

debugclient cannot open Dumpfile error 80070002

I've read that there may be a problem with the path but what path is
that relating to? The actual path where bug files are stored? If this
is the case can someone give me an example of the path where these
files are usually stored.

 

[Ron Martell]

I'm experimenting with a command line tool, <dumpchk.exe Dumpfile.dmp> but I
get the following error:

debugclient cannot open Dumpfile error 80070002

I've read that there may be a problem with the path but what path is that
relating to? The actual path where bug files are stored? If this is the case
can someone give me an example of the path where these files are usually
stored.

There are 3 requirements that must be met in order to get a System
Failure memory dump file created:

1. A memory dump option must be selected in Control Panel - System -
Advanced - Startup and Recovery Settings. If you have changed the
setting to "no memory dump" then a memory dump will not be produced.

2. There must be a paging file configured on the system boot
partition. If you have changed the paging file location to a
different drive letter then a memory dump cannot be saved.

3. The paging file size on the system boot drive is less than the size
of the memory dump then the dump cannot be saved. So if you have 512
mb of RAM and you have chosed the "full memory dump" option then your
paging file on the system boot drive must be at least 512 mb in size.

Hope this explains the situation.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm