Rick "Nutcase" Rogers said:
Hi Andrea,
Take a course in IA32 assembly language in order to use a debug program that
will tell you what's actually going on. Crash Dumps are best left to those
that can correctly interpret the data that is gathered, there is no easy way
to learn this without hours and hours of going through them,
Hi roger,
thank you for your answer. Unfortunately I don't know Assembly but I'm a
C/C++ programmer with some knowledge on win32 platform. I know it's
impossibile and perhaps stupid too desire an easy way to read dump file
'cause we are at machine code level.
But my question start from the necessity to understand or just have a
"suggestion" on the origin of blue screen. I downloaded the microsoft debug
symbols and I'd like to learn to process dump file in order to understand,
for example:
ok, execution stopped in the module
module.dll!function_name();
with this call stack ...
I've got blue screen, I need to understand just the origin.
researching
the resultant error codes, and looking up the sources of indicated modules
involved. A good place for researching the codes and their meaning is the
MSDN library, but it is not by any means the only resource.
I read a lot on microsoft documentation but it's too generic to understand
what's up with my system. If you have any suggestion I will appreciate a
lot!
Thank you very much
andrea