VMware Infrastructure Client 2.5.0 causes BSOD STOP 0x8E

Discussion in 'Windows Virtual Machine' started by Felix Buenemann, Feb 5, 2009.

  1. Felix Buenemann

    Felix Buenemann Bit poster

    Messages:
    4
    As subject says. Starting the VMware Infrastructure Client 2.5.0 as shipped with VMware Infrastructure 3i/vCenter 2.5 under Parallels Desktop for Max 4.0.* causes instant BSOD with STOP 0x8E on WXP PRO SP2 DE.
     
  2. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Seems this software after 2 -3 running causes BSOD on any OSes (tested on Windows XP, w2k3)
    I cleaned it up copying the following:

    C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\2.5\libeay32.dll & C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\2.5\ssleay32.dll

    To

    C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher

    and deleting
    VMware, fusioncache.dat, GDIPFONTCACHEV1.DAT, IconCache.db

    in this directory:

    %userprofile%\Local Settings\Application Data\
    but I deleted software after that
     
  3. Felix Buenemann

    Felix Buenemann Bit poster

    Messages:
    4
    I'm not sure what you mean by viclient causing BSOD on any OSes. I have never seen it BSOD on a physical Windows 2003 R2 host, nor on a physical Windows XP SP3 or using WIndows XP SP3 running under VMware Fusion.

    Regarding your tips: For me libeay32.dll and ssleay32.dll were already present in the Launcher directory with identical file sizes. And I couldn't delete %userprofile%\Local Settings˙Application Data\VMware, because the file hgfs.dat inside the VMware folder was in use. I remove the other files though and it still resulted in BSOD.
     

Share This Page