I can run for hours a VM (windows 7 or 8.1) guest OS on Windows 10 technical preview, but as soon as I go to shut down or suspend the VM, it freezes and then crashes the host OS with a DPC_WATCHDOG_VIOLATION exception. Has anyone seen this before?
I get this same effect after upgrading build 9879
Yes, I can confirm the same behavior. Tested on two different hardware.
I too have the same problem. With Windows 10 TP + build 9879 (i repaired the Workstation TP install to see if it would help, but no).
Is there anything you need from specs or data wise to help?
EDIT: I checked with older versions of Vmware Workstation. (10.0.4) and that one crashes as well. And it gives me no "network bridge" so it seems i wont get anywhere.
Message was edited by: Robert Kommeren
Yes, I have the exact same thing. Whenever I try to shutdown a VM or even a reboot... my Windows 10 Enterprise (9879) {CLEAN INSTALL} will _COMPLETELY_ freeze and I have to restart my computer.
It did not do this before the clean install to build 9879. And yes, for me, Bridged Networking is also broken
Windows 10 Technical Preview Enterprise Build 9879 (64-bit)
Intel i5-2500K
Yeah, same here. I tried to go back a version to 10.0.3 and 10.0.4. Crash on shutdown/suspend.
Tried to clean registry for a fresh install, didnt work. And in the end i just go with it. Ill crash when i am done so to speak 🙂
What I figured out just now that forcefully killing vmware-vmx.exe does not freeze my system. (Of course this is not a fix and not recommended to use to kill your VMs)
But better than to crash on "exit" Nice thanks!
Same here!
It's a DPC_WATCHDOG_VIOLATION (133)
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x133 PROCESS_NAME: vmware-vmx-deb CURRENT_IRQL: d ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from fffff80135cadbe6 to fffff80135cb0502 STACK_TEXT: ffffd000`3f5f7c90 fffff801`35cadbe6 : 00000000`00000000 fffff780`00000320 00000000`00000000 00000000`000095cd : nt!KeAccumulateTicks+0x652 ffffd000`3f5f7d20 fffff801`35c229b5 : edb00002`6f099963 ffffd000`411f8568 fffff801`36032ec0 ffffe001`c4e00f00 : nt!KeClockInterruptNotify+0x906 ffffd000`3f5f7f40 fffff801`35d39bd7 : ffffe001`00000000 fffff801`35da789f 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15 ffffd000`3f5f7f70 fffff801`35dba8da : ffffe001`c4e00f00 0000000f`ffffffff fffff801`36032ec0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x77 ffffd000`3f5f7fb0 fffff801`35dbaf27 : 00000000`00000000 00000000`00000000 0000000f`ffffffff fffff801`35cc7046 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea ffffd000`411f81b0 fffff801`35cc9b88 : 00000000`00000000 fffffa80`00000001 fffffa80`18ba2800 00000000`0000000b : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffd000`411f8340 fffff801`35ce9315 : 00000000`00000000 ffffffff`ffffffff ffffe001`c4c00801 ffffd000`3f780180 : nt!MiDeleteSystemPagableVm+0x948 ffffd000`411f8510 fffff801`35cb90f2 : fffffa80`18ba3000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFreePagedPoolPages+0x285 ffffd000`411f86a0 fffff801`35ec77ed : ffffc001`8fb8d000 ffffd000`411f8838 00000000`00000000 ffffc001`00000001 : nt!ExFreeLargePool+0x5a2 ffffd000`411f8750 fffff801`360cd17a : ffffc001`8fb8d000 00000000`00000000 ffffe001`c5f1b230 00000000`74536d4d : nt!ExFreePoolWithTag+0x7ed ffffd000`411f8820 fffff801`35cbc9be : 00000000`00000002 ffffd000`411f88a0 00000000`00000002 00000000`00000000 : nt!MiSegmentDelete+0x82 ffffd000`411f8860 fffff801`36077531 : ffffc001`8f9bad60 00000000`ffff8001 00000000`00000001 00000000`00000000 : nt!MiCheckControlArea+0x22e ffffd000`411f88d0 fffff801`35ca0ef4 : 00000000`00000000 00000000`00000000 ffffd000`411f8a59 ffffc001`8f9bad90 : nt!ObpRemoveObjectRoutine+0x61 ffffd000`411f8930 fffff801`36060448 : 00000000`00000000 00000000`00000000 ffffd000`411f8a59 fffff6fb`00000001 : nt!ObfDereferenceObjectWithTag+0x94 ffffd000`411f8970 fffff801`3605e879 : 00000000`00000000 00000000`00000000 00000000`08490000 fffff801`35d47201 : nt!ObCloseHandleTableEntry+0x278 ffffd000`411f8ab0 fffff801`35dc3de3 : ffffd000`411f8b80 00000000`00000000 00000000`00000000 ffffe001`c5e66500 : nt!NtClose+0xc9 ffffd000`411f8b00 00007ffc`229a73ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`008cf5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`229a73ca
Seems like i am corrupting my VM's with the "kill vmware-vmx.exe" thing. Oh please mighty VMWare Workstation Gods, help me! 🙂
Same problem with after upgrading to Windows 10 TP build 9879.
I'm using VMware Workstation Tech Preview July 2014.
The same here. I am using vmware workstation v9 still...Waiting for next preview build...
Yeah! That's why I said do not use that :smileysilly:.. Well if it complains about the lock.. just visit the VM folder and delete the .lck folders.
No, not the locks it just wrecks the vmdk (or the FS on there) and i can start over. Ahh well, name of the game.
So with the guy testing on VMWare Workstation 9 we nou have the problem on 9,10 and TP...
For all i know the question stays the same:
Ow mighty VMWare Workstation gods, help us.*
*Because downgrading from a TP version of anykind (Windows/Workstation) never is an option 🙂
I didn't get this issue on build 9860.
I've noticed that it occurred since I installed build 9879.
I think MS was trying to fix some network adapter associated issue with build 9879 (not sure how though) but broke the important things for rest of us...
I suspect that it may be a general virtualization problem as Hyper-V on the host is also reported as causing problems with build 9879.
Hello,
same problem for me with build 9879 with Workstation 10 and 11 Preview. For network bridge problem, I resolved in 9860 build with "Restore Defaults", but in 9879 the trick doesn't work.
--
Regards,
Marco Mangiante
I was hoping the update Microsoft published to 9879 may have included a fix for this but still no change for me
VMWare Workstation is the only application I need to work with the TP and if that worked I can live with most other issues. I have a dilemma of whether or not to go back to Win 8.1 but I guess a fix (from either Microsoft or VMWare?) could resolve the issue at any point or even workaround so I'm trying to hold off.
Same here.. Unfortunately, I will have to go back to Windows 8.1 until this is resolved. At least I have my Tech Preview and Win 8.1 installs on different hard drives just in case something like this happened. I'll go back to the Tech Preview once this is fixed.. Build 9860 was awesome..
Jim