Thursday, June 6, 2013

Citrix PVS and The Blue Screen of Death

Hi Friends,

I ran into a nasty error the other day that I'd like to share with you.  So a little background.  I was creating a Citrix PVS golden image and everything seemed to be working great.  I'm running ESXi 5.0 with PVS 6.1 and XenDesktop 5.6.  I took the default E1000 network card when I was building my golden image and boot times were horribly slow.  I remembered I had some issues with the E1000 settings in the past, but I can hardly remember what I had for breakfast yesterday...  I looked around and found this article on the Citrix site http://support.citrix.com/article/CTX131993 that says to use the VMXNet3 NIC.  No problem, add a new VMXNet3 NIC in vCenter and delete the old E1000 NIC.

I switched my golden image from hard disk boot to vdisk boot, it booted MUCH faster and everything seemed to be working great.  I put my vdisk into Standard Image mode and tried to boot up my PVS clones.  Oh NO, not the BLUE SCREEN of DEATH!


























Thanks goodness for Google!  I started searching and found this article written by Jan Hendriks
http://jhmeier.de/2013/02/19/citrix-pvs-6-1-target-device-fails-to-start-on-vmware-esxi-5-1-with-a-blue-screen/ which totally saved me!  It describes the error I was seeing and pointed to this Citrix article http://support.citrix.com/article/CTX125361, which pointed to these Microsoft articles http://support.microsoft.com/kb/2344941 and/or http://support.microsoft.com/kb/2550978.  I guess when I replaced my E1000 for the VMXNet3 I introduced this.  Luckily there was a hotfix available!

I installed the hotfix and it worked!!

So what does this teach us?  I don't know....  :-)

Until Next Time!
-Brain

1 comment:

  1. It’s frustrating when the blue screen of appears out of nowhere. It was good that you found a fix that saved your computer. What does it teach us? I am not sure either, but save your files and backup in case the things you read on the internet didn’t work right, or for easy file transition in case the problem is with the PC itself. -- Ruby

    ReplyDelete