The information on the problem signature is basically memory positions for the faulting dll at an intermediate language level.

This blog post explain each of the available fields. You can inspect the dll by using MSIL Disassembler

Hope this is what you were looking for,

Regards,

EDIT: As an additional note, in order to investigate intermediate level code I found easier to do File->Dump in the MSIL Disassembler. Then search for the method according to the Signature 07 param. e.g. .method /.590./

The information on the problem signature is basically memory positions for the faulting dll at an intermediate language level.

This blog post explain each of the available fields. You can inspect the dll by using MSIL Disassembler

Hope this is what you were looking for,

Regards,

EDIT: As an additional note, in order to investigate intermediate level code I found easier to do File->Dump in the MSIL Disassembler. Then search for the method according to the Signature 07 param. e.g. .method /.590./

The information on the problem signature is basically memory positions for the faulting dll at an intermediate language level.

This blog post explain each of the available fields. You can inspect the dll by using MSIL Disassembler

Hope this is what you were looking for,

Regards,

The information on the problem signature is basically memory positions for the faulting dll at an intermediate language level.

This blog post explain each of the available fields. You can inspect the dll by using MSIL Disassembler

Hope this is what you were looking for,

Regards,

EDIT: As an additional note, in order to investigate intermediate level code I found easier to do File->Dump in the MSIL Disassembler. Then search for the method according to the Signature 07 param. e.g. .method /.590./