windbg dump command fails with error 0x8007012b

windows windbg minidump
sean e picture sean e · May 9, 2009 · Viewed 7.4k times · Source

A customer is attempting to capture a minidump of a hang. He fires up WindDbg and successfully attaches to the process. WinDbg displays its header:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

and the loaded modules are enumerated.

He enters a dump command:

.dump /m c:\problem.dmp

It reports:

Creating c:\problem.dmp - mini user dump
WriteMemoryFromProcess.Read(0x1f1e000, 0x2000) failed, 0x8007012b
Dump creation failed, Win32 error 0n299
"Only part of a ReadProcessMemory or WriteProcessMemory request was completed."

Error 0x299 is: The requested operation could not be completed due to a file system limitation

Any ideas what this means or how to diagnose?

Answer

Volker von Einem picture Volker von Einem · May 11, 2009

Have a look at the /mA switch, it was introduced with 6.10.3:

Related questions

What is the "Break instruction exception" in WinDbg?

I'm debugging some random crash bugs, but actually very difficult to go deep into. Because when i open crash dump, only find one error: 0:000> .exr -1 ExceptionAddress: 00000000 ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 0 Actually i haven't set any hard-code …

Read More
Unable to find module 'mscorwks.dll'

I try to use the winDBG to debug a dump file. When I run .loadby sos mscorwks.dll It gave me an error message. Unable to find module 'mscorwks.dll' Has anyone seen this before?

Read More
How can I abort a long operation in WinDbg?

Often WinDbg will enter a state where it is *Busy* performing an operation. Often this is due to some mistake I made trying to dt some_variable_itll_never_find or setting a break point somewhere without symbols or the 1000…

Read More