« Collective Pointer (Categories for the Working Software Defect Researcher, Part 3)
Reading Notebook: 22-March-10 »

Bugtation No.118

The clash of titans over the bit of memory.

Dmitry Vostokov, Empires of the Code

- Dmitry Vostokov @ DumpAnalysis.org + TraceAnalysis.org -

This entry was posted on Tuesday, March 23rd, 2010 at 10:05 am and is filed under Bugtations, Crash Dump Analysis, Debugging, Escalation Engineering, Software Technical Support. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “Bugtation No.118”

  1. Knyghte Hande Says:
    March 23rd, 2010 at 4:00 pm

    Hello, Dmitry.

    I want to know if you can help me on an issue I’m facing with a customer. I have a server that’s hanging up because it’s filling up the non-paged memory pool. So, I want to create a WinDBG-compatible memory dump but I don’t want to create a BSOD on the server. Any toughts?

    Thanks!

  2. Dmitry Vostokov Says:
    March 25th, 2010 at 6:09 pm

    I think you can try to use poolmon to get (non)paged pool tag consumption:

    Poolmon.exe /b

    and

    Poolmon.exe /p /b

    and then look at C:\Program Files\Debugging Tools for Windows\triage\triage.ini for pool tag descriptions or if they are not present try to use findstr as shown here:

    http://www.dumpanalysis.org/blog/index.php/2007/08/25/crash-dump-analysis-patterns-part-23b/

    Although if your server completely hangs you would have to reboot it anyway so why not generate BSOD after users are asked to logon (if they can)?

Leave a Reply

You must be logged in to post a comment.