Periodic crashes+reboot and crashes+noreboot (N5105 I226-V)

KLMR

I'm new to networking (I have another background).
I've installed pfsense 2.6 in a topton N5105 i226-V ~~(link below)~~
pfsense is installed in a proxmox (7-3-3) VM. 4 cores 8GB RAM following pfsense's guide.

I'm aware that updated drivers for those NICs won't come up to 2.7

I experience two kinds of crashes:
A. crash + reboot.
The machine suffered from this issuse aprox 24-36 hours. I have to investigate this further. The workaround consist on reseting the wan connection every 24h.
B. crash + stop the VM and restart it manually.
Happens once a week. The machine ramps cpu usage up to 99% and don't reboot by itself. I have to manually stop it in proxmox.

I've read several topics about the issue. And the manual.

Failing power supply (might be?)
Flaky electricity in general (behind pure sine UPS)
Overheating CPU (active cooling + monitored)
Overheating or faulty RAM (+48h of memtest twice, it could be thougth)
Faulty hard drive/SSD/other storage (changed twice)
Faulty drive cables (M2)
and many others… ( <-- thats the problem!)

I'm aware it could be a problem associated to having no monitor connected. So I tried with a hdmi dummy plug as well.

for A cases, short log reports:

Panic String: page fault

After memory replaced and retested (total 4 modules tested in 2 pairs of 8+8 and 4 single module configs).

for B cases, when it completely hangs:

Panic String: %s

and the extende log reports

fatal trap 30

My questions are:

Is anyone else experiencing such issues with these units (topton N5105 and I226-v)?
In your experience, logs appart, what is your diagnosis procedure for such problems?
I usually replace 1 component at a time (is rare to have 2 failing components) but no replacement have had success. It might be:
2.1. the main unit.
2.2. software incompatibility.

renegade

@klmr Following forum thread should help: https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/page-30#post-543852

In short: Try installing the latest microcode as descripbed in that long thread und the crashes should be solved.

stephenw10

Yup that^.

There is a known issue with Proxmox on Jasper Lake hardware.

KLMR

@renegade
thank you very much, I'll give it a try ASAP.

KLMR

As follow up,
the changes proposed in the topic about proxmox seems to work. The firewall has been up for 60 days without an issue.

Tyvm!