-->

This virtual machine's guest operating system has crashed

 This virtual machine's guest operating system has crashed

This article describes how to identify the cause of the issue.

Recently, I had a couple VMs that rebooted unexpectedly and showed events on the vCenter side.

"This virtual machine's guest operating system has crashed" 

When I verified to the OS level, I found the events on the below error..

" BugCheck 0xA: Caused by vnetflt.sys attempt to acquire invalid spinlock from vnetflt's completion context"

Debug Notes:-

-----------------------------------------------------------------------------

 0: kd> ||

.  0 64-bit Kernel bitmap dump: \SecureEncryptedCustomerData\2404180060003383_Sumit\MEMORY.DMP

Windows 10 Kernel Version 14393 MP (2 procs) Free x64

Product: Server, suite: TerminalServer SingleUserTS

Edition build lab: 14393.6795.amd64fre.rs1_release.240226-1752

Kernel base = 0xfffff801`4d486000 PsLoadedModuleList = 0xfffff801`4d78bb40

System Uptime: 10 days 15:23:04.077

SystemManufacturer = VMware, Inc.

SystemProductName = VMware Virtual Platform

Processor: Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz

Bugcheck: A (350, 2, 1, FFFFF8014D501F9D)

Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

Current Update Build Revision: 14393.6796

Memory        OK     Kernel memory looks good

Process crash OK     No crashing processes found

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000000000350, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

    bit 0 : value 0 = read operation, 1 = write operation

    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff8014d501f9d, address which referenced memory

 Bugcheck Thread

Process                   Thread           CID       UserTime KernelTime ContextSwitches Wait Reason Time State

System (ffff9c07684b0040) ffff9c0778184040 4.15ec          0s      844ms           89469 Executive     0s Running on CPU 0

 Priority:

    Current Base UB FB IO Page

    12      12   0  0  2  5

 0 ffff84812871a758 fffff8014d5f5069 nt!KeBugCheckEx+0x0

1 ffff84812871a760 fffff8014d5f1c66 nt!KiBugCheckDispatch+0x69

2 ffff84812871a8a0 fffff8014d501f9d nt!KiPageFault+0x426                                    

3 ffff84812871aa30 fffff80b46907e3a nt!KxAcquireSpinLock+0xd

4 ffff84812871aa60 fffff8014d4f03a7 netbt!AcceptCompletionRoutine+0x4a

5 ffff84812871aac0 fffff80b468b1b38 nt!IopfCompleteRequest+0x197

6 ffff84812871abd0 fffff8014d4cb870 vnetflt+0x1b38

7 ffff84812871ac50 fffff8014d4c8b59 nt!IopProcessWorkItem+0xf0

8 ffff84812871acc0 fffff8014d51aa39 nt!ExpWorkerThread+0xe9

9 ffff84812871ad50 fffff8014d5eb916 nt!PspSystemThreadStartup+0x41

a ffff84812871ada0 0000000000000000 nt!KxStartSystemThread+0x16

 This thread is crashing

                    Related modules:

 start             end                 module name

fffff80b`468b0000 fffff80b`468c4000   vnetflt    (no symbols)          

    Loaded symbol image file: vnetflt.sys

    Image path: \??\C:\WINDOWS\system32\Drivers\vnetflt.sys

    Image name: vnetflt.sys

    Browse all global symbols  functions  data

    Timestamp:    

--------------------------------------------------------------------------------


Cause Identification: The driver vnetflt.sys is dated from 2014. And that caused the BSOD

This system has run into a known issue in VMware. The driver vnetflt.sys is dated from 2014


Workaround: 

You can Navigate to the Programs and Features > VMware Tools > right click Change > Next > select Modify > Next > under VMCI Driver > select NSX Network Introspection Driver > select X Entire feature will be unavailable > Next > Change > Finish


Permanent solution :

 Upgrade the VMware toos and HW version to latest version (Up to match esxi host version)



This virtual machine's guest operating system has crashed This virtual machine's guest operating system has crashed Reviewed by Virtulization on May 02, 2024 Rating: 5

No comments:

Home - PageNavi (show/hide)

hide
Powered by Blogger.