bad_pool_header 0x19 on 2003 Server

[dflorea]

On one 2003 server, I frequently get a BSOD from a bad_pool_header 0x19 error. Here's the entire bugcheck message:

0x00000019 (0x00000020, 0x85ff0550, 0x85ff06e0, 0x0a320063)

Problem is, no minidump file was saved, and my memory.dmp file is just over 1G. I was unable to open it with Wordpad. I downloaded Windbg, but when trying to open the crash dump file all I got was 'corruption' and 'out of context' errors -- apparently I have a learning curve to deal with on Windbg.

These BSOD errors usually come after I do the Windows Updates from WSUS, often during the reboot. Yesterday this happened even when no reboot was required. I understand from looking at others' posts who've had this error that it's likely a device driver, but I need to know which one -- there are no substantive errors showing aside from this.

I'm sure looking for good ideas...

Thanks,

David

[cluberti]

First, make sure that your paging file is at least the size of physical RAM +50MB or so. In fact, make sure to follow these instructions, and then let me know the next time you get a memory dump:

1. If you have a feature like Compaq's Automatic System Restart (ASR), please disable it. This setting is usually found in the BIOS. With this feature enabled, if the BIOS does not detect a heartbeat from the OS, it will restart the server. This will interrupt the dump process.

2. Create or set the following registry value:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

Value: CrashOnCtrlScroll

Type: REG_DWORD

Data: 1

Refer to the following Knowledge Base article for more information on this registry key:

244139 Windows Feature Allows a Memory.dmp File to Be Generated with Keyboard

http://support.microsoft.com/?id=244139

3. Right-Click on the "My Computer" icon on the desktop and select "Properties"; this will open the "System Properties" window. Go to the "Advanced" tab and click "Performance Options". Click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB.

4. Also in the "System Properties" window, click on the "Advanced" tab, then click "Startup and Recovery". Make sure "Complete Memory Dump" is selected (see 4a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed.

4a. If the "Complete Memory Dump" option in step 4 is not available, you will need to manually set this registry value:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

Value: CrashDumpEnabled

Type: REG_DWORD

Value: 1

5. You will need to reboot the server for these changes to take effect.

[dflorea]

No problem -- so if I cause a crash after hours tonight, will that dump file have the data I'm looking for -- I don't have to wait for the machine to error out and crash on its own?

Appreciate the help.

David

[RJARRRPCGP]

Have you checked the temperatures?

I gotten a similar symptom before when there was warm air coming in my duct, (but I have Windows 2000 Pro SP4) it would BSOD when in the middle of installing .Net Framework 2.0 and then BSOD'ed again after it was rebooted.

Random BSODs often are hardware-related.

Well, I ended up just reformatting and reinstalling Windows 2000 Pro after hooking my air conditioner to the intake. I shall have done that earlier. Because I'm OC'ing my Barton 3000+ and I was lazy. I didn't think that the temperature was high enough for a BSOD when running a less processor-demanding task.

The outside air was heating up, because the sun was shining on my outside air extracting apparatus.

With my Barton 3000+ OC, as long as the outside air temperature isn't higher than the 30s, possibly the low 40s, (farenheit) I won't get crashes.

[cluberti]

No problem -- so if I cause a crash after hours tonight, will that dump file have the data I'm looking for -- I don't have to wait for the machine to error out and crash on its own?

Yes - with the above configured (and a reboot performed), you should be good if an error occurs the next time. The memory dump should be about as large as the amount of RAM in the machine (it's a complete memory dump).