AER: Corrected error received

[Nam Trần]

My friend currently has a Windows Server 2012 r2 (VM1) and a Windows Multipoint Server 2012 (VM2) run on a Dell Vostro 3670 PC. VM1 acts like a DBMS Server and VM1 acts like a client pool. One problem is that VM1 usually crashed with the same error message time after time:

Your PC ran into a problem

This problem caused your PC to restart. You can send info to Microsoft about what went wrong to help us improve Windows.

Files that will be sent to Microsoft

C:\Windows\Minidump\091820-3125-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-223781-0.sysdata.xml
C:\Windows\MEMORY.DMP

Even without any VM running, "AER: Corrected error received" constantly happens. Is there any thing I can do to fix the problem?

Thanks.

Hardware details are:

1. Dell Vostro 3670 - Firmware date: 02/21/2020
2. WD SN750 NVMe 250GB
3. TOSHIBA DT01ACA100
4. 32GB (2 x 16GB 2666GHz)

PVEVersion:

proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.4.60-1-pve: 5.4.60-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-12
pve-cluster: 6.1-8
pve-container: 3.2-1
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-2
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2

System log:

Sep 18 18:33:07 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:33:07 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:33:07 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:33:07 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:33:15 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:33:15 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:33:15 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:33:15 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:33:31 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:33:31 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:33:31 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:33:31 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:33:39 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:33:39 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:33:39 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:33:39 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:33:51 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:33:51 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:33:51 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:33:51 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:33:52 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:33:52 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:33:52 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:33:52 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:34:00 pve01 systemd[1]: Starting Proxmox VE replication runner...
Sep 18 18:34:01 pve01 systemd[1]: pvesr.service: Succeeded.
Sep 18 18:34:01 pve01 systemd[1]: Started Proxmox VE replication runner.
Sep 18 18:34:17 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:34:17 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:34:17 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:34:17 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:34:28 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:34:28 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:34:28 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:34:28 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:34:53 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:34:53 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:34:53 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:34:53 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr                 
Sep 18 18:34:57 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
Sep 18 18:34:57 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 18 18:34:57 pve01 kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
Sep 18 18:34:57 pve01 kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr

 

[Alwin]

Sep 18 18:33:07 pve01 kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0 Sep 18 18:33:07 pve01 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Sep 18 18:33:07 pve01 kernel: nvme 0000:01:00.0: AER: device [15b7:5006] error status/mask=00000001/0000e000 Sep 18 18:33:07 pve01 kernel: nvme 0000:01:00.0: AER: [ 0] RxErr

Could be that the nvme is faulty, the power saving doesn't work properly (grub cmd: pcie_aspm=off) or it could be more related to the older bug report.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173

 

[Nam Trần]

Could be that the nvme is faulty, the power saving doesn't work properly (grub cmd: pcie_aspm=off) or it could be more related to the older bug report.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173

Setting pcie_aspm=off seems to work for me. As a result of googling around the problem, a BIOS update can solve it. I am not sure how to update Dell Vostro BIOS in Proxmox in specific or Linux in general.

 

[Alwin]

I am not sure how to update Dell Vostro BIOS in Proxmox in specific or Linux in general.

Best check the vendors documentation on updating the BIOS. They usually have instructions for different ways of updating. Also a good thing to do is to install the latest microcode updates.

 

[Nam Trần]

Best check the vendors documentation on updating the BIOS. They usually have instructions for different ways of updating. Also a good thing to do is to install the latest microcode updates.

I have finally found out that Microsoft Windows seems to be the only supported OS in most cases. There must be a Windows-based PC to create BIOS update media or no update at all.

Thanks.