I ran memtest86 and you were certainly right about having a memory problem... I didn't think that there could be that much RED and the computer even boot up let alone run. I have ordered some new memory and I'll be back when it gets here and I get this computer back up. I won't bother to post these test results ...
Once you get the machine up and tested OK, run a full new set of logs and post those, and we'll use them for the fixes.
I have installed the new memory which passed the mem86 test. I then reran SURT and have attached the new CBS log.
OK - there's a fair old mess in CheckSUR, but I'll have a go at it.
I need to have a look at your COMPONENTS registry hive
Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
You may have to boot to Safe Mode to be able to access the COMPONENTS file, as it can sometimes be locked once loaded by the registry.
(first the 'easy stuff)...
Code:Checking Component Store (f) CSI Missing Identity 0x00000000 appid f2tf75e8598..538c1f07518_31bf3856at364e35_v.1.7601.22296_755f11e36>d01c8b (f) CSI Corrupt Registry Value 0x000000DE S256H amd64_95addf927ae721b7f305a2b2cbf28572_31bf3856ad364e35_6.1.7601.17965_none_675da3dfadf3c614 Data type 524291 should be 3 (f) CSI Payload File Missing 0x00000000 rpcrt4.dll amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.18205_none_122c58425baaf932 (f) CSI Manifest Missing 0x00000002 wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_11.2.9600.17126_none_4cb2e6e683ccce51.manifest wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_11.2.9600.17126_none_4cb2e6e683ccce51 (fix) CSI Manifest Missing CSI File Replaced File: wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_11.2.9600.17126_none_4cb2e6e683ccce51.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab (f) CSI Missing Deployment Key 0x00000000 f28cc4e6857..bb7c48a652e_31bf3856ad364e35_11.2.9600.17280_8129e967c5530e5f HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f22f9fff4a2..d782c9b9ae9_31bf3856ad364e35_11.2.9600.17358_1e3fc9c24fa3d9cc HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2af656ab65..ef6451226e6_b77a5c561934e089_6.1.7601.18529_a22394df6a5050bd HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2c8537ebb1..96aa44b580b_b77a5c561934e089_6.1.7601.22309_0518b22a574cf41c HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f20f75e8598..538c1f07518_31bf3856ad364e35_6.1.7601.22296_715f11e362d01c8b HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2b9c0a826b..2abd65edf4c_31bf3856ad364e35_6.1.7601.17669_0389b8710b1f831b HKLM\Components\CanonicalData\Deployments (f) CSI Corrupt Identity 0xC0150016 1658d7108321c9dcd2f2c137a45ef498, Culture=neutral, Version=6.1.7601.22125, PublicKeyToken=31bf3856ad36<e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_1658e7108321c9dcd2f2c137a45ef498_31bf3856ad364e35_6.1.7601.22125_none_4e243f89cc24586b Bad identity (f) CSI Manifest Missing 0x00000002 amd64_1658e7108321c9dcd2f2c137a45ef498_31bf3856ad364e35_6.1.7601.22125_none_4e243f89cc24586b.manifest amd64_1658e7108321c9dcd2f2c137a45ef498_31bf3856ad364e35_6.1.7601.22125_none_4e243f89cc24586b (f) CSI Missing Deployment Key 0x00000000 f27d03c0155..77fb3b0170f_31bf3856ad364e35_6.1.7601.22736_baca07c646f5cbb9 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2c63154082..4e8de5323a4_b03f5f7f11d50a3a_6.1.7601.22617_3b587cc37281df4d HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2d71d529d1..7a681acf7ad_31bf3856ad364e35_6.1.7601.22724_3f0de4a2a029d465 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2afa72979f..22a6dcd805a_b03f5f7f11d50a3a_6.1.7601.22309_5d9b9db1cb3d29ba HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2228fcd685..c7459d63ef6_31bf3856ad364e35_6.1.7601.22724_10a11dc5d7cda94e HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 f2e63181cbc..30a3214bf81_31bf3856ad364e35_11.2.9600.17728_659000ba11c8bb0d HKLM\Components\CanonicalData\Deployments (f) CSI C Mark Deployment Not Marked 0x00000000 c!a0c608c3639..eafe8b21632_31bf3856ad364e35_6.1.7601.21710_843990578e9fa203 amd64_a0c608c3639a80323680feafe8b21632_31bf3856ad364e35_6.1.7601.21710_none_843990578e9fa203 (f) CSI C Mark Deployment Not Marked 0x00000000 c!a0c608c3639..eafe8b21632_31bf3856ad364e35_6.1.7601.21710_843990578e9fa203 amd64_microsoft-windows-diskdump_31bf3856ad364e35_6.1.7601.21710_none_c569d904c706f2b3
Last edited by NoelDP; 16 Sep 2015 at 10:31. Reason: add note about Safe Mode, and first-fix data
OK. Think I've got the components file linked here; https://www.dropbox.com/s/c7w5s8m714...nents.zip?dl=0
Got it - it may take me a couple of days to check through it, but shout if you haven't heard by Saturday afternoon!
Whatever bugs I have they sound particularly nasty. I really appreciate the effort, thanks.
Let's see how I've done so far...
I've uploaded a file - tbeab.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)
Create a new System Restore point
Open an Elevated Command Prompt, and run the following commands.
If you get an error with any command, STOP THERE - do not reboot! - post for instructions.Code:IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1 REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1 COPY "%userprofile%\desktop\tbeab\COMPONENTS" C:\Windows\System32\config .
Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.
I screwed up (sorta). I had copied the new file to the desktop, then opened an elevated cmd prompt and began entering the command you sent. I got to the end REN entry (next step COPY) and then before entering the COPY part I mistakenly hit ENTER. So the command executed and returned to the command prompt. Flustered, I exited and then went back into the cmd window to try entering the COPY portion. Then I remembered your note about stopping if things weren't going right so I thought I'd better get some input before I continued. I'm currently sitting in cmd window.
That's why I suggest using copy/paste for commands :)
Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.
Quote