J jackhandsome Member Joined Mar 7, 2015 Posts 10 Mar 7, 2015 #1 I have about a 3 year old Win 7 64-bit computer. It has had Windows update issues for quite some time and always been a bit quirky. I just started reading about the error code and have done all of the appropriate response fixes from Microsoft. Let me preface this by saying I have always had issues with the memory which I am installing new chips hopefully today. Until then I was wondering if someone could have a look at the simple text that SFCFix came up with. It will be below. I also cannot run the scf /scannow command in windows or safe mode due to the usual system protection thing. I thought maybe if I posted the SFCFix log maybe someone will recognize it as being something that someone has seen. Thank you in advance. SFCFix version 2.4.3.0 by niemiro. Start time: 2015-03-07 13:50:59.827 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. *EDIT* Crap, I just realized there were specific posting instructions for update fixes. I will be up at the place where the computer is shortly and will do what is needed. Sorry about that. AutoAnalysis:: WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_mdmmc28ø.inf_31sf3856ad264e35_6n1.7600.q6385_no?e_4812c`d1f5383 34 WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsogt-windo§s-b..io.data-cm´linetoo}_31bf38ô6ad364eã5_6.1.7601.17514_none_e6510234bbcb2a8c SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 0 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 15 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 2.4.3.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2015-03-07 13:54:20.849 ----------------------EOF-----------------------
I have about a 3 year old Win 7 64-bit computer. It has had Windows update issues for quite some time and always been a bit quirky. I just started reading about the error code and have done all of the appropriate response fixes from Microsoft. Let me preface this by saying I have always had issues with the memory which I am installing new chips hopefully today. Until then I was wondering if someone could have a look at the simple text that SFCFix came up with. It will be below. I also cannot run the scf /scannow command in windows or safe mode due to the usual system protection thing. I thought maybe if I posted the SFCFix log maybe someone will recognize it as being something that someone has seen. Thank you in advance. SFCFix version 2.4.3.0 by niemiro. Start time: 2015-03-07 13:50:59.827 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. *EDIT* Crap, I just realized there were specific posting instructions for update fixes. I will be up at the place where the computer is shortly and will do what is needed. Sorry about that. AutoAnalysis:: WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_mdmmc28ø.inf_31sf3856ad264e35_6n1.7600.q6385_no?e_4812c`d1f5383 34 WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsogt-windo§s-b..io.data-cm´linetoo}_31bf38ô6ad364eã5_6.1.7601.17514_none_e6510234bbcb2a8c SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 0 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 15 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 2.4.3.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2015-03-07 13:54:20.849 ----------------------EOF-----------------------
J jackhandsome Member Joined Mar 7, 2015 Posts 10 Mar 7, 2015 #2 For whatever reason I was not able to edit my initial post so I am replying with the zipped cbs file. If anyone could take a gander at it I would appreciate it. Thank you.
For whatever reason I was not able to edit my initial post so I am replying with the zipped cbs file. If anyone could take a gander at it I would appreciate it. Thank you.
Go The Power Senior Administrator, Windows Update Expert, Contributor Staff member Joined Mar 5, 2012 Posts 6,292 Location Adelaide, South Australia Mar 8, 2015 #3 Hello and welcome to the forum :) We will try running another scan with SFCFix, but this time using another method: 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. Download SFCFix.exe (by niemiro) and save this to your Desktop. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt. Code: BitShift:: Click on File -> Save. Close out of SFCFixScript.txt. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. 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.
Hello and welcome to the forum :) We will try running another scan with SFCFix, but this time using another method: 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. Download SFCFix.exe (by niemiro) and save this to your Desktop. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt. Code: BitShift:: Click on File -> Save. Close out of SFCFixScript.txt. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. 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.
J jackhandsome Member Joined Mar 7, 2015 Posts 10 Mar 9, 2015 #4 Thank you for your response. I just got in where the computer is this morning. It has been running the script for close to 30 minutes so far. I will let it run and see if it finishes and then reply with the contents. Regarding the CODE tags: Does that just mean to put CODE at the beginning of the text and /CODE at the end? Sorry for my ignorance but am new to that.
Thank you for your response. I just got in where the computer is this morning. It has been running the script for close to 30 minutes so far. I will let it run and see if it finishes and then reply with the contents. Regarding the CODE tags: Does that just mean to put CODE at the beginning of the text and /CODE at the end? Sorry for my ignorance but am new to that.
J jackhandsome Member Joined Mar 7, 2015 Posts 10 Mar 9, 2015 #5 I Ctrl+c'd the script to stop it because I had to use the computer for something else and got the following: Code SFCFix version 2.4.3.0 by niemiro. Start time: 2015-03-09 09:42:30.390 Microsoft Windows 7 Service Pack 1 - amd64 Using .txt script file at C:\Users\server\Desktop\SFCFixScript.txt.txt [0] SFCFix version 2.4.3.0 by niemiro has encountered an unhandled exception. Currently storing 0 datablocks. Finish time: 2015-03-09 10:12:35.313 Script hash: hBI6Mql4H4Bclpn1EppfVE6OvuMnGbPTS9YilWvhfmA= ----------------------EOF----------------------- /CODE I know that means nothing and I will try it again probably tonight. How long does it generally take to run? If it is an hour or 2 I'll let it run but if it is generally 5-10 minutes then I know the script is not going through as it should.
I Ctrl+c'd the script to stop it because I had to use the computer for something else and got the following: Code SFCFix version 2.4.3.0 by niemiro. Start time: 2015-03-09 09:42:30.390 Microsoft Windows 7 Service Pack 1 - amd64 Using .txt script file at C:\Users\server\Desktop\SFCFixScript.txt.txt [0] SFCFix version 2.4.3.0 by niemiro has encountered an unhandled exception. Currently storing 0 datablocks. Finish time: 2015-03-09 10:12:35.313 Script hash: hBI6Mql4H4Bclpn1EppfVE6OvuMnGbPTS9YilWvhfmA= ----------------------EOF----------------------- /CODE I know that means nothing and I will try it again probably tonight. How long does it generally take to run? If it is an hour or 2 I'll let it run but if it is generally 5-10 minutes then I know the script is not going through as it should.
Go The Power Senior Administrator, Windows Update Expert, Contributor Staff member Joined Mar 5, 2012 Posts 6,292 Location Adelaide, South Australia Mar 9, 2015 #6 It depends on how many Bitshifts are detected, it would be best to run it for a few hours.
J jackhandsome Member Joined Mar 7, 2015 Posts 10 Mar 10, 2015 #7 I ran it for 8 hours and still either didn't finish or was caught in a loop. I noticed it was maxing out 1 of the cores. I think the best option honestly is a clean install which I didn't want to do. When I got to thinking about it there has always been issues. When I was installing windows initially I think the ram had corrupted the os because I had to fight it to get windows installed which should never happen. I knew at the time there was troubleshooting to do but was in a time crunch. I'm pretty sure that if I just do a clean install with the new memory then it should be fine. Thank you for your time and effort. I do appreciate it.
I ran it for 8 hours and still either didn't finish or was caught in a loop. I noticed it was maxing out 1 of the cores. I think the best option honestly is a clean install which I didn't want to do. When I got to thinking about it there has always been issues. When I was installing windows initially I think the ram had corrupted the os because I had to fight it to get windows installed which should never happen. I knew at the time there was troubleshooting to do but was in a time crunch. I'm pretty sure that if I just do a clean install with the new memory then it should be fine. Thank you for your time and effort. I do appreciate it.
Go The Power Senior Administrator, Windows Update Expert, Contributor Staff member Joined Mar 5, 2012 Posts 6,292 Location Adelaide, South Australia Mar 10, 2015 #8 When seeing bitflips in the registry it is often the cause of bad RAM. A fresh install of Windows will be good here.
When seeing bitflips in the registry it is often the cause of bad RAM. A fresh install of Windows will be good here.
