%3Cp%3EToday%20I%20upgraded%20a%20customer%20to%20%3Cstrong%3EESXi%206.5%20Update%201%3C/strong%3E,%20but%20unfortunately%20some%20of%20them%20ended%20up%20purple%20screening%20at%20reboot%20after%20they%20were%20updated.%3C/p%3E%3Ch3%3EAffected%20Servers%20so%20far%3C/h3%3E%3Cul%3E%3Cli%3EHPE%20BL460c%20Gen9%3C/li%3E%3Cli%3EHPE%20DL360p%20Gen8%20(Reported%20by%20anonymous%20user)%3C/li%3E%3Cli%3EHPE%20DL380%20Gen9%20(Reported%20by%C2%A0Bernhard)%3C/li%3E%3Cli%3EHPE%20DL380%20Gen8%20(Reported%20by%20Ralf)%3C/li%3E%3Cli%3EHPE%20DL380p%20Gen9%20(Reported%20by%20Victor)%3C/li%3E%3C/ul%3E%3Ch3%3EPSOD%20Error%3C/h3%3E%3Cp%3E%3Cem%3EPSOD:%C2%A0#PF%20Exception%2014%20in%20world%2068297:sfcb-intelcim%20IP%200x41801b704d8f%20addr%200x443919649c000%3C/em%3E%3C/p%3E%3Cp%3E%3C!--more--%3E%3C/p%3E%3Cp%3EIn%20short%20the%20customer%20was%20running%20ESXi%205.5,%20and%20I%20reinstalled%20the%20servers%20using%20HPE%206.5%20Update%201%20OEM%20Image%20found%20here:%20%3Ca%20href=%22https://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI65U1-HPE&productId=614?src=vmw_so_vex_bknuts_793%22%3Ehttps://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI65U1-HPE&productId=614%3C/a%3E%3C/p%3E%3Cp%3EI%20configured%20the%20servers%20and%20found%20that%20VMware%20Update%20Manager%20had%203%20additional%20updates:%3C/p%3E%3Cp%3E%3Ca%20href=%22https://usercontent.one/wp/vm.knutsson.it/wp-content/uploads/2017/08/Selection_442.png%22%3E%3Cimg%20class=%22alignnone%20wp-image-532%22%20src=%22https://usercontent.one/wp/vm.knutsson.it/wp-content/uploads/2017/08/Selection_442-300x18.png%22%20alt=%22VUM%20Updates%22%20width=%22667%22%20height=%2240%22%20/%3E%3C/a%3E%3C/p%3E%3Cp%3EOddly%20it%20still%20wanted%20to%20install%20Update%201.%20I%20had%20already%20updated%20some%20Gen8%20servers,%20and%20they%20had%20no%20issue%20with%20me%20installing%20all%20updates,%20so%20I%20went%20ahead%20and%20installed%20all%20three%20updates.%20But%20in%20this%20case%20the%20server%20never%20came%20back%20online.%20Instead%20it%20kept%20giving%20a%20PSOD%20on%20boot:%3C/p%3E%5Bcaption%20id=%22attachment_534%22%20align=%22alignnone%22%20width=%22667%22%5D%3Ca%20href=%22https://usercontent.one/wp/vm.knutsson.it/wp-content/uploads/2017/08/Selection_439-1.png%22%3E%3Cimg%20class=%22wp-image-534%22%20src=%22https://usercontent.one/wp/vm.knutsson.it/wp-content/uploads/2017/08/Selection_439-1-300x220.png%22%20alt=%22PSOD%22%20width=%22667%22%20height=%22489%22%20/%3E%3C/a%3E%20#PF%20Exception%2014%20in%20world%2068297:sfcb-intelcim%20IP%200x41801b704d8f%20addr%200x443919649c000%5B/caption%5D%3Cp%3EAfter%20some%20investigation%20I%20found%20it%20to%20be%20caused%20by%20the%20Ixgben%20driver%20updates.%20It%20is%20a%20driver%20for%20Intel%20network%20adapters.%20This%20also%20corresponded%20with%20the%20PSOD%20coming%20from%20sfcb-intelcim.%3C/p%3E%3Cp%3EAnyway%20I%20contacted%20HPE%20Support,%20and%20the%20supported%20just%20heard%20of%20a%20similar%20case,%20so%20he%20wanted%20some%20logs%20and%20promised%20to%20return%20to%20me%20asap.%3C/p%3E%3Cp%3EHPE%20Support%20return%20a%20little%20later%20and%20told%20me%20that%20they%20do%20not%20have%20a%20record%20of%20the%20noted%20kernel%20exception,%20so%20I%20was%20probably%20among%20the%20first%20to%20experience%20the%20error,%20if%20not%20the%20first.%20Hooray%20I%20was%20the%20first!%3C/p%3E%3Ch3%3EWorkaround%3C/h3%3E%3Cp%3EHPE%20Returned%20and%20stated%20that%20those%20two%20updates%20should%20just%20be%20excluded,%20since%20it%20is%20a%20driver%20delivered%20by%20intel,%20and%20it%20does%20not%20work%20with%20the%20HPE%20firmware.%3C/p%3E%3Cp%3EYou%20should%20also%20avoid%20the%20VMware%206.5%20Update%201%20in%20Update%20Manager.%20I%20guess%20it%20also%20contains%20a%20ixgben%20driver%20from%20intel.%3C/p%3E%3Cp%3ETo%20quickly%20return%20to%20a%20working%20installation%20without%20reinstalling.%20you%20can%20press%20%3Cstrong%3EShift+R%3C/strong%3E%20during%20startup%20to%20get%20back%20to%20a%20working%20configuration.%20Thank%20you%20to%20my%20college%20%3Ca%20href=%22https://www.linkedin.com/in/abdec/%22%3EAndr%C3%A9%20Briand%20de%20Cr%C3%A9vecoeur%3C/a%3E%20for%20bringing%20this%20to%20my%20attention.%20%3Ca%20href=%22https://kb.vmware.com/kb/1033604?src=vmw_so_vex_bknuts_793%22%3Ehttps://kb.vmware.com/kb/1033604%3C/a%3E%3C/p%3E