Crash Dump File Won't Open? [WINDBG.EXE]

[Sixaxis]

In short, I use Windows 7 Ultimate 32-bit and everytime I try to open Dump Files from either my computer or other computers with Microsoft's WinDbg.exe, it mainly gives these two errors at the end and WONT let me use any commands or examine the files:

"ERROR: Reload failure, partially initialized target
WaitForEvent failed".
------------------------------------------------------------------------------------------

Well, everytime I try to open a Crash Dump File (.DMP) that came from a game I use, it doesn't allow it. The thing is, there's only 2 of them out of the 20 something here that actually open, but I want to open the others too as they contain important information I need (Some of them are from different computers, but the thing is, I have about 12 on my computer that were created on my computer and only 2 of them open up). This is what happens when I use WinDbg.exe to try to open one of the dump files:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Kimberly\Desktop\Flash Drive\Debug View\Crash Dump Files\redluffy\irisclient v21769 2011-01-14 10-53-55.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Fri Jan 14 12:53:55.000 2011 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:01:42.000
ERROR: Reload failure, partially initialized target
WaitForEvent failed

That happens with almost all of the dump files. Why? (NOTE: That dump file is from another computer. The computer I opened it on, and am currently running it on, is Windows 7 Ultimate 32-bit)

 

[CarlTR6]

Are you trying to open memory dump files or mini dump files? Make sure you computer is configured for mini dumps. Read the last part of the first post in this tutorial: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[Sixaxis]

Thank you for replying. If you're asking if my computer is able to create mini-dumps and read them with windbg.exe, then yes. The problem is that oddly it can only read 2 of them out of the dozens I have on my computer and when I try to read one of the ones besides those 2, I get the said error below. Why is this?

*I also attached one of them that are unreadable for me @ the bottom of the post to see if it's readable for anyone else. If it's not too much trouble I'd really like for someone to see if it works for them. Thank you.*


http://www.sevenforums.com/attachment.php?attachmentid=132506&stc=1&d=1295215095

 

[CarlTR6]

I tried to open it and I could not open it either. This is what I get.

Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp2_irisclient v21769 2011-01-14 10-53-55.zip\irisclient v21769 2011-01-14 10-53-55.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Fri Jan 14 12:53:55.000 2011 (GMT-5)
System Uptime: not available
Process Uptime: 0 days 0:01:42.000
ERROR: Reload failure, partially initialized target
WaitForEvent failed
?:???> !Analyze
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
No export Analyze found

 

[Sixaxis]

Hm, I'll just go with the assumption that the program is creating corrupt Mini Dumps under certain conditions, and the 2 that actually work were chance ones. Thank you for your help CarlTR6! Glad there's helpful people like you on the net. Take care.

 

[CarlTR6]

You are welcome for the help and thank you for the compliment. It may be that your computer is shutting down to quickly to properly write the dump file.

 

[cluberti]

I ran the previously attached dump file through dumpchk, and it's complaining that the dumped process was partially initialized, meaning either the process being dumped is actively blocking debugger process attach events (this is possible), or it really is simply not dumping out properly (either due to problems with the debugger APIs on that machine, or something funky the process is doing while running). I can see loaded modules from dumpchk, though, and I noticed that GameGuard is installed. It is an active rootkit detector/anti-cheating application, and as such it is likely this is actively discouraging debugging (as if you attach as an invasive debugger, you have intrinsic rights to overwrite/change process memory - aka, "cheating").

 

[CarlTR6]

Thank you for the help, cluberti. Much appreciated.

Sixaxis, I have encountered problems with GameGuard before. It apparently causes problems on some Win 7 systems. Many third party security programs do not work well with Win 7 because of Win 7's own built in security coding.