Now MCE can count the number of found mCodes. But I understand that he only counts those mCodes that he knows? If so, can you add another option? First, we look for and calculate the mCodes that we know. Then we search and calculate everything only by the general search string Then we look for and count everything, only by 'pat_acpu’ Compare the results of both searches. If the results match, then nothing new. If ‘pat_acpu’ counter is greater than the known counter, then something has been found and can be analyzed.
If believe AMD’s statements, then until the end there will be new 4xxx models, and next year 5xxx models for laptops. And it is difficult to say what the CPUID will be.
Edit/Added:
No calc/count. Example
1 2 3 4
while (found (pat_acpu)) if (check (cpu_id) == false) printf ("Found Unknown %X %X\n", CPUID, Offset)
MCE counts all the microcode patterns detected by pat_icpu + pat_acpu + pat_vcpu + pat_fcpu. There is one pattern for each vendor which should detect all their microcodes and prevent false positives as much as possible. In this case, there is no need to have an extra less strict AMD pattern because it would give false positives and whatever MC count comes from there will be inaccurate.
Unless absolutely necessary (i.e. vendor changed Header structure completely, never happened so far) there should only be 1 pattern per vendor because regex searches are generally very complicated/slow. Optimizations can be made (and are made in MCE) to make them faster but the rule of thumb is to keep them as infrequent as possible.
Regarding CPUID, MCE does not rely on that for the regex patterns. Since AMD, in their infinite wisdom, do not have a microcode size in the header (even though half of it is "reserved"), MCE needs to keep a hardcoded list of generations and their static (unique to AMD) microcode sizes. This is done via the CPUID but only after the microcode has been detected/allowed by the regex pattern:
If a new microcode CPUID is found and MCE does not know its static size yet, an error is shown but the microcode is shown/accepted:
The issue with Zen 3 was that the Loader ID value range was set to 0-4 but Zen 3 started using 5 so it needed to be increased first to detect a valid microcode before dealing with the Size (CPUID). Honestly, any vendor can change many things in the header which will break the regex searches (reserved fields, revisions etc) but for AMD, I increased Loader ID to 6 now (should cover the next generation) to be on the safe side and hopefully without extra false positives.
Just came here to post this, was trying to download MC Extractor v1.48.1 r159 and Windows Defender reported a trojan, had a small scare thinking the MC Extractor github was compromised, edge removed it as soon as it was downloaded. Did not happen with R157. Maybe a new version needs to be pushed to remediate this issue?
UPDATE: For some reason, windows is calling r157 as a PUP (Potentially Unwanted Program), still much nicer than to call it a trojan and immediately blocking it, lol
Guys, please read the README over at Github. There a specific section just for false positives. I’ll probably have to include that note at each release from now on unfortunately.
Found funny readings in a Z97 bios Lost_N_BIOS is working with- fragments of AMD mcs in NVRAM in a HSW/BDW bios (Z97)- NVRAM entries are named 'MrcS3resume’
MCE output:
Are these fake recognitions or how could that have happened?
False positives. Must be ignored. The AMD detection pattern is already as strong as it can be considering AMD’s idiocy when it comes to firmware development.
Hi, All. I can’t find any newer microcode for: # │ CPUID │ Platform ID │ Revision │ Date │ Type │ Size │ Offset │ Last 3 │ 106A4 │ 02 (1) │ A │ 2008-09-19 │ PRD │ 0x2400 │ 0x93820 │ No Anyone can help me with it?
And there’s no change, new program revision included exe, new db- revision only never did. Otherwise people might use what they like better, I don’t care.
MCE 1.71 show error dialog on Windows 7 SP1. "The program can’t start because api-ms-win-core-path-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem." MCE 1.70 works fine. similar issue on other software.
