Re: Failover cluster HP-Proliant crashes occationally with a blue screen

What version of the storport.sys are you running? Vendors might require a
specific version of storport.sys.

Also, with newer storport hotfixes, I've seen many issues with Proliant
servers due to issues with some HP integrated array drivers. See
http://support.microsoft.com/kb/940015 for more details...this KB singles
out storport hotfixes 932755 & 941276, but I've seen cases where other
versions above those listed in 932755 have also caused this issue.

Additionally, you might consider disabling the HP Insight storage agent
service as this can also trigger problems.

If this doesn't get you anywhere, you should open a case with Microsoft PSS
to examine the memory dumps dig deeper into this issue.

Hope this helps.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

<> wrote in message
news:4fe028dc-49af-49b9-b49a-...
> Hello,
>
> We have an SQL Server 2005 SP2 fail-over cluster with two HP Proliant
> DL385's each running Windows Server 2003 Enterprise x64 Edition
> Service Pack 2.
>
> Each Proliant has a QLogic QLA2340 HBA card and is connected to an IBM
> DS4800 (Firmware 07.10.23).
>
> Originally both Prolants were running HBA Driver 9.1.7.16 and Firmware
> 1.45.
>
> Under this configuration both machines were rebooting every so often
> and we are not sure why. They didn't do this when attached to our old
> SAN.
>
> The stop errors we get are 0x0000003b and 0x000000d1.
>
> One of the Proliants, which I'll refer to as Machine1 also
> occationally (3 times/month) crashes with a blue screen usually with
> the previously mentioned stop errors.
>
> In an attempt to fix this Machine1 was changed so it is running HBA
> Driver 9.1.4.15 and Firmware 1.52.
> Machine2 is still running HBA Driver 9.1.7.16 and Firmware 1.45.
>
> According to the IBM Compatibility Matrix the OS/HBA Firmware/HBA
> Driver/SAN Firmware are a match for Machine1 so we don't know why it
> is continuing to reboot.
>
> Machine1 also has produced a blue screen crash once after the HBA card
> firmware was upgraded.
>
> May I please know what I can do to troubleshoot this?
>
> Thank you.