PF Exception PSOD iSCSI HP Blade BL620 G7

[VidyaB]

I have the following configuration:

HP c3000 enclosure with 2 PS and 4 Fans

HP Onboard Administrator Module

HP KVM Module

HP 1GB Ethernet Pass-Thru Module

HP BL620c G7 with Intel Xeon 28xx Processors and 64 GB RAM

HP 320GB IO Accelerator Module

Corsair USB Drive plugged-in to Onboard USB Module

Intel 520 SSD

HP iSCSI Mezzanine Card

Drobo B800i

ESXi installed is HP Custom OEM version (VMware-ESXi-5.1.0-799733-HP-5.34.23) downloaded from VMware site upgraded using depot file (VMware-ESXi-5.1.0-Update1-1065491-HP-5.50.26-depot) to the latest available version.

There are 2 networks on the box. One network is to communicate with all the machines and the other network is SAN connected iSCSI Port #2 of Drobo B800i.

ESXi box connects to 2 TB Multi-Cluster LUN on Drobo B800i via SAN network creating a SAN datastore for ESXi.

There are 2 VMs installed on the ESXi box. A Windows 2012 server and other Windows 7.

Windows 2012 server VM is stored on SAN datastore and directly connects to NTFS LUNs on Drobo using Microsoft iSCSI Adapter and the mapping drives are shared using NFS essentially acting as file sever.

Window 7 VM is stored on HP IO Accelerator datastore. When I am copying any file from local disk on Windows 7 VM to a NFS share on Windows 2012 server, I am getting Pink Screen of Death (PSOD) with PF Exception 14.

Any help in identifying root cause of this problem is greatly appreciated.

[kermic]

When dealing with vmkernel PSOD it is usually recommended to submit a ticket to VMware Support. Those guys have a lot more experience and documentation / info available on interpreting the error codes and dealing with these issues.
I know that this is not very helpful, however it's the thing that I would do.

[SatyS]

Hi

This may be caused by either a hardware or a software issue.

Please try the resolution for the same in below links.

VMware KB: Understanding Exception 13 and Exception 14 purple diagnostic screen events in ESX 3.x/4....

VMware KB: ESX/ESXi hosts fail with a purple diagnostic screen and report the error: #PF Exception(1...

But it says that "This issue does not affect ESXi 5.1".Just try a reboot and see whether this resolves the issue.

Regards,

SatyS

If you find this useful,mark the answer as correct/helpful

[VidyaB]

Thank you for your quick response kermic and SatyS.

SatyS -- I have already tried reboot, reinstall and change all four 16 GB OEM memory modules.

The same setup is working on another server minus Windows 2012 server.

I will submit a ticket to VMware and see if it leads to solution or not.

[admin]

You have to reboot only when the below condition is satisfied;

ps -c  | awk {'print $1'} | sort -n | tail -n 1

If the output returns a value of 100,000 or above it is recommended to schedule a reboot.

Did you check that the GOS configurations are supported on the ESXi versions that you have used .?

IF yes please make sure that your configurations doesn't fall into the scenarios mentioned below;

VMware Knowledge Base Documents:

1. http://kb.vmware.com/kb/2006859

2. http://kb.vmware.com/kb/2021887

3. http://kb.vmware.com/kb/2033723

4. http://kb.vmware.com/kb/2037366

~dGeoregy

[VidyaB · Accepted solution]

Thank you dGeorgey for your response.

I have looked into those VMware KB documents but they are not applicable to my scenario.

My problem is Solved.

I have replaced Windows 2012 server with Windows 2008 R2 server. Now everything works fine. ESXi PSOD is gone.