BSOD on many Windows 2016

DeeMaas

Renowned Member
Dec 10, 2012
22
0
66
Code:
# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-20-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-8
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-19-pve: 4.15.18-45
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.13.8-3-pve: 4.13.8-30
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.19-1-pve: 4.4.19-66
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-54
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-6
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
# qm config 120
agent: 1
balloon: 0
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
memory: 3072
name: nomad
net1: virtio=76:E3:CC:CC:03:04,bridge=vmbr189
numa: 0
onboot: 1
ostype: win10
protection: 1
scsihw: virtio-scsi-pci
smbios1: uuid=362b345a-0c51-4343-bb3b-43a8d04b7e0b
sockets: 1
virtio0: MSA2040-VM:vm-120-disk-1,size=35G

Windows Dump
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
        the pagefile offset. Parameter 3 contains the page CRC value.
        Parameter 4 contains the expected CRC value.
Arg2: 000000000000ba44
Arg3: 00000000903a3f09
Arg4: 000000000000ba44

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  14393.3269.amd64fre.rs1_release.190929-1234

SYSTEM_MANUFACTURER:  QEMU

SYSTEM_PRODUCT_NAME:  Standard PC (i440FX + PIIX, 1996)

SYSTEM_VERSION:  pc-i440fx-2.12

BIOS_VENDOR:  SeaBIOS

BIOS_VERSION:  rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org

BIOS_DATE:  04/01/2014

DUMP_TYPE:  2

BUGCHECK_P1: 3f

BUGCHECK_P2: ba44

BUGCHECK_P3: 903a3f09

BUGCHECK_P4: ba44

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


BUGCHECK_STR:  0x1a_3f

CPU_COUNT: 2

CPU_MHZ: 95d

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: f

CPU_MODEL: 6

CPU_STEPPING: 1

CPU_MICROCODE: f,6,1,0 (F,M,S,R)  SIG: 1'00000000 (cache) 1'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  PAGE_HASH_ERRORS_0x1a_3f

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

PAGE_HASH_ERRORS_DETECTED: 1

ANALYSIS_SESSION_HOST:  YAKUKHIN

ANALYSIS_SESSION_TIME:  11-13-2019 13:46:52.0721

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  ffffe601f608d130 -- (.trap 0xffffe601f608d130)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000068 rbx=0000000000000000 rcx=0000000000000000
rdx=000001ce23ff0000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb256d285f7d0 rsp=ffffe601f608d2c0 rbp=0000000000000001
 r8=00000000ffffffff  r9=0000000000000000 r10=000001ce23fefc00
r11=0000000000000780 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
win32kfull!vSolidFillRect1+0x170:
ffffb256`d285f7d0 4c890a          mov     qword ptr [rdx],r9 ds:000001ce`23ff0000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8014638a92e to fffff80146361d10

STACK_TEXT:
ffffe601`f608cc88 fffff801`4638a92e : 00000000`0000001a 00000000`0000003f 00000000`0000ba44 00000000`903a3f09 : nt!KeBugCheckEx
ffffe601`f608cc90 fffff801`4629a4c0 : ffffa20b`8ce6a030 ffffe601`f608d130 ffffe601`f608cdc0 ffffa20b`8ce6a010 : nt!MiValidatePagefilePageHash+0x7244a
ffffe601`f608cd60 fffff801`4629c4ec : 00000000`00000000 ffffe601`f608cee0 ffffa20b`8d868780 00000000`00000000 : nt!MiWaitForInPageComplete+0x320
ffffe601`f608ce90 fffff801`462ba34f : 00000000`c0033333 ffffa20b`8ce6a010 ffffa20b`8d868780 00000000`00000004 : nt!MiIssueHardFault+0x31c
ffffe601`f608cf30 fffff801`4636ed61 : ffffc83c`bcadfbca ffffe1f0`f87c3fc8 ffffe1f0`f87f9000 ffffe1f0`ff200400 : nt!MmAccessFault+0x128f
ffffe601`f608d130 ffffb256`d285f7d0 : 00000000`00000780 000001ce`23fb0000 00000000`00000000 000001ce`23fb0000 : nt!KiPageFault+0x321
ffffe601`f608d2c0 ffffb256`d285f513 : 00000000`00000000 ffffa20b`ffffffff 000001ce`23fb0000 000001ce`00001e00 : win32kfull!vSolidFillRect1+0x170
ffffe601`f608d310 ffffb256`d285eec8 : 00000000`00000780 ffffb233`41c21120 ffffb256`d2c20810 ffffb256`d2c207f0 : win32kfull!vDIBSolidBlt+0x1f3
ffffe601`f608d540 ffffb256`d284b1c9 : 00000000`00000000 ffffe601`f608d860 00000000`00000000 00000000`00000000 : win32kfull!EngBitBlt+0x3a8
ffffe601`f608d6a0 ffffb256`d28fb372 : 00000000`00000000 00000000`00000000 00000000`00010056 00000000`00000000 : win32kfull!GrePatBltLockedDC+0x265
ffffe601`f608d760 ffffb256`d28fb199 : ffffb233`40000700 00000000`61050518 ffffb256`00000000 00000000`00000000 : win32kfull!NtGdiPatBlt+0x1b2
ffffe601`f608d8b0 ffffb256`d28133d5 : 00000000`00000000 ffffa20b`8cef2090 00000000`00000000 00000000`00000000 : win32kfull!EraseBitmap+0x6d
ffffe601`f608d910 ffffb256`d28f04bf : 00000000`00000000 ffffb233`40047b10 ffffa20b`8cef2090 ffffe601`00000000 : win32kfull!xxxSwitchDesktop+0x281
ffffe601`f608da30 ffffb256`d28f03db : 00000000`00000006 ffffe601`f608db90 00000000`00000000 0000050a`b7da2a20 : win32kfull!RemoteDisableScreen+0xaf
ffffe601`f608da90 ffffb256`d2a1aafd : ffffa20b`8c890080 00000000`00000000 00000000`00000020 00000000`00000000 : win32kfull!xxxRemoteStopScreenUpdates+0x1b3
ffffe601`f608dc10 fffff801`46371803 : ffffa20b`8c890080 00000000`00000000 00000000`00000020 00007fff`2c923150 : win32kfull!NtUserRemoteStopScreenUpdates+0x3d
ffffe601`f608dc40 00007fff`2d4d92a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000063`a187fa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`2d4d92a4


THREAD_SHA1_HASH_MOD_FUNC:  9acfa4ae8c33cf27c7eb6368be168d8e9d98dc68

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  bca980910ee1c46217d69e11b1b066e776781b3c

THREAD_SHA1_HASH_MOD:  5d35f6861fe6a228c3d422df998a52bb4f1be8b6

SYMBOL_NAME:  PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID:  PAGE_HASH_ERRORS_0x1a_3f

PRIMARY_PROBLEM_CLASS:  PAGE_HASH_ERRORS_0x1a_3f

FAILURE_BUCKET_ID:  PAGE_HASH_ERRORS_0x1a_3f

TARGET_TIME:  2019-11-13T09:17:56.000Z

OSBUILD:  14393

OSSERVICEPACK:  3269

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 Server TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-09-30 01:46:50

BUILDDATESTAMP_STR:  190929-1234

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.3269.amd64fre.rs1_release.190929-1234

ANALYSIS_SESSION_ELAPSED_TIME:  1d8d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:page_hash_errors_0x1a_3f

FAILURE_ID_HASH:  {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

Followup:     MachineOwner
---------

 *** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!