BSOD STOP:000000xF4; SFC Scan results (iassdo.dll.mui corrupt)

Scyrge · 17 Mar 2015

Hey all, I've been randomly getting computer freezes and BSODs for the past couple weeks now, and I think I've narrowed it down to something dealing with either my hard drive or my windows install. I have a Kingston SV300 SSD with the latest firmware. For some reason my computer isn't saving minidump files so I can't look into the cause of the BSOD, so I figured I'd check hard drive diagnostics and windows diagnostics. My HD tests came back clean, but my SFC scan tells me that iassdo.dll.mui is corrupt and cannot be repaired.

Since I can't post the dump, I'll upload a picture I took of the BSOD along with the SFC results.

Golden · 18 Mar 2015

Follow this to configure minidumps:

Dump Files - Configure Windows to Create on BSOD

Then when you next get a BSOD, follow this:

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

Scyrge · 18 Mar 2015

I already have my computer set to create the small memory dump (256kb) and it never does. I'm pretty sure the problem is that the computer hangs again while on the 'initializing disk' step of the BSOD. I think I've read online that it's due to the computer not recognizing the hard drive at that point. I'll go ahead and try switching it over to kernel dump mode.

I'll post again when (if) I get another BSOD - in the meantime, any idea what I can do about that corrupt dll.miu file?

Golden · 19 Mar 2015

Test the disk....use DOS version to run LONG test:
SeaTools for DOS and Windows - How to Use

NoelDP · 23 Mar 2015

I'd need to see the full CBS logs to be certain but this...

Code:

2015-03-17 04:49:59, Info                  CSI    00000319 [SR] Repairing 1 components
2015-03-17 04:49:59, Info                  CSI    0000031a [SR] Beginning Verify and Repair transaction
2015-03-17 04:49:59, Info                  CSI    0000031c [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
2015-03-17 04:49:59, Info                  CSI    0000031e [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
2015-03-17 04:49:59, Info                  CSI    0000031f [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2015-03-17 04:49:59, Info                  CSI    00000322 [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
2015-03-17 04:49:59, Info                  CSI    00000324 [SR] Repair complete

...looks to me like the classic iasssdo/Pretty_Peacock mixup.
Unfortunately, so far as I know, no-one has managed to fix this without a repair install of the OS yet

Scyrge · 24 Mar 2015

Unfortunately I no longer have my Windows disk. If it's nothing serious (and I haven't really notice anything), then I guess I just wont worry about it.

And pertaining to my HD, I've used Kingston's SSD Toolbox to run both a Smart Short test and a Smart Extended test. If you think it's not good enough and SeaTools would be better, I've got a copy of Hiren's Boot CD I could go dig up.

I haven't had a BSOD in a while, so no update on the dump file.

Scyrge · 07 Apr 2015

Hey all, I had another string of bluescreens last night. For some reason my computer is still refusing to create dump files. I ran another long test on my SSD with seatools and all came back clean. Is it possible this could be caused by overheating?