Windows Updates, but getting error code 80070246 = READY TO SEND EVENTS AND SYSTEM LO

[KHRIZZLEXMANE]

I've successfully created the usb drive and have formatted it, however the steps that follow are unclear...

am I supposed to follow these steps?

• Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

1. Shut down and turn off your computer.
2. Unplug all power sources to the system: unplug the power from the outlet/surge protector or PSU (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing (or remove the RAM panel if it is a laptop).
5. Remove all but one memory module making sure you are grounded while doing so.Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
   
6. Replace the casing (or replace the RAM panel if it is a laptop) and put the remaining memory module(s) in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.



Some of the best information provided by a user who had RAM problems that were difficult to track down:

 

[zcomputerwiz]

Don't follow those instructions, we only want to run the memory test program at this time. If memtest finds problems, then we will look at the machine.

I have a fix ready for you:

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.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. 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.

View attachment SFCFix.zip

 

[KHRIZZLEXMANE]

so now that I have the usb drive ready and formatted, what next? forgive my naive ways lol

 

[zcomputerwiz]

That's fine, let's wait on the memory test for now.

Please download and run the fix script from post #22

Post back with the results.

 

[KHRIZZLEXMANE]

SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-01 18:34:45.879
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Mark\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_340566a692262b8e465d19c0¿ab8743a_b03f5f7æ11d50a3a_6.1.76°1.22617_none_38¹d94aec0b26316.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installsqlstate_sql_b03f5f7f11d50a3a_6.1.7600.16385_none_5e893f5247903730.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-fw_nítfxperf_dll_31bn3856ad3¾4e35_6.2.7601.17514_none_5ec9dfb2784680æc.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-instállutillib_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_8b3db65294ce6352.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_neôfx-lh_s`ared_dll_keys_b03f5f7f11d50a3a_6.1.7600.16385_none_ad47410a2dd3a317.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_neôfx-installutil_exe_config_rtm_3¹bf3856ad364e35_6.1.7600.16385_none_c4b459e91851aaf5.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\62a1629ba9e99e6bdccb35f4a113135831773a2545b9d78052a8a41250973b17.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_545e2067025f300d6d686e10cf904683_b03f5f7f11d50a3a_6.1.7601.18410_none_47df726baf8d6265.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_c166e377fcecd5daae2afeb3316a2023_b03f5f7f11d50a3a_6.1.7601.18410_none_a8212f2bcce34fc4.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_d486ef7d420d3e61536a70f99e5f188b_b03f5f7f11d50a3a_6.1.7601.18410_none_75731594b75653c0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_wvpchbus.inf.resources_31bf3856ad364e35_7.1.7601.17514_ru-ru_94589588e6fde5ce.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_e60c403f5d728dab.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_340566a692262b8e465d19c0¿ab8743a_b03f5f7æ11d50a3a_6.1.76°1.22617_none_38¹d94aec0b26316.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installsqlstate_sql_b03f5f7f11d50a3a_6.1.7600.16385_none_5e893f5247903730.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-fw_nítfxperf_dll_31bn3856ad3¾4e35_6.2.7601.17514_none_5ec9dfb2784680æc.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-instállutillib_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_8b3db65294ce6352.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_neôfx-lh_s`ared_dll_keys_b03f5f7f11d50a3a_6.1.7600.16385_none_ad47410a2dd3a317.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_neôfx-installutil_exe_config_rtm_3¹bf3856ad364e35_6.1.7600.16385_none_c4b459e91851aaf5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_340566a692262b8e465d19c07ab8743a_b03f5f7f11d50a3a_6.1.7601.22617_none_389d94aec0b26316.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\62a1629ba9e99e6bdccb35f4a113135831773a2545b9d78052a8a41250973b17.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_545e2067025f300d6d686e10cf904683_b03f5f7f11d50a3a_6.1.7601.18410_none_47df726baf8d6265.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_c166e377fcecd5daae2afeb3316a2023_b03f5f7f11d50a3a_6.1.7601.18410_none_a8212f2bcce34fc4.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_d486ef7d420d3e61536a70f99e5f188b_b03f5f7f11d50a3a_6.1.7601.18410_none_75731594b75653c0.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_wvpchbus.inf.resources_31bf3856ad364e35_7.1.7601.17514_ru-ru_94589588e6fde5ce.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_e60c403f5d728dab.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7601.17514_none_5ec9dfb2784680fc.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installsqlstate_sql_b03f5f7f11d50a3a_6.1.7600.16385_none_5e893f5247903730.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installutillib_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_8b3db65294ce6352.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installutil_exe_config_rtm_31bf3856ad364e35_6.1.7600.16385_none_c4b459e91851aaf5.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_340566a692262b8e465d19c0¿ab8743a_b03f5f7æ11d50a3a_6.1.76°1.22617_none_38¹d94aec0b26316 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installsqlstate_sql_b03f5f7f11d50a3a_6.1.7600.16385_none_5e893f5247903730 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-fw_nítfxperf_dll_31bn3856ad3¾4e35_6.2.7601.17514_none_5ec9dfb2784680æc with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-instállutillib_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_8b3db65294ce6352 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_neôfx-lh_s`ared_dll_keys_b03f5f7f11d50a3a_6.1.7600.16385_none_ad47410a2dd3a317 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_neôfx-installutil_exe_config_rtm_3¹bf3856ad364e35_6.1.7600.16385_none_c4b459e91851aaf5 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_340566a692262b8e465d19c07ab8743a_b03f5f7f11d50a3a_6.1.7601.22617_none_389d94aec0b26316.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\62a1629ba9e99e6bdccb35f4a113135831773a2545b9d78052a8a41250973b17.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_545e2067025f300d6d686e10cf904683_b03f5f7f11d50a3a_6.1.7601.18410_none_47df726baf8d6265.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_c166e377fcecd5daae2afeb3316a2023_b03f5f7f11d50a3a_6.1.7601.18410_none_a8212f2bcce34fc4.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_d486ef7d420d3e61536a70f99e5f188b_b03f5f7f11d50a3a_6.1.7601.18410_none_75731594b75653c0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_wvpchbus.inf.resources_31bf3856ad364e35_7.1.7601.17514_ru-ru_94589588e6fde5ce.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_e60c403f5d728dab.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7601.17514_none_5ec9dfb2784680fc.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installsqlstate_sql_b03f5f7f11d50a3a_6.1.7600.16385_none_5e893f5247903730.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installutillib_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_8b3db65294ce6352.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_netfx-installutil_exe_config_rtm_31bf3856ad364e35_6.1.7600.16385_none_c4b459e91851aaf5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 17 datablocks.
Finish time: 2016-01-01 18:34:47.050
Script hash: RWRLbppunff8kywBfhVrVNE1pH8J7CvVhzdqD8Uci9U=
----------------------EOF-----------------------

 

[zcomputerwiz]

Very good. Let's run the System Update Readiness Tool to see where we're at.

System Update Readiness Tool (SURT)

If you don't already have the latest version, download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, zip up and attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

 

[KHRIZZLEXMANE]

sounds great, i'll be home in a handful of hours, will work on it as soon as i get there. I'll also be off the next two days hope to get this up and going im beyond excited!

 

[KHRIZZLEXMANE]

Tried to run the SURT in 64 bit, I get the ERROR 0X80004002...[h=1]no such interface supported error :huh:[/h]

 

[KHRIZZLEXMANE]

the results from the windows memory test.... "Your computer has a memory problem.."

 

[zcomputerwiz]

Ok. Is this machine still under warranty of any kind?

 

[KHRIZZLEXMANE]

No, it is no longer under warranty

 

[KHRIZZLEXMANE]

ran the dell system diagnostics tool... yeah memory is bad so it seems

 

[zcomputerwiz]

Have you installed ram in a computer before?

 

[KHRIZZLEXMANE]

Yes I have, I even checked the ram slots to ensure they were paired correctly.
It has been a while though. I am looking to purchase 16 Gbs for this beauty. A friend has advised me to reset the cmos once i do but to be honest I dont really know how to do that nor am i aware of any other manual adjustments ill have to make

 

[zcomputerwiz]

I wouldn't change any settings.

Are there two sticks of RAM in this computer or only one?

 

[KHRIZZLEXMANE]

There are 2 sticks, 4 slots.

 

[zcomputerwiz]

Very good. Shut the computer down, unplug the power cord from the power supply, then open the side of the case and ground yourself by either holding onto some exposed (shiny) metal on the case or use a grounding strap and remove one of the sticks of RAM by pushing down the tabs on either side.
Take the stick out and put it in a static safe bag or somewhere else where it will not be touched or damaged.

Close the side of the case and plug the power cord back in, then turn the computer on and run the memory diagnostics again.

 

[KHRIZZLEXMANE]

ok, I'll try that. so once i get the new stick for the ram, what do i do with the bad one?

 

[KHRIZZLEXMANE]

The reason I ask is because im going to get a whole new pair of ram sticks to replace these

 

[zcomputerwiz]

Ideally before receiving the new RAM we would test each current stick and slot individually to determine if it is a bad stick or a bad slot.