Blue Screen of Death

[NathanPNE]

Sorry to make another new thread.

I recently did a SFC/Scannow using CMD and it came up that I had corrupt files, that it was unable to repair it and to check the CBS log which I have done.


Basically I cant make head to tail of the information I was supplied so im hoping one of you guys could help.

(Also could this be the root of my BSOD?)

POQ 120 ends.
2013-11-06 22:54:15, Info CSI 000002e6 [SR] Verify complete
2013-11-06 22:54:15, Info CSI 000002e7 [SR] Repairing 1 components
2013-11-06 22:54:15, Info CSI 000002e8 [SR] Beginning Verify and Repair transaction
2013-11-06 22:54:15, Info CSI 000002e9 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2013-11-06 22:54:15, Info CSI 000002ea [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-11-06 22:54:15, Info CSI 000002eb Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2013-11-06 22:54:15, Info CSI 000002ec [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-11-06 22:54:15, Info CSI 000002ed [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2013-11-06 22:54:15, Info CSI 000002ee Hashes for file member \??\C:\Windows\SysWOW64\en-US\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2013-11-06 22:54:15, Info CSI 000002ef Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2013-11-06 22:54:15, Info CSI 000002f0 [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
2013-11-06 22:54:15, Info CSI 000002f1 Repair results created:
POQ 121 starts:

POQ 121 ends.
2013-11-06 22:54:15, Info CSI 000002f2 [SR] Repair complete
2013-11-06 22:54:15, Info CSI 000002f3 [SR] Committing transaction
2013-11-06 22:54:15, Info CSI 000002f4 Creating NT transaction (seq 2), objectname [6]"(null)"
2013-11-06 22:54:15, Info CSI 000002f5 Created NT transaction (seq 2) result 0x00000000, handle @0x85c
2013-11-06 22:54:15, Info CSI 000002f6@2013/11/6:22:54:15.773 CSI perf trace:
CSIPERF:TXCOMMIT;5
2013-11-06 22:54:15, Info CSI 000002f7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired


Thank you all in advance!

 

[himnextdoor]

It is possible that a Windows Update caused the blue screen. Has the system been okay since?

Also, it is possible that a Windows Update replaced you iassdo.dll file and I believe that SFC examines a list of files that were installed with the disk to confirm file integrity.

Do a search for the file iassdo.dll, it's in: C:\Windows\WinSX\

I have this file on my machine and it is 46 KB in size and its date is 13th July 2009.

Is yours a newer one?

 

[NathanPNE]

I found the file and its dated 14th July 2009

 

[NathanPNE]

The BSOD does not occur randomly, it occurs when playing games (Well, demanding ones.)