Unable to load dmp files for some users, any ideas why?

writhziden · 29 Dec 2011

Anak said:

Good to know!

Your thread may turn into a "sticky". "Debugging the debugger"

The WinDbg problem seems to occur when it cannot properly verify all driver dates. One of the times that I used the Break trick, it spit out about 20 drivers that were unable to have the dates verified. My guess is: the data for the dates gets corrupted and WinDbg can't verify them properly.

Anak · 29 Dec 2011

I wonder how long one would have to wait for Microsoft to verify your theory.

writhziden · 29 Dec 2011

Anak said:

I wonder how long one would have to wait for Microsoft to verify your theory.

I don't know, but I'm not paying them to figure it out. Lol. My dad was writing a piece of software and found an issue with Microsoft's code, and they wanted him to pay them the troubleshooting fee just for him to tell them what it was. Microsoft is just a money sink hole when it comes to their programs having issues that need fixing.

Edit: I have sent an e-mail to the SDK team to see if they can find the problem. I attached a sample .dmp file that I had issues with.

Anak · 29 Dec 2011

writhziden said:

Anak said:

I wonder how long one would have to wait for Microsoft to verify your theory.

I don't know, but I'm not paying them to figure it out. Lol. My dad was writing a piece of software and found an issue with Microsoft's code, and they wanted him to pay them the troubleshooting fee just for him to tell them what it was. Microsoft is just a money sink hole when it comes to their programs having issues that need fixing.

Well, that only seems fair.

There are several sayings that come to mind...One is; "What goes around, comes around"

writhziden said:

Edit: I have sent an e-mail to the SDK team to see if they can find the problem. I attached a sample .dmp file that I had issues with.

Did you send it through a proxy, you would not want them to know your IP address.

writhziden · 19 Jan 2012

Anak said:

writhziden said:

Anak said:

I wonder how long one would have to wait for Microsoft to verify your theory.

I don't know, but I'm not paying them to figure it out. Lol. My dad was writing a piece of software and found an issue with Microsoft's code, and they wanted him to pay them the troubleshooting fee just for him to tell them what it was. Microsoft is just a money sink hole when it comes to their programs having issues that need fixing.

Well, that only seems fair.

There are several sayings that come to mind...One is; "What goes around, comes around"

writhziden said:

Edit: I have sent an e-mail to the SDK team to see if they can find the problem. I attached a sample .dmp file that I had issues with.

Did you send it through a proxy, you would not want them to know your IP address.

The SDK team never did respond. Guess for now, the solution I posted is the best workaround.

Anak · 19 Jan 2012

writhziden said:

I found a solution to the problem. If it gets stuck as it did in my case, click Debug -> Break -> then click on the command line box (next to kd>) -> Type "!analyze -v" (without quotes) -> Hit Enter

The WinDbg problem seems to occur when it cannot properly verify all driver dates. One of the times that I used the Break trick, it spit out about 20 drivers that were unable to have the dates verified. My guess is: the data for the dates gets corrupted and WinDbg can't verify them properly.

Instead of corruption it may be that the dates were never added to the driver package or they are in an area that the Dbg doesn't think to look.

Either case though, it would be highly unusual that, that would occur.