DISM Error 582

Ahounari

Member
Joined
Sep 15, 2016
Posts
18
Hello all,
Lately my desktop has been bluescreening about once a day, and, having thoroughly checked the hardware, run memtest, etc. I came to conclude that the issue was in software. I started by running
sfc /scannow
which got me this error
Windows Resource Protection could not perform the requested operation.
I then ran
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
any DISM command other than /CheckHealth returns
error 582 "An illegal character was encountered."
SFCFix returned no helpful information, just 'all clear' logfile with no actual information in it.
Any help would be appreciated.

P.S. If you would like, i can run SFCFix again, and upload the log. I deleted the last one as it had literally no information in it, just a message with SFCFix's version number and an 'all clear'.
 
Hi Ahounari,
This error indicates an unexpected character in one of the registry keys, values, or data.

Please manually upload the components hive by following these instructions:

Upload Components Hive
  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current COMPONENTS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.
 
Code:
Key:   HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\3122502efcbcfead32bf7efb66eef374e79b465941d8e8ca3bdec3e81de2eb77
Value: c!c7d6c4<99d2..8e7937bb866_b03f5f7f11d50a3a_4.0.9600.211[B][Color=#FF0000]*ø*[/Color][/B]0_775552ae4616d335
Data:  

Key:   HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-themecpl.resources_31bf3856ad364e35_6.3.9600.16384_en-us_236592b6694f4c89
Value: identity
Data:  Microsoft-Windows-themecpl.Resources, Culture=en-US, Version=6.3.9600.16384, PublicKmyToken=[B][Color=#FF0000]*�*[/Color][/B]1bf3856id364e35, ProcessorArchitecture=x86, ver{ionScope=NonSxS

Key:   HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6
Value: f256!mdmtdkj6.inf
Data:  2[B][Color=#FF0000]*

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


View attachment SFCFix.zip
 
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-09-21 02:57:46.319
Microsoft Windows 8.1 Update 3 - amd64

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\3122502efcbcfead32bf7efb66eef374e79b465941d8e8ca3bdec3e81de2eb77.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-themecpl.resources_31bf3856ad364e35_6.3.9600.16384_en-us_236592b6694f4c89.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6\v!6.3.9600.16384.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\3122502efcbcfead32bf7efb66eef374e79b465941d8e8ca3bdec3e81de2eb77.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-themecpl.resources_31bf3856ad364e35_6.3.9600.16384_en-us_236592b6694f4c89.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6\v!6.3.9600.16384.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.17709 (winblue_r9.150219-1500)\ComponentFamilies\amd64_mdmtdkj6.inf_31bf3856ad364e35_none_9f0880f97c66f0f6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\3122502efcbcfead32bf7efb66eef374e79b465941d8e8ca3bdec3e81de2eb77.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-themecpl.resources_31bf3856ad364e35_6.3.9600.16384_en-us_236592b6694f4c89.
RegistryScript:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2016-09-21 02:57:47.567
Script hash: LZ76QcW92ZtkIiy0WKzjvi2SF7oqXA1dQWWQqfjNOW4=
----------------------EOF-----------------------
 
Code:
2016-09-21 13:50:22, Error                 CSI    00000d20 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE #1370400170# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:312{156}]"Microsoft-Windows-themecpl.Resources, Culture=en-US, Version=6.3.9600.16384, PublicKeyToken=31bf3856id364e35, ProcessorArchitecture=x86, versionScope=NonSxS")
[gle=0xd0150016]
2016-09-21 13:50:22, Error                 CSI    00000d21@2016/9/21:18:50:22.543 (F) base\wcp\componentstore\versionedindex.cpp(1021): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::PopulateComponentFamiliesKey expression: (null)
[gle=0x80004005]

Looks like a new bitflip, it isn't in the hive that was last uploaded.

How long was memtest run? Are you overclocking? How old is this computer?
 
I ran memtest for 12 hours, no overclock, and it's custom built, with some parts upgraded and others not, but the last fresh install of windows was around February this year.
December last year I upgraded the motherboard, graphics card, and system drive. Did burn-in testing on all of it, all passed a 24-hour burn-in.
 
Has the machine had this BSOD problem since the new motherboard or has it developed fairly recently?

If recent, check the board for bulging capacitors. If it was new in December I doubt that would be the problem, but it is a good place to start.
Verify that your CPU fan is clear and check your CPU temperatures to rule out overheating.
Try running Prime95 in stress testing mode overnight, the default options (blend) should be fine. GIMPS - Free Prime95 software downloads - PrimeNet
If Prime95 reports an error or the machine bluescreens, that confirms a hardware problem of some variety.
Try repeating the test with only one stick of RAM (or spare RAM if you have any).

Let me know what you find.
 
I actually ran Memtest86+ overnight last night, and it came up with 4 errors.
I checked the reviews for the memory I'm using yesterday and found several cases of the memory developing errors over time, particularly if the BIOS hasn't detected it properly and tries to run it at a lower clock speed, which mine did.
I will be RMAing the ram asap

As a side note, oddly, the BSOD's only seem to happen at idle/low activity, like if i don't have anything heavy running and leave the room.
 
Very good, glad you found the source of the problem :)

Do you have spare RAM in the mean time?
 
I have a 4GB set that passes memtest with flying colors, so i can get by, but it will definitely be painful until the new memory gets here.
I'm actually considering ordering a 16GB kit of a different brand to use in the interim, or perhaps indefinitely, as both this set, and the other have a lifetime warranty.
 
Excellent.

Please manually upload the components hive by following these instructions:

Upload Components Hive
  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current COMPONENTS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.
 
Please run DISM, then when it finishes zip and attach CBS.log.
I can't load the hive and would like to verify if that is really a problem or if it's just a bad download/upload.
 
Looks like there's still some fixing to do.

Please turn Automatic Windows Updates off until we get the registry issues sorted out.

Please manually upload the components hive by following these instructions:

Upload Components Hive
  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current COMPONENTS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.
 

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

Back
Top