Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I've always pondered this question but could never find an answer. One of my thoughts was that it was part of the BIOS, but that gets stopped once the kernel can support the system. Than I thought maybe it was part of the Windows kernel, but how can that be if the kernel has crashed? Any thoughts?

share|improve this question

closed as not constructive by Karan, Keltari, sudo, Dave M, CharlieRB Feb 5 '13 at 13:27

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

    
@Alexander: I may have come off wrong. I do know where the minidump and debugging files are stored but the actual code which "is", in essence, the BSoD, I'm unaware of its location. Thanks for the answer though! –  Cole Feb 4 '13 at 21:52

2 Answers 2

BSOD handling code is in ntoskrnl.exe

share|improve this answer
    
As is most of the core Windows code. –  cpast Feb 4 '13 at 22:42
    
Formatted text spew to screen from ntoskrnl error handler routine with background color blue and foreground color white. (There is no page ™ ) –  Fiasco Labs Feb 5 '13 at 5:37

Frome Windows 7 IT Forum theme BSOD error log location:

Check in %systemroot%\minidumps like c:\windows\minidumps

See also Startup and Recovery window, "Small dump directory" edit box.

share|improve this answer
    
The OP is not asking about the minidump path (see comment above). He apparently thinks there's a separate file for BSODs. –  Karan Feb 5 '13 at 4:39

Not the answer you're looking for? Browse other questions tagged or ask your own question.