[SOLVED] [Win7SP1 x64] Hundreds of corruptions

Brian I removed two modules (ensuring to keep two that were in matching/paired slots). I didnt notice any change in any behaviour. What were you expecting to see?
 
OK so you still have the crashing from explorer, etc? If that's the case then I guess put back the memory modules and do the following.


Test RAM With Memtest86+

Please ensure you allow 8 passes of the program!

Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting
 
Hi
Tonight I managed to run the memtest routine. It took about an hour to do all 8 passes and had no errors.
Robyn
 
I just ran SFCFix again and received this output:

AutoAnalysis::
WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.0.0_none_c5e12c26ff7bf1e3.
CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.0.0_none_c5e12c26ff7bf1e3) on component watchlist.

WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-windowscodec_31bf3856ad364e35_0.0.0.0_none_ba5bad27e9485a31.
CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-windowscodec_31bf3856ad364e35_0.0.0.0_none_ba5bad27e9485a31) on component watchlist.

WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.0.0_none_7e33f54feaffc8dd.
CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.0.0_none_7e33f54feaffc8dd) on component watchlist.

WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_0.0.0.0_none_2edaee19aa21269d.
CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_0.0.0.0_none_2edaee19aa21269d) on component watchlist.

I am not enough of an expert on the windows registry to understand what this is telling me. I have opened RegEdit and browsed to that location, which is there.
 
dammit, just seen it. I will do that this evening. It is an OCZ SSD, I did try find specific tools to run diagnostics on it. But I have SeaTools somewhere, will give that a go. Thanks
 
Hi Brian
I tried running the latest SeaTools that I burnt to CD, but it just got stuck at 10% of the short test for what seemed like an length of time that meant something wasnt right. So today I took it out, plugged it into a different machine (via SATA not USB) and tested it with a few utils (SeaTools for Windows, SSDUtility (OCZ monitoring util) and SSLife). I also did another thorough Chkdsk. Everything came back saying that there were no issues and that the drive was expected to run till about 2026 (at the rate I have used it thus far). So I dont think there are any errors with the drive.

I still cant figure out how to get the files that are being reported as missing/corrupt. I haev worked out which KB release they are from, but I cant install it (see above posts). Perhaps you could detail how I can extract the required files from a KB package and then I could manually copy them over. Otherwise, is there a way to force the system to reinstall the KB package, hopefully thereby getting good working copies of the files installed?
Thanks
Robyn
 
If you want to extract the files from the KB that you downloaded you can do something like the following.

c:
cd c:\MSUFolder
expand -F:* Saved_MSU_File_Name.msu c:\MSUFolder
expand -F:* Saved_MSU_File_Name.cab c:\MSUFolder
 
Hi
Sorry for the gap in communication, I have been away from home in the wilderness without signal.
I probably did not ask my question clearly enough. I am able to opeb the MSU and CAB files (using 7zip) but all that gets me is a bunch of CAT and MUM files. I am not sure how I am meant to get those files extracted to access the DLLs that are contained within the update (or perhaps my understanding of win updates is lacking, and the CAT and MUM files contain code on how to modify an existing DLL?? However, that doesn't seem right to me, and that they would more likely distribute a newer version of the DLL)

My questions from above still stand please:
* I have worked out which KB release they are from, but I cant install it (as if I try remove it it fails, and if I try reinstall it says it is already installed). Is there a way to force the system to reinstall the KB package, hopefully thereby getting good working copies of the files installed?
* Is there any info on what SFCFix is telling me when it mentions issues with the registry (see my post above on the 19th)

Thanks
Robyn
 
* I have worked out which KB release they are from, but I cant install it (as if I try remove it it fails, and if I try reinstall it says it is already installed). Is there a way to force the system to reinstall the KB package, hopefully thereby getting good working copies of the files installed?
Not really, no. I've done it a couple times but it's very tricky and risky if you don't know what you are doing.

* Is there any info on what SFCFix is telling me when it mentions issues with the registry (see my post above on the 19th)
There is no public documented information. There is an acadamy here where we teach interested users how to be a Windows Update specialists. There's really a lot to it. Not something that can be taught over a few posts.
 
Brian
OK. So is there nothing else I can do to try recover the system? Should I just give up and do the usual reinstall of windows?
Thanks
Robyn
 
I do think that is the best course of action. Since you have the issues in Safe Mode, I believe the corruption is too much to fix or a the very least not worth it if you have the option to re-install.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top