Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 19461

VM on Server 2019 Hyper-V rebooted twice today after stable for 2 weeks

$
0
0

Hi all,

Brand new Fujitsu RX2540M4 server with 2 Xeon Silver CPUs, 128GB DDR4 mem and 6 x 480GB SSD in RAID-6. Server 2019 Standard ROK installed, Hyper-V role enabled. There are 2 VM's running on it, both Server 2019 STD, in production since about 2 weeks. SRV1-DC is domain controller with 8GB RAM assigned, SRV2-ADMIN is domain member and hosts a SQL SRV DB and acts as a terminal server for 6 thin client users (Office 365 ProPlus apps and ERP system users), with 96GB assigned to it. NIC team 1 consists of 2 Gbit adapters, used by the Hyper-V host, NIC team 2 consists of 4 Gbit adapters and is used as a virtual switch for the VM's.

Today, SRV2-ADMIN suddenly rebooted twice, the following errors can be found in the Hyper-V events on the HV host:

'SRV2-ADMIN' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x3B, ErrorCode1: 0xC0000005, ErrorCode2: 0xFFFF864C3F0BBAA9, ErrorCode3: 0xFFFF8C0BDAE62250, ErrorCode4: 0x0.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID B6FE9B8F-9129-4B6A-81AB-79BCE490AD6C)

Error code 0x3B assuming a memory access violation

'SRV2-ADMIN' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x50, ErrorCode1: 0xFFFFFC048E600000, ErrorCode2: 0x2, ErrorCode3: 0xFFFFF8005A252377, ErrorCode4: 0x2.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID B6FE9B8F-9129-4B6A-81AB-79BCE490AD6C)

Error code 0x50 PAGE_FAULT_IN_NONPAGED_AREA

The errors make me suspect the RAM in this server, but this is a brand new machine which has 4 sticks of 32GB ECC memory. Before contacting Fujitsu I would like to be 200% sure it's a hardware and not a driver issue.

The Hyper-V host hasn't rebooted, only this one VM. Of course, it's the biggest memory user so if one of the 4 sticks of RAM is going south, chances are high that the errors occur within this VM.

I hope that someone out there recognizes this behavior and is wanting to share his/her experience here.

Thanks!

Kristof


Viewing all articles
Browse latest Browse all 19461

Trending Articles