- Joined
- May 22, 2010
- Messages
- 386 (0.07/day)
Processor | R7-7700X |
---|---|
Motherboard | Gigabyte X670 Aorus Elite AX |
Cooling | Scythe Fuma 2 rev B |
Memory | no name DDR5-5200 |
Video Card(s) | Some 3080 10GB |
Storage | dual Intel DC P4610 1.6TB |
Display(s) | Gigabyte G34MQ + Dell 2708WFP |
Case | Lian-Li Lancool III black no rgb |
Power Supply | CM UCP 750W |
Software | Win 10 Pro x64 |
The server does not really need to be doing "anything" for memory errors to pop, it could be a single write/read to an address that's bad and it will trigger the ECC.Wait. What? Are each of those table entries an indication where data was corrupted? Holy crap!
What is your data server doing that it is encountering that many memory errors?
You could be "idling" in desktop and the errors will trigger all the same, it all depends on what address is being used(maybe it's at the beginning of the array, maybe it's at the end and you don't "see" it until the ram gets full)
those table entries are indeed data corruption events SOLVED by the ECC(so they're transparent to the OS)