DL580G5 BAD POOL HEADER Stop Code 19

[Vague Assumption]

One day, after an elective reboot, my big beautiful G5 (and a crucial production server, may I add) handed me a blue screen.

Restarting cured it. Same thing just happened, 11/5/2010 5:30PM.

A pattern emerges: one bad restart followed by one good restart.

I have two pieces of evidence to offer: one is the attachment, the iml log, that gives the exact blue screen message, and the output from the OS.

Problem Event Name: BlueScreen

OS Version: 6.0.6002.2.2.0.274.10

Locale ID: 1033

Additional information about the problem:

BCCode: 19

BCP1: 0000000000000021

BCP2: FFFFFA804151F000

BCP3: 000000000000DCA0

BCP4: 0000000000000000

OS Version: 6_0_6002

Service Pack: 2_0

Product: 274_3

Files that help describe the problem:

C:\Windows\Minidump\Mini110510-01.dmp

C:\Users\mwilson\AppData\Local\Temp\1\WER-417396-0.sysdata.xml

C:\Users\mwilson\AppData\Local\Temp\1\WER7C02.tmp.version.txt

Read our privacy statement:

http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409


Here is an excerpt from the iml.html file:


1. Failed Operating System 10/22/2010 20:00 10/22/2010 20:00 1 System Crash - Message: BugCheck, STOP: 0x00000019 (0x0000000000000021, 0xFFFFFA8041038000, 0x000000000000D9B0, 0x00720067002D006C)

2. Failed Operating System 11/05/2010 17:15
11/05/2010 17:15 1 System Crash - Message: BugCheck, STOP: 0x00000019 (0x0000000000000021, 0xFFFFFA804151F000, 0x000000000000DCA0, 0x0000000000000000

[Mi6t0]

Can you upload the dump file somewhere? Or install microsoft debugging tools and open it. Maybe this could give some more info...

Is it windows 2003?

[Erdogan Temur]

Hi,

The issue is documented in the Microsoft Knowledgebase (KB)

Click here to access the technical article at: http://support.microsoft.com/?id=976443

Installing the fix from this KB resolves the issue. As stated in the KB 976443, "the iSCSI driver (Msiscsi.sys) does not manage allocated pool space correctly. This behavior leads to pool corruption. Therefore, when the corrupted pool is accessed, the system triggers the stop code 0x00000019."

regards

[Vague Assumption]

Thanks, Erdogan.

That's the best data I've got so far.

But:

Two hangups: wrong OS, and I wasn't managing SCSI -- in the classical sense of the work, working with the initiators. Can we consider restarting a 'managing of iSCSI?'

Lucky guess on iSCSI! I happen to be using it, not FC.

My OS is W2K8 SP2, not R2;

The cluster does have one instance of SQL2K8
R2, however.

Thanks for reading, though.