Ilog Blue Screen Trap (BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE3))

[Icharus]

I get these kind of errors on my proliant ml350.

Blue Screen Trap (BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE3))

Blue Screen Trap (BugCheck, STOP: 0x000000D0 (0x00000008, 0xD0000002, 0x00000000, 0x80899707))


Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x00000004, 0xD0000002, 0x00000001, 0xB9ED7909))

[Cederberg · Accepted solution]

Hi!

Are you using the E200/E200i smart array adapter? if so you need to update the firmware to at least version 1.82

check this Microsoft KB which describes the issue.
http://support.microsoft.com/kb/969550

Regards.
//Cederberg

[Icharus]

Thanks for help, i reply here if driver update did not help.

[Erdogan Temur]

Hi,
install last support pack on system and than virus programs upgrade.

os version ?

That will also fix the problem :) Remember to assign points to answers that helped in your problem. So the forum stays alive...

[juan quesada]

hello,

look for a file with extention .dmp at %SystemRoot%\minidump... you will have several, of them (one matching each bluescreen) attach them here for analysis.

JQ

[Icharus]

Could not find the .dmp files, but last time bluescreen occured a few months ago.
I Updated yesterday those smart array drivers, hope it does not do bluescreen anymore.
Thanks for the help.

[Icharus]

And operating system is Microsoft windows 2003 small business

[juan quesada]

all BSOD auto save a dump file unless there is no enough page file avaliable at the time of the crash, try setting the recovery to minidumps, they are either 64kb (32 bits) or 128kb (64bits) ...so pagefile size will not be affected.

look for system properties --> start up and recovery.

JQ

[cgclondon]

Hello, same error here, but different kit:

Device Information

Blade Type Server Blade

Manufacturer HP

Product Name ProLiant BL460c G1

Part Number 416655-B21

System Board Spare Part Number 410299-001

Running Windows 2003 R2

Running SQL 2005

Blue Screen, our first time, but since this server is really important to us, I want to make sure that i understand what is the problem.

After restart, havent seen the error again... (at least for the next few hours)

The server restarted and when I first log in this is what I saw:

System Failure: Stop Error

Comment:

0x000000c5 (0x00000004,0xd0000002,0x0000000,0x8089bce3)

From the IML Log (blade manager)

Abnormal Program Termination (BugCheck, STOP: 0x000000C5 (0x00000000, 0xD0000002, 0x00000001, 0x8089C4BB))

Please help,

I try to attach the dump file, but seems that the site doesnt like it...

Thank you!

[cgclondon]

Just been checking the windows site, and the errors they mention are not the ones we refer in this post, what makes you think that that is the problem? You seen this happening before? previous experience? I dont want to embark myself in updating the firmware of my 14 blade servers thrying to prevent this from happening again, if im not 100% certain, hope you understand.

Thanks your help

[LondonCentralIT]

Same Problem again:

Abnormal Program Termination (BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE3))

Blade Type Server Blade

Manufacturer HP

Product Name ProLiant BL460c G1

Part Number 416655-B21

System Board Spare Part Number 410299-001

[Spectroscopy]

From the event log seen in the IML, I can assure you that it’s caused due to driver corruption pool.

A detailed explanation of the same:-

The DRIVER_CORRUPTED_EXPOOL bug check has a value of 0x000000C5. This indicates that the system attempted to access invalid memory at a process IRQL* that was too high.

(IRQL== Interrupt Request Level) is a hardware independent means with which Windows prioritises interrupts that come from the system's processors. On processor architectures which Windows runs on, hardware generates signals which are sent to an interrupt controller*.

Cause

The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.

In most cases, this bug check results if a driver corrupts a small allocation (less than PAGE_SIZE). Larger allocations result in bug check 0xD0 (DRIVER_CORRUPTED_MMPOOL).

Resolving the Problem

Too resolve this problem we need to collect the Dump to point out the Driver that is causing the issue and the pool table that is overflowing which is causing for a sporadic restart of the server. If you have recently installed any new software, check to see if it is properly installed. If there was any KB update done from MS kindly have a track of the KB NO. or revert it back to its state where the last machine backup was taken.

Further Log analysis will be posted 

Kudos