Analyzing BSOD without a dump
Posted
by
eeoo2555
on Stack Overflow
See other posts from Stack Overflow
or by eeoo2555
Published on 2012-07-02T08:36:28Z
Indexed on
2012/07/03
3:15 UTC
Read the original article
Hit count: 113
One of the drivers I'm developing has caused a BSOD. Unfortunately a dump file was not created since it was not configured / low resources. I was trying to reproduce this crash but no luck so far.
Is there any way to get some info using WinDbg or any other tool? I have this information:
- A screenshot of the BSOD
- The .sys file.
- Its pdb
- The source code
- The machine it was crashed on
I have everything except the dump itself.
Your help will be much appreciated.
As I said above, no dump (/minidump) exists. This is the actual problem.
For this specific crash, I know I won't be able to get the stack. Just getting the specific line of code will be good enough. Because the BSOD contains the module's address, it seems like there should be a way to detect which line exactly is it. As I mentioned above, I do have the .sys file, the pdb and the source code.
This is the specific code taken from MSDN: SYSTEM_SERVICE_EXCEPTION. How can I know from there what was the specific line? and/or the specific exception raised?
© Stack Overflow or respective owner