VMware Cloud Community
Cherry1337
Contributor
Contributor

ESXi 5.5 U3 HP Branded // ML30 // KMODE Exception not handled

Hello,

we have a major problem with an old ESXi 5.5 U3 Host.

Specs:
HP Proliant ML30 Gen9

ESXi 5.5 U3 HP Branded Image

We need to ensure that Windows 10 can be setup as VM on this system. Before we switched the physical Hardware to the ML30 this was possible.

Now we are unable to boot a Windows 10 1803 Iso on this Hypervisior. The U3 supports Windows 10. Also the ML30 in the list of supported devices.

When we start a new virtual Maschine from a Windows Iso we always get the same error "KMODE Exception not handled". Its directly after the first loading screen.

We already tried to boot up a existing maschine - same error. There is no Windows Dump file to analyse the error. Also the ESXi VM logs seems to be clean.

We invested some time to fix this error on our own:

- Upgrade the Maschine

- Remove all Device etc. from the maschine

- activated IDE Modus in the VMDK File

- Updatet all HP Drivers

Is there anyone out there with the same problem and a solution? Is there any error log about the hardware drivers that esxi is using? Maybe some drivers dont work correctly.

Upgrading the Host to 6.5 is the last thing we can do, before that we want to ensure there is no other solution arround. The support for Windows 10 on a ESXi 5.5 is given, it should be possible to get it running.

Thanks!

Reply
0 Kudos
5 Replies
MikeStoica
Expert
Expert

Reply
0 Kudos
Cherry1337
Contributor
Contributor

Hi, sorry this link isnt helpful at all. I already wrote that we dont have any chance to boot windows at all. So there is no possibility to change any driver or anything else.

Its a simply problem with the host/hardware. HP is unable to help us cause they dont even know what they support and what not. Also VMware tells us AHHH sry only technical guidance. The customer paid more than thousand euro to get support. And vmware tells us technical guidance = forum links. Really? They have many specialists that need 1-2 hours to fix this problem and all we get is forum links with useless stuff.... So we have no other chance to cancle the upgrade to 6.5 or higher and switch over to another hypervisor. The customer buys allways the support license and other stuff they dont even need. After 5 Years using this product without any support case vmware is still not helping in a critical thing.

Reply
0 Kudos
stereomax12
Contributor
Contributor

there is nothin on that website which I find useful but this one is a helpful for everyone

https://www.wibidata.com/

Reply
0 Kudos
unknownspammer
Contributor
Contributor

I have some working solutions, Check out the full post- https://trickyfi.com/fix-kmode-exception-not-handled-error/

Reply
0 Kudos
Andrewsmith123
Contributor
Contributor

here i found a complete guide related to kmode exception not handled error. Here you can find all the reasons and solutions effecting kmode not to work.

Try https://cybergeeksoftware.com/windows/kmode-exception-not-handled/

Reply
0 Kudos