Now I know there have been MANY threads in relation to this ridiculous error but I have gone through all of them and tried all things. At least I think I have.
I have run Windows Repair Environment.
I have repaired/reinstalled C++, framework, DirectX.
I have downloaded the correct DLL files and gone into safe mode and place them in the Wendows/System32 files manually.
Even done the ChKDsk thing and it came up clean.
I have a fresh install of Windows as I recently had my HDD fail. I'm now running on a Samsung EVO 840 512GB SSD. However I had this issue before the migration took place.
I have no idea where to go from here. I am LOST! I would greatly appreciate your help with this one.
Cheers
Windows 7 Professional 64-Bit SP1
i7 860 @ 2.8Ghz
8GB Ram DDR3
I think we need a lot more data to be able to have any hope of proper diagnosis - and I also think you may have made mistakes with your handling of the dll problems you mention.
SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type SFC /SCANNOW
and hit the Enter key
Wait for the scan to finish - make a note of any error messages - and then reboot.
Upload the whole CBS folder (C:\Windows\logs\CBS) (compressed, please!) to your OneDrive or DropBox Public folder, and post a link.
Ok. So I ran the program. Below is the txt file log.
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-22 18:02:49.360
Not using a script file.
AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-22 18:04:31.684
----------------------EOF-----------------------
Bother - I was hoping that the developers had fixed the bug that prevents proper fixing of that problem.
Let's check that the problem really is what I think it is...
I've uploaded a file - SFCFixScript.txt - to my OneDrive at Noel's OneDrive Please download and save it to the same location as SFCFix.
Open the SFCFix location in Windows Explorer - and drag the SFCFix.txt file over onto the SFCFix.exe file - this should force SFCFix to run the file It will create a new log file - please upload that.
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-22 21:48:44.086
Using .txt script file at C:\Users\Taity's\Desktop\SFCFixScript.txt [0]
FileScan::
[0: 5] C:\Windows\winsxs\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui
Expected: hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg= Found: tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=
Expected: 6.1.7600.16385 Found: Version number not available.
Successfully traced component x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7.
Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack
[1: 1] C:\Users\Taity's\AppData\Local\Microsoft\Windows Mail\Stationery\Pretty_Peacock.jpg
File is untraceable.
Found: tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=
Version number not available.
Trace not available.
[2: 2] C:\Windows\winsxs\amd64_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_448b1c3c529ce8ed\iassdo.dll.mui
Expected: OP2PFNasfNNIWM0oyuajsI6jQ9pkJ7CbHj0zbJYzCpQ=
Expected: 6.1.7600.16385
Successfully traced component amd64_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_448b1c3c529ce8ed.
Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack
Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-22 21:48:46.877
Script hash: AS/gyxE4ETb1c9eSmnRXNOqNESluK69i+K/MbMhBhzo=
----------------------EOF-----------------------
A repair install of Windows 7 should work - make sure that your install disk is a good one, or download the iso from DigitalRiver and create a new disk.
See the tutorial here. Repair Install - Windows 7 Help Forums
hi, you never mentioned whether the computer you are using is an OEM build (Dell, HP, Acer, Sony, etc.) or a custom-built rig; you just gave us your specs. Please clarify this.
The reason I mention this is that you vented about Win7 and possibly upgrading to Win8.1--this is something that should not be taken trivially. 9/10 Customers I have that tried this upgrade failed the first time. You'll need to at least do the following:
1) Download the Windows8.1 Compatability Assistant from microsoft.com and run it on your Internet connected computer. If it fails; you'll have to remedy any software and hardware inconsistencies otherwise 8.1 upgrade will most certainly fail. :frown:
2) Contact the Manufacturer of your comptuer [or the Motherboard maker if you built your own custom-rig desktop] and ASK THEM if your hardware has BIOS support for 8.1. If it doesn't that upgrade probably will fail. :frown:
3) Visit the website of your computer manufacturer or Motherboard maker and see if they have posted BIOS updates AND drivers that are compatible with your hardware. If they do not, it's unlikely to work on 8.1 :frown:
Further if your computer (if OEM make) does not have a "Windows 8.1 Ready" or "Windows 8.1 Compatible" sticker on it somewhere, it means the hardware was never tested as WHQL passing by Microsoft. That means that it's not guaranteed to run 8.1; it'd be a crapshoot at best. **this is not applicable for Motherboard makers, as they put their stickers on the outside of the box; if you kept the box you can look to see if it's there. If it's not; same as OEM situation above, it's unlikely to work. :ermm:
Just FYI.
BIGBEARJEDI
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!