ESXi 5.5 host fails with the purple diagnostic screen error: VSCSIFilter_GetFilterPrivateData

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi 5.5 fails with the purple diagnostic screen.
• You see the error:

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)@BlueScreen: #PF Exception 14 in world 103492:hostd-worker IP 0x41802c2c094d addr 0x30

PTEs:0x1aefdb027;0x40cec6b027;0x0;

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)Code start: 0x41802c000000 VMK uptime: 21:06:32:38.296

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111dbc0:[0x41802c2c094d]VSCSIFilter_GetFilterPrivateData@vmkernel#nover+0x1 stack: 0x4136c7d

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111dbf0:[0x41802c2c0bc3]VSCSIFilter_IssueInternalCommand@vmkernel#nover+0xc3 stack: 0x410961

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111dc60:[0x41802c6510ad]CBRC_FileSyncRead@<None>#<None>+0xb1 stack: 0x0

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111dd70:[0x41802c64aa65]CBRC_DigestRecompute@<None>#<None>+0x291 stack: 0x1391

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111dda0:[0x41802c6519d2]CBRC_FilterDigestRecompute@<None>#<None>+0x36 stack: 0x20

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111de30:[0x41802c406eee]VSI_SetInfo@vmkernel#nover+0x322 stack: 0x411424b18120

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111dec0:[0x41802c5b804b]UWVMKSyscallUnpackVSI_Set@<None>#<None>+0xef stack: 0x41245111df10

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111df00:[0x41802c57da47]User_UWVMKSyscallHandler@<None>#<None>+0x243 stack: 0x41245111df20

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111df10:[0x41802c0aa65d]User_UWVMKSyscallHandler@vmkernel#nover+0x1d stack: 0x275c3918

YYYY-MM-DD TIME cpu24:103492 opID=3e7060fb)0x41245111df20:[0x41802c0f1064]gate_entry@vmkernel#nover+0x64 stack: 0x0


Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi 5.5

Resolution

This is a known issue affecting VMware ESXi 5.5.x.

 

This issue is resolved in VMware ESXi 5.5 Update 3.

Additional Information