That error message occurs regardless of CPU in use. Looking at the code, it grabs the CPU identifier string and formats that message with it. It can trigger on AMD CPUs that are definitely unaffected by Intel’s instability issues, so I wouldn’t put too much stock in it unless you are dealing with 13th- or 14th-gen Intel CPUs.
It would be interesting to know if the 11xxx and 12xxx chips are making up a similar sized portion (compared to 13/14th gens) of the reports you are seeing. That Oodle link calls out 13xxx and 14xxx chips as being the affected SKUs, rather than 11xxx and 12xxx, and Intel confirm this in the following statement: Intel® Core™ 13th and 14th Gen Instability Customer Passthrough Statements.
As a sidenote, there’s a root cause statement from Intel here: Intel Core 13th and 14th Gen Desktop Instability Root Cause Update - Intel Community.
How often, in broad strokes if you are unable to share specifics, are you seeing this issue reported? From information I’ve seen during the 13th- and 14th-generation issues, the 11th- and 12th- generation and prior, along with AMD, have considerably lower failure rates.
If you are worried about hardware stability, and if you have access to these systems, running the Intel tool (Intel® Processor Diagnostic Tool)'s stress test and running decompress tests outside of Oodle decompression may help to rule out CPU issues. If tests are failing or if decompression is erroring outside of Unreal’s codebase, then could be a hardware issue of some kind.
If these are being read from DDC, it’s possible there’s DDC corruption that may be fixed by clearing the DDC and letting it regenerate.
Best regards,
Chris