No minidump created sometimes - reports "Only part of a ReadProcessMemory or WriteProcessMemory request was completed"

***NOTE*** Please do create a NEW issue per each detected bug! Do not list
all detected problems in single issue record!

What steps will reproduce the problem?
1. Some, but not all, crashes due to an intermittent access violation do not 
produce crash reports with a valid/complete minidump file. The 
CrashSender1402.exe program does not terminate.
2.
3.

What is the expected output? What do you see instead?

The expected output is a crash dump report containing a valid minidump file.

What version of CrashRpt are you using?

1402

What is your version of Visual Studio?

2008

What is your version of Windows operating system?

Windows 7

Please provide any additional information below.

The issue is reproducible across two machines (Windows 7 and Windows 2008 
Server).
The problem is specific to one crash, or at least, is not reprodicible with a 
deliberate crash in which null is explicitly dereferenced to produce an access 
violation. 

Attached is a slightly sanitized crashdump XML report.

There was a mention in the changelog of a commit to fix precisely this issue, 
but it evidently does not work in all cases.

Original issue reported on code.google.com by grrus...@googlemail.com on 15 Jan 2014 at 8:08

Attachments:

crashrpt.xml

fgokey / crashrpt

No minidump created sometimes - reports "Only part of a ReadProcessMemory or WriteProcessMemory request was completed" #234