Bsod & Windows 7 Sp1 (ERROR_NOT_​FOUND 0×80070490) will not update

whatsntomake said:

I've been experiencing a random flurry of BSODs which I suspect has something to do with the reason why I cannot install Windows 7 SP1. However, these problems may not be connected and could be two seperate and distinct issues.

When I try to run the SP1 upgrade I receieve (ERROR_NOT_​FOUND 0×80070490).
What I've done:
I've tried running chkdsk and sfc/ scannow - which have both come up clean.
I've done a clean reformat of my pc several times - still no luck.
I've tried installing SP1 both from windows update (automatically) and from a manual download via the windows website.
I've run several of the microsoft FIX IT tools to no avial (and tried the aggressive fix)
Because I originally suspected that malwarebyte or eset security were causing persmission conflicts - I reformatted my pc and have no 3rd party antivirus/firewall program installed atm.
I have run memtest in the past several times - I do not believe this to be a memory fault.

My specs:
Windows 7 (x64)
Asus P67 Sabertooth with latest BIOS (1902)
Intel I7 2600k
Geforce GTX 590.
8 GB of corsair memory.
Razer Blackwidow Ultimate keyboard.
Steelseries sensei mouse.
Corsair 650w power supply.

I've attached my dump and cbs files. Please let me know if you need anything else and thank you for your help!

No DMP files included in upload please try this method


We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Whoops sorry I forgot to hit upload and posted w/o doing so. Sending up them up now.
My CBS file is quite large - I'll have to split it into multiple volumes and upload.
My DMP is now uploaded. My CBS files are uploaded.

whatsntomake said:

Whoops sorry I forgot to hit upload and posted w/o doing so. Sending up them up now.
My CBS file is quite large - I'll have to split it into multiple volumes and upload.
My DMP is now uploaded. My CBS files are uploaded.

There are two probable causes.

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

whatsntomake said:

Responding from mobile: I've already done the memtest test quite extensively in the past. For convience I will upload the CBS file on mediafire once I return to my desktop. I will try the driver verifier and post the results. Thanks for your help!

We dont really need the cbs.log. All we need to know is what it said at the end. Did it find violations? and was it ale to fix them?

I enabled driver verifier - so far no bsods. I've surfed a few web pages (as I don't have much else installed ATM - since i'm coming from a reformat)

I decided to try to re-install SP1 via windows update. It failed. There were no BSODs that occurred along the way. After windows update finished downloading SP1 - it began installing it. The updater said that it was successfully installed and that I had to restart. After I restarted (about reaching 10% in configuring update); windows said that it could not configure the update, undid the changes from SP1 and rebooted. When I log into my account I see the error below (attached).

I've had this issue several times after I decided to reformat my computer. As I indicated before I thought various programs might have been conflicting with the SP1 updater - so I've run through a few re-formats and full windows installations. I've heard that SP1 isn't supposed to be run off the bat off a fresh windows install - so I've always let windows updater run it's course (usually after about after 100 updates and a few reboots) and notify me when it's time to install SP1.

Sorry I am not very familiar with the CBS.log. Here's what I've noticed that sticks out:

Initializing online with Windows opt-in: False
2011-11-03 13:24:46, Info CBS SQM: Cleaning up report files older than 10 days.
2011-11-03 13:24:46, Info CBS SQM: Requesting upload of all unsent reports.
2011-11-03 13:24:46, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2011-11-03 13:24:46, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2011-11-03 13:24:46, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2011-11-03 13:24:46, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2011-11-03 13:24:46, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2011-11-03 13:24:46, Info CBS NonStart: Checking to ensure startup processing was not required.
2011-11-03 13:24:46, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x15ffe30
2011-11-03 13:24:46, Info CSI 00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
2011-11-03 13:24:46, Info CSI 00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x210
2011-11-03 13:24:46, Info CSI 00000007@2011/11/3:20:24:46.317 CSI perf trace:
CSIPERF:TXCOMMIT;255
2011-11-03 13:24:46, Info CBS NonStart: Success, startup processing not required as expected.
2011-11-03 13:24:46, Info CBS Startup processing thread terminated normally


I've noticed I didn't activate windows manually yet. I've just activated it. It's a long shot but maybe this will work for SP1. Time to leave it on and let install it overnight.

Have you run the update readiness tool?



Ensure you install the correct 64 or 32bit option for your system)

Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

ISC Diary | Windows 7 / 2008 R2 Service Pack 1 Problems

links courtesy jmh

I have run that tool. It installs a hotfix but unfortunetly doesn't solve the problem.

whatsntomake said:

I have run that tool. It installs a hotfix but unfortunetly doesn't solve the problem.

it is not supposed to "fix" anything just tell you if your system has all the files it needs to update to SP-1