VMware Communities
cjcilino
Contributor
Contributor

Win 10 Guest Crashing with error "Hal Initilization Failed" when Win 10 host laptop goes to sleep/hibernates

I have a laptop running Win 10 1903 (host). I have VM (Workstation Pro 15.1.0) running Win 10 1903 (Guest).

When I close my laptop or if it hibernates and I forget to suspend my VM it crashes saying there was a HAL initilization error (see screenshot below):

2019-07-25_08h36_03.png

Of course my power settings on the lap top are set to put it to sleep after 20 min. I've used VMWare for awhile on previous versions of windows. When the host would go to sleep it would automatically suspend the guest.

Can someone help me prevent these crashes on my guest VMs? Thanks

14 Replies
continuum
Immortal
Immortal

> When the host would go to sleep it would automatically suspend the guest.

That is the easy part - many users reported problems with resuming VMs after the host woke up from sleep / hibernation.

The safe approach is to suspend the VM before you allow your host to go to sleep


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
cjcilino
Contributor
Contributor

The safe approach is to suspend the VM before you allow your host to go to sleep

Right... I was hoping to avoid that. I didn't know if the host could send a message to the guest to suspend automatically. Seems like that's the way it has worked in the past.

Reply
0 Kudos
Sambzap
Contributor
Contributor

Is this still the recommendation. I find my Win10 Guest crashed after a host wake up.

Nothing can be done automatically?

Reply
0 Kudos
jac2jac2
Contributor
Contributor

I have the same issue, but only just started noticing it.  W10 host, W10 WS.  My old XP VM doesn't have the same issue. :-).

Reply
0 Kudos
Jatz76
Contributor
Contributor

I've had the same issue for a since I upgraded to a Dell Precision 5530. It came with the Windows 10 Pro 1903 (march). I think it might have something to do with Windows Smart Sleep. Haven't found a fix so far but am getting very tired of loosing my work. Surely vmware can find a fix, many people are having this issue.

masi0
Contributor
Contributor

I am getting exactly the same issue on XPS 7590 and Windows 10 guest

Despite system runs on AC it is having issues with VM guest after ~30 minutes of PC with screen off

Reply
0 Kudos
Swatboss
Contributor
Contributor

I am receiving the same error, but my machine is not sleeping...

Host Specs:

Machine: HP Proliant DL380P Gen8

OS: Windows Server 2019 Datacenter

OS Version: 1809

Client Software:

VMWare Workstation 15 Pro

Reply
0 Kudos
nzi95001
Contributor
Contributor

Same error here on two Windows 10 VMs.

Reply
0 Kudos
thatoneITguy
Contributor
Contributor

Having the same issue. It started after 1909 upgrade from 1607. Sleep has always been disabled on the host, never on the guest. Seems like this is a windows undocumented feature.

 

I'm running 16.1.0 build-17198959

 

