VMware VMX Crash Running Win 10 x64 Build 10074

[NoelC1]

This is not a "request for support" but in the interest of helping VMware engineers find problems, and knowing full well Win 10 is beta software...

After running Win 10 build 10074 for more than a day, the virtual machine process crashed.

I've attached the VMware.log to this message, and I can provide additional supporting info via PM if requested.

-Noel

[bobvance]

Same here, including the exact error message:

NOT_REACHED d:/build/ob/bora-2496824/bora/devices/ahci/ahci_user.c:1530

Since installing preview 10074 on 2015-05-01, this has happened each time after ~1 day on an idle VM (I've been too busy last few days to play with win10 -- didn't even notice the first one 'til next day)

This did not happen on any earlier previews, including 10061 & 10071.

My Logs look very similar to yours.

The VM appears to be rocking along, with balloon messages every 30 mins.

Then, boom, BOTH times, 15 mins after previous balloon message, it craps out.

2015-05-01T18:17:19.848-04:00| vmx| I120: Log for VMware Workstation pid=6164 version=11.1.0

build=build-2496824 option=Release

...

2015-05-02T14:17:39.754-04:00| vmx| I120: MemSched: Balloon enabled 1 guestType 4 maxSize 0

2015-05-02T14:32:49.142-04:00| vcpu-0| I120: NOT_REACHED d:/build/ob/bora-

2496824/bora/devices/ahci/ahci_user.c:1530

2015-05-03T08:33:45.683-04:00| vmx| I120: Log for VMware Workstation pid=9788 version=11.1.0

build=build-2496824 option=Release

...

2015-05-03T08:33:47.716-04:00| vmx| I120: MemSched: Balloon enabled 1 guestType 0 maxSize 0

2015-05-03T09:03:47.952-04:00| vmx| I120: MemSched: Balloon enabled 1 guestType 4 maxSize 0

2015-05-03T09:33:48.566-04:00| vmx| I120: MemSched: Balloon enabled 1 guestType 4 maxSize 0

...

2015-05-04T08:34:11.197-04:00| vmx| I120: MemSched: Balloon enabled 1 guestType 4 maxSize 0

2015-05-04T08:49:18.584-04:00| vcpu-0| I120: NOT_REACHED d:/build/ob/bora-

2496824/bora/devices/ahci/ahci_user.c:1530

bv

[dariusd]

Thanks for the report, Noel and bobvance.  We've seen this issue in our own internal testing too, and we're investigating.

Thanks,

--

Darius

[bobvance]

FYI

The problem still occurred after installing 10074 from scratch from ISO,

with no new programs or utilities installed, and no Vmware Tools,

Originally, I had updated from 10071 where I had Vmware tools installed

along with several utilities and apps, including Office 2000.

bv

[JonRowlison]

I'll join the "me too" list. Same error, same situation (>24 hours idle) and this was also a 10074 scratch build from ISO.

[Chamel123]

Got the same issue but in my case, if the VM is running with no user in session the VM doesn't crash. Must have something to do with the user profile and not with the Windows 10 services that are running with no user in session. Maybe this could help to narrow down the problem.

[bobvance]

I built another VM from scratch and left it NOT logged in,

but it also crashed after a day.

For most of the time, it was the only VM running.

(I'm running on a desktop w only 4GB memory,

so usually have only one VM in play mode.)

For the Win10 VM, I allocated 1.5 GB.

bv

[dariusd · Accepted solution]

OK, we have a fix queued up for the next patch release to address this problem.

It turns out that the most recent builds of Windows 10 will sometimes issue S.M.A.R.T. commands to SATA devices even when the device reports that it does not support S.M.A.R.T., and the unexpected commands are confusing our SATA emulation and leading to the error you're seeing.

The fix will simply ignore the unexpected S.M.A.R.T. commands.

I can't say exactly when we'll have the update in your hands, but I'm hoping it will be reasonably soon.  Sorry for the trouble you've all encountered!

Thanks,

--

Darius

[bobvance]

Excellent.

Thanks.

bv

[NoelC1]

Thank you (and all the engineering/support teams) Darius.

Have you reported it to Microsoft?  Regardless, I'll go ahead and do so just to be sure they know.

-Noel

[peetz]

This issue also occurs with VMware ESXi (including 6.0.0b).

I worked around it by removing the SATA CD drive from the VM and adding a "legacy" IDE CD drive.

Andreas

[TomMoreno]

I am having the same issue on ESX 6.0.0 with full version Win10 Pro.

I recently set up a Win 10 VM to host a Quickbooks server for our financial staff and every other day the machine crashes with the same error.

I'm going to try removing the SATA CD Drive tonight to see if that does the trick.

Thanks!

[NoelC1]

What exact version of VMware are you running, and on what host OS, Tom?

Edit:  I see that you mentioned ESX 6.0.0...  Is that the 'b' suffix release.

For what it's worth, I never saw the error again after the next Workstation 11 update (I have 11.1.2 build-2780323 now), and I've run Win 10 (build 10240) in a VM for days on end.

-Noel

[TomMoreno]

Hi Noel,

I'm running in in Hypervisor ESX 6.0.0 (2494585) and the OS is Win 10 Pro 10240.

VM was created in Fusion Pro 8.0.0 (2985594) as a Hardware v11 machine and uploaded to ESX via Fusion Pro.

Thanks!

[vicenac]

This happens with the production version of Win 10 on hardware version 11 with the newly introduced SATA CD-ROM. We have a Win 10 on version 8 with the old IDE CD-ROM and that has no issues.

I removed the SATA CD-ROM and added the old IDE CD-ROM instead, as suggested in other posts. Keeping fingers crossed.

Our ESX is ESX 6.0.0, 3029758 (Update 1).

I hope this helps!

[chaithu4u]

great answer thank you very much

[smr222]

KB article 2138543 has been published on this issue

Windows 10 VM crashes on ESXi 6.0 (2138543)

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2138543

Removing the SATA CD ROM worked for me (ESXi6U1)

Thanks to everyone

-Stefan

[Bleeder]

KB 2138543 now says "You are not authorized to access this article. It may have been moved or the reference is out-of-date."

[MLorenz]

Hello,

having the same error.

Windows 10 64

I switched Hardware from 8 to 10 - but the error persists

Is there a fix available in the meantime?

Thanks

[smr222]

it seems vmware pulled KB2138543 soon after it was published...