From your description, my first thought is it sounds like a host firmware issue. Have you checked that the system firmware/BIOS for your Cisco C240 M4 is fully up-to-date? Maybe try going into firmware and attempting to clear/reset the firmware configuration back to factory defaults, just in case. If none of that helps, please consider posting a screenshot/photo showing the PSOD as there may be other information on that screen which we can use to track down the problem.
Is it the same even for ESXi 6.0 (latest update)?
Are there any special settings for the CPU of the host? like hyper-threading? I had a similar problem with an HP Proliant server that is HT-enabled and after disabling this feature, ESXi works without any problem!Please mark my comment as the Correct Answer if this solution resolved your problem
What kind of image did you use?
Is it VMware image or customized with Cisco drivers?
Are there any warning/error messages on server management interface?
Usually PSODs are connected with firmware-driver issue. Try to update firmware on your server if you didn't do that.
One correction. This is a C220 M5, not an M4. The image is OEM enhanced, and not the standard VMWare ESXi image. The systems are error free, and we decommissioned and recommissioned one of the four servers to make sure we are not missing something there. We have only tried the 6.5 and 6.7 images. We actually have VMWare running on the server, which runs fine. The decision to reimage was to have a clean load. We suspect this is an image problem, but the PSOD doesn't give us much to go on.
6.7.0 release 13473784
could not start pcpu 1; no response to kick
cr0=0x8001003d cr2=0x0 cr3=0x100094000 cr4=0x10012c
Also talking to Cisco about this, but hoping someone would understand where the problem might be based on the data above.
Can you check such steps:
1) Check and update if you have newest BIOS firmware.
2) Reset BIOS settings to default