VMware Global Community
cyrker
Contributor
Contributor

Serveur ESX 5.1 patched : "blue screen" on all the VM Windows "problem with the driver : cismbios.sys "

Hello,

All our servers ESX 5.1 has been updated with all the patchs dedicated for ESX 5.1.

And then, all the VM Windows has crashed with a "blue screen" related with the driver "cismbios.sys".

Before that, all the VM was running normally.

What is necessary to do in this case ?

Regards,

Reply
0 Kudos
5 Replies
cyrker
Contributor
Contributor

21 views, and no reply ...Smiley Sad

Reply
0 Kudos
Cstark
Contributor
Contributor

Hi,

We have experienced the same issue with cismbios.sys since patching ESX 5.1. We first thought this was VMware tools but removing made no difference, we narrowed it down to the LANDesk agent, when removed the blue screens would stop (with VMware tools reinstalled).

LANDesk version: 9.50.0.530

Do you have LANDesk installed? We have a case logged just now with VMware.

Reply
0 Kudos
ct2
Contributor
Contributor

We have a 2003 Server running on VSphere 5.5 no problems. When we move it to VSphere 6.0 We get Exactly the same issue we move it back to 5.5 no issues: We do have LANDESK installed and are looking into it.

Reply
0 Kudos
Cstark
Contributor
Contributor

You're probably aware, there's a temp solution that I posted here http://chrisstark.co/2015/03/vsphere-5-1-patch-may-cause-landesk-cismbios-sys-blue-screen/ which might be of help.

If you change/implement the following registry key it will stop the blue screening:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\CISMBIOS]

Start=dword:00000004

LANDesk are still testing a suitable fix.

Reply
0 Kudos
ct2
Contributor
Contributor

Thanks Chris, Landesk have confirmed this is a known defect (TFS 303111) and released a component patch LD96-CP_AM-2015-0321. According to LD support this patch is applicable for the 9.6 environment but will be tested targeting 9.5 environment shortly.

I have also attempted moving a win 7 vm to Vsphere 6. with a different BSOD result. Removing Landesk resulted in a successful move to vsphere 6. I will wait for the patch to be tested  and pushed before moving the remaining VMs.

Reply
0 Kudos