ProLiant Servers (ML,DL,SL)

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

 
SOLVED
Go to solution
LondonCentralIT
New Member

Re: Ilog Blue Screen Trap (BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE

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
HPE Pro

Re: Ilog Blue Screen Trap (BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE

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


Regards, AVI
CSCB ISS L2 Engineer - EMEA
Global SCupport Delivery
Technology Services, Enterprise Group

Accept or Kudo