Admin Tip #300: Using Dumpchk.exe to Determine Memory Dump Information

Hits: Failed to execute CGI : Win32 Error Code = 3


If Windows NT Server or Windows 2000 Server fails with a bugcheck, an error will be written in the system event log and a memory dump will be saved to %systemroot%\MEMORY.DMP, usually c:\winnt\memory.dmp. The dump file will reveal the driver that generated the stop code. Running Dumpchk.exe memory.dmp generates the line

ExceptionAddress somememoryaddress

The Resource Kit utility pstat.exe will generate a LONG list of Load Modules and Load Addresses which you can redirect to a text file, pstat.exe > memoryadr.txt. The module with the address equal to or just below the ExceptionAddress, reveals the failing driver.

Related tips:
New Crash Dump Options in Windows 2000 Reduce Memory.dmp Size
Blue Screen Preparation Before Contacting Microsoft
Windows 2000 Feature Allows a Memory.dmp File to Be Generated with Keyboard
WinNT Fails to Create a Memory.dmp On Any Other LUN Than 0
3Com 3c905b Prevents Write of Memory.dmp