022521-58234-01.dmp 2/23/2021 12:00:32 PM HAL_INITIALIZATION_FAILED 0x0000005c 00000000`00000115 fffff794`80015470 00000000`00021681 ffffffff`c0000001 storport.sys storport.sys+df30 Microsoft Storage Port Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.488 (WinBuild.160101.0800) x64 ntoskrnl.exe+3f5780 C:\WINDOWS\Minidump\022521-58234-01.dmp 6 15 19041 713,308 2/25/2021 4:23:21 PM
022321-35171-01.dmp 2/17/2021 10:12:37 PM HAL_INITIALIZATION_FAILED 0x0000005c 00000000`00000115 fffff7b2`c0015470 00000000`0000fb4f ffffffff`c0000001 ntoskrnl.exe ntoskrnl.exe+3f5780 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.685 (WinBuild.160101.0800) x64 ntoskrnl.exe+3f5780 C:\WINDOWS\Minidump\022321-35171-01.dmp 6 15 19041 741,876 2/23/2021 9:18:40 AM
021721-43093-01.dmp 2/15/2021 3:01:05 PM HAL_INITIALIZATION_FAILED 0x0000005c 00000000`00000115 fffff7cd`40015470 00000000`000089a3 ffffffff`c0000001 ndis.sys ndis.sys+7960 Network Driver Interface Specification (NDIS) Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.1 (WinBuild.160101.0800) x64 ntoskrnl.exe+3f5780 C:\WINDOWS\Minidump\021721-43093-01.dmp 6 15 19041 1,013,948 2/17/2021 7:54:11 AM
020821-17375-01.dmp 2/7/2021 11:23:15 AM HAL_INITIALIZATION_FAILED 0x0000005c 00000000`00000115 fffff782`c0015470 00000000`00008540 ffffffff`c0000001 ntoskrnl.exe ntoskrnl.exe+3f5780 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.685 (WinBuild.160101.0800) x64 ntoskrnl.exe+3f5780 C:\WINDOWS\Minidump\020821-17375-01.dmp 6 15 19041 852,028 2/8/2021 12:12:32 PM
020521-48906-01.dmp 2/4/2021 10:39:04 AM HAL_INITIALIZATION_FAILED 0x0000005c 00000000`00000115 fffff79c`00015470 00000000`00004690 ffffffff`c0000001 ntoskrnl.exe ntoskrnl.exe+3f5780 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.685 (WinBuild.160101.0800) x64 ntoskrnl.exe+3f5780 C:\WINDOWS\Minidump\020521-48906-01.dmp 6 15 19041 1,452,284 2/5/2021 11:16:47 AM

Has anyone seen this to resolution?

Reply
0 Kudos
ems4ty
Contributor
Contributor

I have a Dell T320 with a Xeon E5-2470v2 Processor and 48 GB Memory.  The Host Server is running a fresh installation of Win Server 2019 Standard.  Just installed clean and performed all windows updates.

Using VMWare Player 16, I have (2) Guest OS Machines.  

    1)  1st Guest is a Windows 10 Physical to VM Creation performed with Vcenter Converter from a remote computer.  This VM starts and runs fine and I haven't experienced any issues.

    2)  2nd Guest is a fresh clean install of Win10Pro x64 and has all of the current updates installed.  This VM is experiencing the HAL Initialization Error Stop where the Guest OS Encounters the problem, gets the blue screen of death, and then just sits there and does nothing.  My only option is to logon to the Win2019 Server Host and then click on the VMPlayer VM and hit Reset Guest OS button.  After that, the VM comes back and goes online.

Both the VM's and the Host are set to never go to sleep in their power management configuration.  HDD's are set to never sleep as well.

Is there anything that anyone can point to that can solve this issue or is it just a random Windows 10 Guest OS running on VMWare issue?

Reply
0 Kudos
jedikcc
Contributor
Contributor

Were you able to find a solution?  I have the exact same problem.

Reply
0 Kudos
ems4ty
Contributor
Contributor

Ditch VMware.  Convert VMDK to VHD and run Hyper-V instead.  No issues after that.

Been running VMware for years.  Disappointed to not get an actual resolution.  Had another IT Professional monitor my situation and even he couldn't find out why, through checking various logs, does this happen.   I installed PRTG Monitoring Agent and found out that the HAL Initialization would occur at 3:25AM everytime.  

I'm assuming it's a Windows Update thing but no matter what we did, we could not stop this event from occurring.  It also appeared to happen at random, meaning it wasn't daily.  But let's say 3x a week or so.  What's even more aggravating is that the VM would never restart automatically like the BSOD says it was supposed to do.

We converted the problem VM to VHD and am running it via Hyper-V on the same server as a test and its hasn't mucked up once.  Soooooo, I believe it to be a VMWare issue and since I can't get a straight answer, I'm just about done dealing with VMWare.

Good luck.

Reply
0 Kudos
vfandrea
Contributor
Contributor

Hi , I have same problem , Host with WinSRV 2019 and VM with WinSrv2019... I got the BSOD and the VM doesn't reboot automatically.

I'm using Vmware Workstation PRO 16, the latest one and Win update done to both.

any solution from Vmware ???

Reply
0 Kudos
fpivot95
Contributor
Contributor

Hello, I'm having the same exact issue. Solutions proposed didn't work. Any ideas?

Reply
0 Kudos