mingl0280's Posts

This happens after a long run of a vm. Crash report: Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (20 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff807`45a00000 PsLoadedModuleList = 0xfffff807`4662a2d0 Debug session time: Wed Feb 16 23:26:31.486 2022 (UTC - 7:00) System Uptime: 6 days 14:18:03.070 Loading Kernel Symbols ..........................................Page 203880cc6 too large to be in the dump file. Page 2024930c7 too large to be in the dump file. ..................... ................................................................ ................................................................ ................................................................ ... Loading User Symbols PEB is paged out (Peb.Ldr = 0000008f`8ac7c018). Type ".hh dbgerr001" for details Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 80, {4f4454, 0, 0, 0} *** ERROR: Module load completed but symbols could not be loaded for vmx86.sys Probably caused by : PSHED.dll ( PSHED!PshedBugCheckSystem+10 ) Followup: MachineOwner --------- 15: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NMI_HARDWARE_FAILURE (80) This is typically due to a hardware malfunction. The hardware supplier should be called. Arguments: Arg1: 00000000004f4454 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 19041.1.amd64fre.vb_release.191206-1406 SYSTEM_MANUFACTURER: System manufacturer SYSTEM_PRODUCT_NAME: System Product Name SYSTEM_SKU: ASUS_MB_KBLX SYSTEM_VERSION: System Version BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 3403 BIOS_DATE: 03/19/2021 BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC. BASEBOARD_PRODUCT: PRIME X299-A BASEBOARD_VERSION: Rev 1.xx DUMP_TYPE: 1 BUGCHECK_P1: 4f4454 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 CPU_COUNT: 14 CPU_MHZ: cf0 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 55 CPU_STEPPING: 4 CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 2006A08'00000000 (cache) 2006A08'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x80 PROCESS_NAME: vmware-vmx.exe CURRENT_IRQL: f ANALYSIS_SESSION_HOST: PC-MING ANALYSIS_SESSION_TIME: 02-16-2022 23:39:22.0046 ANALYSIS_VERSION: 10.0.17763.132 amd64fre LAST_CONTROL_TRANSFER: from fffff80745eb41da to fffff80745df73b0 STACK_TEXT: ffff9b00`06d86b38 fffff807`45eb41da : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffff9b00`06d86b40 fffff807`42bf15b0 : 00000000`00000000 ffffd70a`de027848 fffff807`46650860 ffffd70a`de027848 : nt!HalBugCheckSystem+0x7a ffff9b00`06d86b80 fffff807`45fb616e : 00000000`00000000 ffff9b00`06d86c29 ffffd70a`de027848 fffff807`46650860 : PSHED!PshedBugCheckSystem+0x10 ffff9b00`06d86bb0 fffff807`45eb8892 : 00000000`0000003c 00000000`0000003c fffff807`46650860 00000000`0000005c : nt!WheaReportHwError+0x46e ffff9b00`06d86c90 fffff807`45f0d8c2 : 00000000`00000001 ffff9b00`06d86d10 00000000`00000000 fffff807`45f20170 : nt!HalHandleNMI+0x142 ffff9b00`06d86cc0 fffff807`45e02a82 : ffff9b00`06d1afb0 ffff9b00`06d86ed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132 ffff9b00`06d86d10 fffff807`45e02852 : ffff9b00`06d1afb0 00000000`00000000 00000000`00004c20 00000000`00000020 : nt!KxNmiInterrupt+0x82 ffff9b00`06d86e50 fffff807`605a200a : fffff807`605a93c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212 fffffc0d`6b2fed48 fffff807`605a93c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmx86+0x200a fffffc0d`6b2fed50 fffff807`605ac055 : 000009f6`000009f6 00000000`00006001 fffffc0d`6b2ff201 ffffd70b`016f66a0 : vmx86+0x93c4 fffffc0d`6b2fee90 fffff807`605a2f7e : 00000000`00020000 00000283`b0a04414 fffffc0d`6b2ff218 00000000`00000000 : vmx86+0xc055 fffffc0d`6b2fef60 fffff807`605a3992 : 00000000`00000000 ffffaf8c`e09c9680 00000000`00000000 fffff807`45c0afca : vmx86+0x2f7e fffffc0d`6b2ff140 fffff807`46075558 : 00000000`00000408 00000000`00000000 00000000`00000000 ffffd70a`f5b714f0 : vmx86+0x3992 fffffc0d`6b2ff1a0 fffff807`46074e16 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x728 fffffc0d`6b2ff2e0 fffff807`45e08db5 : 00000000`00000000 00000000`00000000 00000000`0000043c fffff807`460dbcb0 : nt!NtDeviceIoControlFile+0x56 fffffc0d`6b2ff350 00007ffd`eb72ce54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 0000008f`8c5ff638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`eb72ce54 THREAD_SHA1_HASH_MOD_FUNC: 8806dc88140c2524eef176ee246ccad9f8c38818 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 851495a8441fd2ed118d7f999b7057ecc8ace0ff THREAD_SHA1_HASH_MOD: 7a50970c0a4ce5e07eb2e6ed336e7f5dcc45416d FOLLOWUP_IP: PSHED!PshedBugCheckSystem+10 fffff807`42bf15b0 4883c428 add rsp,28h FAULT_INSTR_CODE: 28c48348 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: PSHED!PshedBugCheckSystem+10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: PSHED IMAGE_NAME: PSHED.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4c55dc99 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 10 FAILURE_BUCKET_ID: 0x80_PSHED!PshedBugCheckSystem BUCKET_ID: 0x80_PSHED!PshedBugCheckSystem PRIMARY_PROBLEM_CLASS: 0x80_PSHED!PshedBugCheckSystem TARGET_TIME: 2022-02-17T06:26:31.000Z OSBUILD: 19041 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2026-07-16 03:36:24 BUILDDATESTAMP_STR: 191206-1406 BUILDLAB_STR: vb_release BUILDOSVER_STR: 10.0.19041.1.amd64fre.vb_release.191206-1406 ANALYSIS_SESSION_ELAPSED_TIME: 10cb ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x80_pshed!pshedbugchecksystem FAILURE_ID_HASH: {8a2ee997-736c-fd91-e621-4aa5f52b7420} Followup: MachineOwner ---------  

Recently have this weird crash on VMWare WS Pro 16.2.0 for one of my VM. It crashes when the virtual system is using a lot of CPU. Crash logs are attached. Do not crash after downgraded back to 16.1.2 Do not crash before upgrading the VM compatibility to 16.2.0.  

Hi, I recently want to convert a very large VHDX file from HyperV to VMWare's vmdk, but the size for the vhdx file is 8TB and cannot be converted via Starwind V2V. Is there any other way to convert this thing to a vmdk? Thanks.