This code is Windows saying a file failed its integrity check, so the loader refused to trust it. Microsoft's name for it is STATUS_INVALID_IMAGE_HASH. It shows up in two places, in a browser as an "Aw, Snap!" page when another program injects an unsigned DLL into a tab, and at startup or driver load when a driver or system file is unsigned, damaged, or tampered with.
sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.If the browser error returns after you updated everything, try the browser with all extensions disabled and any third-party security software temporarily uninstalled, then re-enable them one at a time to find the injector. If a driver still fails its signature check after a fresh download from the maker, check whether the system clock is wrong, since a clock set far in the past or future can make a valid signature look expired.
Is 0xc0000428 a virus? Not by itself. It means a file failed a signature check, which can happen to a legitimate file that was damaged, badly updated, or injected by another program. But because malware can tamper with files, a full scan is a sensible step, especially when the error names a system file.
Why does Chrome show STATUS_INVALID_IMAGE_HASH? Chrome and Edge run web pages in sandboxed processes that refuse DLLs not signed by Microsoft. When antivirus, data loss prevention, overlay, or accessibility software injects its own DLL into a page process, Windows rejects it and every tab shows Aw, Snap with this code. Updating or removing the injecting software is the fix.
Should I disable driver signature enforcement to fix 0xc0000428? No, not as a fix. Disabling signature enforcement lets unsigned and possibly tampered drivers load, which removes the protection that caught the problem. Get a properly signed driver from the hardware maker instead, and only use test signing if you are a developer testing your own driver.