Memory Dump May Be Missing or Corrupted on Dynamic Mirrored Drive (253935)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q253935 SYMPTOMS
When a server stops responding (hangs) at a blue screen, the dump file may be missing or corrupted after you restart the server. Running Dumpchk.exe against the dump file may return the following message:
Validating the integrity of the PsLoadedModuleList
Error: could not read base of PsLoadedModuleList
ERROR: The module list is not valid
CAUSE
This behavior can occur if the server is running on a dynamic mirrored volume. The dump file is saved correctly to the primary drive, but when you restart the server the file becomes corrupted.
WORKAROUND
To work around this problem, disconnect the slave drive before restarting the server. You can then capture the dump file. If you have already started the server, the file is already corrupted. To prevent the server from restarting automatically:
- Click Start, point to Settings, and then click Control Panel.
- Double-click System.
- On the Advanced tab, click Startup and Recovery.
- Click to clear the Automatically Reboot check box, and then click OK.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
This behavior does not occur with legacy mirrored volumes, only with dynamic mirrored volumes.
| Modification Type: | Major | Last Reviewed: | 11/4/2003 |
|---|
| Keywords: | kbenv kbFileSystems kbprb w2000fs KB253935 |
|---|
|