Vmworkstation Unknown Error Please Try Again
Hello nhsk4u
I am Dave, I volition help you with this.
Please upload whatsoever minidump files y'all have, I volition cheque those to meet if they provide any insight into a potential cause of the system crashes.
Open Windows File Explorer.
Navigate to C:\Windows\Minidump
Copy any minidump files onto your Desktop, and so zip those up.
Upload the null file to the Cloud (OneDrive, DropBox... etc.), so choose to share those and get a share link.
Then post the link here to the nada file, so we can have a wait for you.
___________________________________________________________________ Power to the Developer! MSI GV72 - 17.3", i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD
Was this reply helpful?
Was this reply helpful?
Hi nhsk4u
Your minidump files just bespeak memory (RAM) corruption no specific driver is listed
All drivers and BIOS on your B550 AORUS ELITE V2 motherboard seem to be fully upwards to date.
ane
Kicking into BIOS, if at that place is an XMP profile prepare on your RAM, det that to default.
ii
Expect to see if your organisation stabilizes, if not, the best option is to download the widely available gratuitous utility MemTest86, and then run a total 4 laissez passer scan with that to test your RAM for physical errors
___________________________________________________________________ Power to the Developer! MSI GV72 - 17.3", i7-8750H (Hex Cadre), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD
Was this respond helpful?
Hi DaveM121
have run Windows Retentiveness Diagnostic and information technology is clear. Kindly advise. cheers
Eventvwr:
The Windows Retentiveness Diagnostic tested the computer's memory and detected no errors
Was this reply helpful?
Hi nhsk4u
Windows Retentiveness Diagnostics is not a in depth as MemTest86, information technology would be best to un a full 4 laissez passer scan with that.
If no RAM errors are found, to try to force Windows 10 show any faulting drivers, the best pick would be to turn on Commuter Verifier, allow your PC crash 3 times, and then you must turn off Driver Verifier, and finally, upload any newly created minidump files
https://answers.microsoft.com/en-us/windows/for...
___________________________________________________________________ Ability to the Programmer! MSI GV72 - 17.three", i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD
Was this reply helpful?
Howdy DaveM121,
I have two DIMMS installed and performed beneath.
Removed DIMM1, booted on DIMM2 and tried powering ON vm, information technology crashed windows 10
Removed DIMM1, booted on DIMM1 and tried powering ON vm, it crashed windows 10
DIMM was installed on slot 2 & 4, Have changed them to one & 3 and tried powering ON vm, information technology crashed windows 10
Have enabled commuter verified and rebooted windows 10 to take affect however it acquired BSOD with DRIVER VERIFIER DETECTED VIOLATION.
went to safemode to disable commuter verified and then rebooted windows x, it came upwards
uploaded minidumps created during these tests, could you please check and advise? thanks
I accept non done MemTest86 yet as I need to create ISO and kicking it. If you however recommend MemTest86, I would do it.
Was this respond helpful?
Hi nhsk4u
Those minidump files indicate a driver named VBoxNetLwf.sys which is part of VirtuualBox as the cause of the organization crashes.
Try re-installing that software to se if that resolves the crashes.
___________________________________________________________________ Ability to the Developer! MSI GV72 - 17.3", i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD
Was this reply helpful?
Hi DaveM121,
I have uninstalled virtual box and enabled driver verifier again.
I accept been able to reproduce issue and it is vmx86.sys driver which is causing the outcome.
below info from problems analysis
Please annotation that I have before tried different versions of workstation and result is same. Could you please suggest if it is due to any security setting that is suspecting this driver equally an consequence?
******************************************************************************* * * * Bugcheck Assay * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the commuter was specified in the registry equally being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the organisation, BugChecks 0xC4, 0xC1 and 0xA will be amongst the most commonly seen crashes. Arguments: Arg1: 0000000000002002, Code Integrity Issue: The caller specified an executable MDL mapping. (Expected: MdlMappingNoExecute) Arg2: fffff801813a4c21, The accost in the driver's lawmaking where the error was detected. Arg3: 0000000000000010, Page Priority (MM_PAGE_PRIORITY logically OR'd with MdlMapping*). Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: ane Key : Assay.CPU.mSec Value: 2624 Primal : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 30409 Key : Analysis.Init.CPU.mSec Value: 593 Key : Analysis.Init.Elapsed.mSec Value: 5665 Key : Analysis.Memory.CommitPeak.Mb Value: 75 Key : WER.Bone.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: ten.0.19041.1 FILE_IN_CAB: 120221-18265-01.dmp BUGCHECK_CODE: c4 BUGCHECK_P1: 2002 BUGCHECK_P2: fffff801813a4c21 BUGCHECK_P3: x BUGCHECK_P4: 0 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: vmware-vmx.exe STACK_TEXT: ffffdc80`73ccf3f8 fffff801`735cde24 : 00000000`000000c4 00000000`00002002 fffff801`813a4c21 00000000`00000010 : nt!KeBugCheckEx ffffdc80`73ccf400 fffff801`7319ca25 : fffff801`73812c8c 00000000`00002002 fffff801`813a4c21 00000000`00000010 : nt!VerifierBugCheckIfAppropriate+0xe0 ffffdc80`73ccf440 fffff801`735c4c74 : 00000000`00000010 00000000`00000010 fffff801`73812c8c 00000000`00000000 : nt!VfReportIssueWithOptions+0x101 ffffdc80`73ccf490 fffff801`735e3c13 : ffffcc83`2f328fc0 000002c7`81da0000 ffffcc83`2f328fc0 00000000`00000002 : nt!VfCheckPagePriority+0x70 ffffdc80`73ccf4d0 fffff801`813a4c21 : ffffcc83`2f328fc0 ffffcc83`2f9869b0 000002c7`81da0000 fffff801`735c4708 : nt!VerifierMmMapLockedPagesSpecifyCache+0x43 ffffdc80`73ccf520 ffffcc83`2f328fc0 : ffffcc83`2f9869b0 000002c7`81da0000 fffff801`735c4708 00000000`00000000 : vmx86+0x4c21 ffffdc80`73ccf528 ffffcc83`2f9869b0 : 000002c7`81da0000 fffff801`735c4708 00000000`00000000 ffffcc83`00000010 : 0xffffcc83`2f328fc0 ffffdc80`73ccf530 000002c7`81da0000 : fffff801`735c4708 00000000`00000000 ffffcc83`00000010 ffffcc83`36109000 : 0xffffcc83`2f9869b0 ffffdc80`73ccf538 fffff801`735c4708 : 00000000`00000000 ffffcc83`00000010 ffffcc83`36109000 00000000`00000000 : 0x000002c7`81da0000 ffffdc80`73ccf540 fffff801`735d4d97 : ffff75b8`66caeee8 ffffcc83`35b310d8 fffff801`73275a08 fffff801`735d4f01 : nt!ViGenericVerifyIrpStackDownward+0x1d8 ffffdc80`73ccf640 fffff801`735cd10a : fffff801`73275a00 ffffe386`4ed5c3bf ffffcc83`30891a70 ffffcc83`1feeb7b8 : nt!VfMajorVerifyIrpStackDownward+0xb3 ffffdc80`73ccf6a0 ffffcc83`30891a70 : ffffcc83`1feeb700 ffffcc83`00000001 ffffcc83`00000001 fffff801`73275a08 : nt!IovpCallDriver1+0x4ce ffffdc80`73ccf750 ffffcc83`1feeb700 : ffffcc83`00000001 ffffcc83`00000001 fffff801`73275a08 ffffcc83`1feeb700 : 0xffffcc83`30891a70 ffffdc80`73ccf758 ffffcc83`00000001 : ffffcc83`00000001 fffff801`73275a08 ffffcc83`1feeb700 fffff801`735c1f0a : 0xffffcc83`1feeb700 ffffdc80`73ccf760 ffffcc83`00000001 : fffff801`73275a08 ffffcc83`1feeb700 fffff801`735c1f0a ffffcc83`2f312ea0 : 0xffffcc83`00000001 ffffdc80`73ccf768 fffff801`73275a08 : ffffcc83`1feeb700 fffff801`735c1f0a ffffcc83`2f312ea0 ffffcc83`30891a70 : 0xffffcc83`00000001 ffffdc80`73ccf770 00000000`00000000 : 00000000`00000000 ffffdc80`73ccfb40 ffffcc83`2f312ea0 ffffcc83`2f312ea0 : nt!IopSynchronousServiceTail+0x1a8 SYMBOL_NAME: vmx86+4c21 MODULE_NAME: vmx86 IMAGE_NAME: vmx86.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 4c21 FAILURE_BUCKET_ID: 0xc4_2002_VRF_vmx86!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {bed64b6d-6335-bfbd-48c9-0ea61b8df6d7} Followup: MachineOwner --------- Was this reply helpful?
Hi nhsk4u
Please completely disable Driver Verifier and await to run across if your arrangement is stable after removing VirtualBox
___________________________________________________________________ Power to the Developer! MSI GV72 - 17.3", i7-8750H (Hex Cadre), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD
Was this reply helpful?
Hi DaveM121,
My issue is windows 10 crashing when i ability on VM on VMware workstation.
While we troubleshooting this effect, i have installed Virtualbox to create VM to create VMs as an alternate solution
Yet when we enabled driver verifier for 1st time, virtualbox commuter acquired BSOD during reboot which was initiated to get verifier settings into effect. As you informed, this crash was caused due to virtualbox commuter hence i uninstalled information technology.
I have again enabled commuter verifier for 2d time and able to reproduce crash during powering ON vm on VMware workstation. Information technology is acquired by vmx86.sys which is relevant to VMware workstation hence I would need your expert advise on this.
am attaching minidump caused by vmx86.sys, kindly bank check and advise.
Please annotation that I accept disabled driver verifier after collecting crash
Was this reply helpful?
Source: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-crashing-when-powering-on-vm-on-vmware/00a83e7f-bdb0-4059-82f4-a1ac6f9c339a
0 Response to "Vmworkstation Unknown Error Please Try Again"
Postar um comentário