Memory protection faults

[teb]

I have been getting a lot of memory protection faults in the last couple weeks.  This is on an official OpnSense DEC2750.  I am thinking the RAM has gone south, so I was going to order replacement.  It looks like it is DDR4, but in what configuration?  2x4GB? 

I got this a while ago, so I can't imagine there is a warranty on it that is still valid.

Is there something else I should look at? 

Thanks,
Travis

system_20251213.log:<13>1 2025-12-13T22:39:54-05:00 mira.domain.org kernel - - [meta sequenceId="228"] <118>[4] savecore 245 - - reboot after panic: general protection fault
system_20251214.log:<13>1 2025-12-14T02:41:49-05:00 mira.domain.org kernel - - [meta sequenceId="190"] <118>[4] savecore 230 - - reboot after panic: general protection fault
system_20251214.log:<13>1 2025-12-14T15:27:22-05:00 mira.domain.org kernel - - [meta sequenceId="190"] <118>[4] savecore 237 - - reboot after panic: general protection fault
system_20251214.log:<13>1 2025-12-14T18:40:23-05:00 mira.domain.org kernel - - [meta sequenceId="189"] <118>[4] savecore 245 - - reboot after panic: page fault
system_20251214.log:<13>1 2025-12-14T22:32:22-05:00 mira.domain.org kernel - - [meta sequenceId="189"] <118>[4] savecore 230 - - reboot after panic: general protection fault
system_20251214.log:<13>1 2025-12-14T23:29:41-05:00 mira.domain.org kernel - - [meta sequenceId="19"] [3391] panic: general protection fault
system_20251214.log:<13>1 2025-12-14T23:29:41-05:00 mira.domain.org kernel - - [meta sequenceId="24"] [3391] vpanic() at vpanic+0x161/frame 0xfffffe00cdb97ae0
system_20251214.log:<13>1 2025-12-14T23:29:41-05:00 mira.domain.org kernel - - [meta sequenceId="25"] [3391] panic() at panic+0x43/frame 0xfffffe00cdb97b40
system_20251214.log:<13>1 2025-12-14T23:29:41-05:00 mira.domain.org kernel - - [meta sequenceId="36"] [3391] KDB: enter: panic
system_20251214.log:<13>1 2025-12-14T23:29:41-05:00 mira.domain.org kernel - - [meta sequenceId="224"] <118>[4] savecore 225 - - reboot after panic: general protection fault
system_20251215.log:<13>1 2025-12-15T01:00:54-05:00 mira.domain.org kernel - - [meta sequenceId="26"] [5421] panic: general protection fault
system_20251215.log:<13>1 2025-12-15T01:00:54-05:00 mira.domain.org kernel - - [meta sequenceId="31"] [5421] vpanic() at vpanic+0x161/frame 0xfffffe00cbdeeaa0
system_20251215.log:<13>1 2025-12-15T01:00:54-05:00 mira.domain.org kernel - - [meta sequenceId="32"] [5421] panic() at panic+0x43/frame 0xfffffe00cbdeeb00
system_20251215.log:<13>1 2025-12-15T01:00:54-05:00 mira.domain.org kernel - - [meta sequenceId="46"] [5421] KDB: enter: panic
system_20251215.log:<13>1 2025-12-15T01:00:54-05:00 mira.domain.org kernel - - [meta sequenceId="235"] <118>[4] savecore 225 - - reboot after panic: general protection fault
system_20251215.log:<13>1 2025-12-15T01:42:09-05:00 mira.domain.org kernel - - [meta sequenceId="190"] <118>[4] savecore 225 - - reboot after panic: general protection fault
system_20251215.log:<13>1 2025-12-15T08:09:38-05:00 mira.domain.org kernel - - [meta sequenceId="19"] [23193] panic: general protection fault
system_20251215.log:<13>1 2025-12-15T08:09:38-05:00 mira.domain.org kernel - - [meta sequenceId="24"] [23193] vpanic() at vpanic+0x161/frame 0xfffffe00ce2e6b70
system_20251215.log:<13>1 2025-12-15T08:09:38-05:00 mira.domain.org kernel - - [meta sequenceId="25"] [23193] panic() at panic+0x43/frame 0xfffffe00ce2e6bd0
system_20251215.log:<13>1 2025-12-15T08:09:38-05:00 mira.domain.org kernel - - [meta sequenceId="36"] [23193] KDB: enter: panic
system_20251215.log:<13>1 2025-12-15T08:09:38-05:00 mira.domain.org kernel - - [meta sequenceId="224"] <118>[4] savecore 230 - - reboot after panic: general protection fault
system_20251215.log:<13>1 2025-12-15T12:27:42-05:00 mira.domain.org kernel - - [meta sequenceId="189"] <118>[4] savecore 230 - - reboot after panic: general protection fault
system_20251215.log:<13>1 2025-12-15T14:43:39-05:00 mira.domain.org kernel - - [meta sequenceId="190"] <118>[4] savecore 227 - - reboot after panic: general protection fault
system_20251215.log:<13>1 2025-12-15T19:42:24-05:00 mira.domain.org kernel - - [meta sequenceId="19"] [17876] panic: general protection fault
system_20251215.log:<13>1 2025-12-15T19:42:24-05:00 mira.domain.org kernel - - [meta sequenceId="24"] [17876] vpanic() at vpanic+0x161/frame 0xfffffe00ca10f420
system_20251215.log:<13>1 2025-12-15T19:42:24-05:00 mira.domain.org kernel - - [meta sequenceId="25"] [17876] panic() at panic+0x43/frame 0xfffffe00ca10f480
system_20251215.log:<13>1 2025-12-15T19:42:24-05:00 mira.domain.org kernel - - [meta sequenceId="43"] [17876] KDB: enter: panic
system_20251215.log:<13>1 2025-12-15T19:42:24-05:00 mira.domain.org kernel - - [meta sequenceId="231"] <118>[4] savecore 243 - - reboot after panic: general protection fault

[patient0]

This is on an official OpnSense DEC2750.  I am thinking the RAM has gone south, so I was going to order replacement.  It looks like it is DDR4, but in what configuration?  2x4GB? 
<snip>
Is there something else I should look at? 

I would run a memtest86+ first.

But if it is memory, is 1x8GB and is very low profile. In my DEC740 was a 4GB Transcend TS512MLH64V6HL (see photo attached, the 'L' is really important) and I replaced it with an 8GB Kingston KVR26N19S8L/8. I guess the 8GB model could use Transcend TS1GLH64V6BL, which is just the 8GB model of the one in mine.

You can use 'dmidecode' to check what RAM you got and there are plenty of threads on this forum about that topic, e.g. https://forum.opnsense.org/index.php?topic=32615.msg157764#msg157764

[Jose]

+1 for run memtest86+ first.

That particular UDIMM module from @patient0 is a Low-profile one with Samsung(SEC) chips, virtually any Low-profile DDR4-2666(PC4-21300) or faster should work with most hardware, the memory speed/latency is adjusted by the BIOS based on the SPD.

If the system is configured with single module, any decent brand should work, but if it is configured in dual-channel 2x4G, then they should be analyzed individually to check what module is failing(if that's the case) then replace the failed module with the same brand/model, or a brand-new matched kit.

[patient0]

but if it is configured in dual-channel 2x4G

The DEC700 series got only one RAM slot, https://shop.opnsense.com/dec700-series-opnsense-desktop-security-appliance/