Proliant ML530 G2 Bugcheck 0x0000001E, Exception Code 0x80000004, W2K SP #4

[SEBEMISMNUSA]

This is another attempt to get this posted on this forum.

A HP Proliant ML 530 G2 is intermittently crashing and rebooting. I am trying to determine why.

There are no errors being listed from the Insight agents nor from the monitoring Compaq Insight Manager 5.5 software nor the HP Insight Manager 7 sp2.3 software. The web page for the computer, https://computer:2381, also lists no errors - nothing failed nor degraded.

I am also aware of the Microsoft Technet article - KB148978.

Bugcheck 0x0000001E with Exception Code of 0x80000004
When a bugcheck 0000001e error occurs with an exception code of 80000004, it may indicate that there is faulty hardware on the computer.

This computer has been running fine since November 22, 2002 until March 29, 2004 - no crashes.

I have additional details in the attached file. It has many more details on this computer (hardware installed - all HP, software installed W2k server sp # 4 plus the numerous Microsoft security updates. On April 21, 2004, I installed the Microsoft security updates MS04-011 to MS04-014. I also installed the Proliant Support Pack version 7.00A.

End.

[Jay Lillie]

Similar situation. Posting my Bugcheck information for comparison...

Win2K Adv Server (SP4 + hotfixes)

Compaq Proliant ML570 Quad Processors 4GB RAM

Started happening about once a week over the last month... trying to determine if related to more sporadic (and uninvestigated) crashes noted periodically since Dec.

I notice you're running SQL on your boxes (among others...) We're supporting Lotus Domino on ours, so this seems to confirm that this is likely an issue between Compaq H/W and Win2K.

BugCheck, STOP: 0x0000001E (0x80000004, 0xDD46B2C8, 0xFCE6F640, 0xFCE6F640)

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 80000004, The exception code that was not handled
Arg2: dd46b2c8, The address that the exception occurred at
Arg3: fce6f640, Parameter 0 of the exception
Arg4: fce6f640, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

FAULTING_IP:
nt!KiFreezeExecutionLock+8
dd46b2c8 c3 ret

EXCEPTION_PARAMETER1: fce6f640

EXCEPTION_PARAMETER2: fce6f640

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x1E

LAST_CONTROL_TRANSFER: from dd40e5b0 to dd42f3e6

STACK_TEXT:
fdd379ac dd40e5b0 00000000 00010017 00000000 nt!ZwAdjustGroupsToken+0x6
fdd37d44 dd467735 fdd37d60 00000000 fdd37db4 nt!CcWriteBehind+0x1a4
fdd37db4 00000000 fd105e68 00000000 e2847ee8 nt!ExRaiseStatus+0xb1


FOLLOWUP_IP:
nt!KiFreezeExecutionLock+8
dd46b2c8 c3 ret

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiFreezeExecutionLock+8

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 403d35e2

STACK_COMMAND: kb

BUCKET_ID: 0x1E_nt!KiFreezeExecutionLock+8

Followup: MachineOwner
---------

[JohnWRuffo]

First off, make sure you have the latest bios, there are some fixes in this one:
http://h18023.www1.hp.com/support/files/server/us/download/20864.html

After you have the latest bios installed, go into the bios and make sure that the Array Controller and any other boards are configured. Confirm the boot order and the correct O/S is selected.

Save this configuration.

Once the configuration is saved, you should not see this problem arrise... unless you have a "hardware" problem.
The Bug Check you listed ( http://support.microsoft.com/default.aspx?scid=kb;en-us;148978&Product=nts40 ) looks like a cache problem. Does your 530 have both processors? Could be a PPM going bad.

[JohnWRuffo]

Jay:

Take a look at this advisory: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&taskId=110&prodSeriesId=316545&prodTypeId=15351&objectID=PSD_EM040428_CW01
if it applies?

[Prashant (I am Back)]

Hi,

Seems to be you have tried all
But please do try this also
http://h18007.www1.hp.com/support/files/server/us/download/20864.html

Which Fixes :

Resolved an intermittent problem which may manifest itself as a Windows blue screen, Linux kernel panic (kernel oops), or a system lock-up after which the OS is halted and requires a reboot. These OS problems may occur during installation of the HP ProLiant Support Pack (PSP) or anytime after installation. This problem is seen more frequently with higher speed processors.

The Windows blue screen failure code may vary but the most frequently observed bug check stop code values are as follows:

0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x0000001E KMODE_EXCEPTION_NOT_HANDLED
0x0000000A IRQL_NOT_LESS_OR_EQUAL
0x0000001A MEMORY_MANAGEMENT
0x000000C2 BAD_POOL_CALLER
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The Windows failure occurs when running the HP ProLiant Advanced System Management Controller Driver or the HP ProLiant iLO Advanced and Enhanced System Management Controller Driver. The failure can occur when the system is idle or under load.

Regards,
Prashant S.

[SEBEMISMNUSA]

June 3, 2004

In summary, using HP Version Control Manager 2.0x and the Version control agent 2.0x., I quickly identified what firmware and drivers were not current. I updated everything (as I was planning to contact HP in case the crashes/blue screens continued). The firmware/drivers were relatively current. There were a few yellow icons in version control agent. This computer has been updated about once per year for firmware & drivers.
So far, this has stopped this blue screen/crashes.

End.