RELATED: How to Scan for (and Fix) Corrupt System Files in Windows Run the SFC Command to Repair System Files On Windows 7 and earlier, Microsoft offers a downloadable “System Update Readiness Tool” instead. If a file has been modified, it will automatically replace that file with the correct version. If the SFC command doesn’t work, you can also try the Deployment Image Servicing and Management (DISM) command on Windows 8, 10, or 11 to repair the underlying Windows system image. The System File Checker (SFC) tool built into Windows will scan your Windows system files for corruption or any other changes. RELATED: Everything You Need to Know About the Blue Screen of Death If Windows is experiencing blue-screen or other crashes, applications are failing, or some Windows features just aren’t working properly, there are two system tools that might be able to help. If a file has been modified, it will automatically replace that file with the correct version. The System File Checker tool built into Windows can scan your Windows system files for corruption or any other changes. If SFC fails to run properly or cannot repair the files, run 'DISM /Online /Cleanup-Image /RestoreHealth' to fix any remaining issues. In by the security system, and then only when resource limits are encountered.Open Command Prompt or PowerShell as administrator, then run 'sfc /scannow' to fix corrupted Windows System Files. It may occur due to a failure in a refresh operation, which is used only Hardware problems or filesystem corruption.

It can also indicate that the registry gotĪn I/O error while trying to read one of its files, so it can be caused by Something has gone badly wrong with the registry. Is there anything I can do? REGISTRY_ERROR (51) I am not sure how to proceed and if there is anything I can do to fix the registry problem. Once I waited for about 8 hours between booting the laptop and logging in and it worked again until I restarted and logged in more quickly. I don't recall installing anything recently and I haven't attached any new hardware.

I have copied the output from windbg below. Based on the memory dump it is some kind of registry error. It is fine if I am in safe mode, but crashes every time when I log in to normal windows mode. I have recently started getting a blue screen of death (BSOD) error very shortly after logging in to my Windows 7 laptop.

Registry_error windows 7