How to solve VMware View Virutal Machine deployment fails with a purple diagnostic screen and the error: PF Exception 14 - GFCPutSectionHeader (2076931)?

VMware View deploy လုပ်ထားတဲ့ VMware ESXi 5.5 Hypervisor တွေမှာ အောက်ကလို Purple Diagnostic Screen နဲ့ System Logs မျိုးကို တွေ့ရင် ဘာလုပ်ကြမလဲဗျ။

Logs:
2015-01-06T15:09:07.842Z cpu3:32848)@BlueScreen: #PF Exception 14 in world 32848:CmdCompl-3 IP 0x41802f0a5db1 addr 0x6c
PTEs:0x88cf47e023;0x88cf47f023;0x8077b72023;0x0;
2015-01-06T15:09:07.842Z cpu3:32848)Code start: 0x41802e400000 VMK uptime: 137:10:13:26.272
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141da00:[0x41802f0a5db1]GFCPutSectionHeader@esx#nover+0x1 stack: 0x41240141da80
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141daa0:[0x41802f0b7332]SEResource_UnlockResources@esx#nover+0x13a stack: 0x41240141dae0
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141dac0:[0x41802f0bb60d]SETxnGTEFaultCleanupCompletionArgs@esx#nover+0x65 stack: 0x0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db00:[0x41802f0bb65e]SETxnGTEFaultCompletion@esx#nover+0x4e stack: 0x410a7bd54cc0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db40:[0x41802f0ace4f]SESparseCheckAndReleaseLocks@esx#nover+0x10b stack: 0x41240141dbc0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db70:[0x41802f0afa6f]SESparseAsyncDataDone@esx#nover+0x43 stack: 0x4132c1e7d2c0
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dba0:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x410c3f360fb0
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dbd0:[0x41802e6ce2c2]FS_IOAccessDone@vmkernel#nover+0x56 stack: 0x412ec00e8b18
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dc00:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x412ec1b31480
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc30:[0x41802e42d48f]AsyncCompleteOneIO@vmkernel#nover+0x16b stack: 0x412ec23e6080
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc60:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x41240141dc90
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc90:[0x41802e6fe241]FDSAsyncTokenIODone@vmkernel#nover+0xdd stack: 0x1022
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141dd90:[0x41802e7214c3]SCSICompleteDeviceCommand@vmkernel#nover+0x46f stack: 0x410a7bd32488
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141ddc0:[0x41802ed0bebe]nmp_CompleteCommandForDevice@com.vmware.vmkapi#v2_2_0_0+0x82 stack:
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141ded0:[0x41802ed0c18e]nmp_CompleteCommandForPath@com.vmware.vmkapi#v2_2_0_0+0x12a stack: 0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141df60:[0x41802e742475]SCSICompletePathCommand@vmkernel#nover+0x2a5 stack: 0x41240141dfa0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141dfd0:[0x41802e7552c0]SCSICommandCompletionWorld@vmkernel#nover+0x19c stack: 0x0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141dff0:[0x41802e653532]CpuSched_StartWorld@vmkernel#nover+0xfa stack: 0x0
2015-01-06T15:09:07.853Z cpu3:32848)base fs=0x0 gs=0x418040c00000 Kgs=0x0

ဘာမှ ထွေထွေထူးထူး လုပ်စရာမလိုပါဘူး။
VMware က ပြောထားပြီးသားပါ Known Issue ပါတဲ့။ VMware ESXi 5.5 Patch 1 version အားလုံးမှာ ဖြစ်တဲ့ Error ပါတဲ့။
ဖြေရှင်းဖို့ အတွက် ESXi 5.5 Patch 02 ကို update လုပ်လိုက်ရုံပါပဲတဲ့ဗျာ။

အသေးစိတ်သိချင်ရင် ဒီမျာသာ သွားဖတ်ပေတော့ဗျို့ ။

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2076931

ပျော်ရွှင်ပါစေဗျာ။
(Be knowledgeable, pass it on then)