BSOD from Windows Update

[paulking]

BSOD from Windows Update becomes "Unknown Error"

So far, I have little more than an operating system with no actual software installed. I have wanted to do some updates to my installation, but on several occasions, I have been stopped by a BSOD. Sometimes it is not on the screen long enough to construe the error. Also, I have been shown the location of the error logs that purportedly cause BSOD, but me, with admin privelages, have not enough permissions to see them.

My hardware is indicated in considerable detail under my user profile (click on my username and follow the links to "system spec").


Recently, these BSODs have disappeared to be replaced with:

• Unknown error: Code 800B0100
• Unknown error: Code 80073172
• Unknown error: Code 8007065E

Paul King

 

[marsmimar]

Hello Paul and welcome to Seven Forums.

Since you're dealing with BSOD issues, it would help if you set up your machine to generate dump files whenever you get a BSOD. And then follow the BSOD posting instructions.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

If I'm understanding things correctly, you're trying to install Windows Updates but one or more of them are causing a BSOD. Is the computer set to "Install updates automatically (recommended)"? If so, you probably won't know for sure which update is causing the problem. It's better to install updates manually in small groups (maybe 5 at a time.) Keep track of the KB numbers. Restart the computer after each group and make sure things are working as they should. If there are problems you'll know which group of updates to uninstall. Then try installing one at a time, rebooting after each one, and check the computer. They'll either all install correctly or you'll know the specific update causing problems. Start with the Critical updates first, then Important, then Recommended, then Optional. This is a slower method but usually gives better update results.

http://www.sevenforums.com/tutorials/2797-windows-update-settings-change.html

 

[paulking]

One KB article I read said, for one of my "unknown error" codes, that I try to run Windows Upgrade from the installation DVD during a running windows session. That idea worked (on the second try) but I still have 129 updates, and no error messages at least. I am now trying your idea. Of the 129 updates, I installed the ones near the end of the list, say the last 15 or 20. I got a BSOD from that. Those were mostly security updates, and a malicious software removal tool. I am trying again as I write this, with the first 5 (including some .NET updates, IE8, Media Centre, ActiveX Killbits), and lived. ... But then I died again with the following security updates. So, I downloaded the tool and I'll tell you later what the results are through the zip file.

 

[paulking]

I finally have the system dump from your program. Hopefully, it's all in order.

It has been attached.

Paul King

 

[marsmimar]

Paul, I'm asking one of the BSOD analysts to take a look at your dump file. (Unfortunately, I'm at work and my work computer isn't equipped for BSOD analysis.) Hopefuly he'll get back to you in a short while. Also, he's on the other side of the world.

 

[marsmimar]

The analyst I talked to is also at work and his computer isn't equipped for BSOD analysis either.

But he suggested you might try resetting your Windows Updates and re-register update components. I won't be home for about 8 hours (working the midnight shift.) If resetting update components doesn't work I will definitely go through your dump files.

http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

 

[paulking]

Still trying to install updates that can be installed. Might consider trying resetting Win Update later.

Installed the System Update Readiness tool, still got these errors.

[FONT=Courier New]UPDATE       | ERROR
-------------+--------------
KB2732500    | 800B0100
KB977074     | [/FONT][FONT=Courier New][FONT=Courier New]800B0100
[/FONT] KB2749655    | 800B0100
KB2743555    | 80073712
KB975496     | 800B0100
KB2761217    | 800736CC
[/FONT]

Windows has only offered some of the above updates again after these errors.

 

[NoelDP]

Please post the CheckSUR.log file -

 

[marsmimar]

Did you have a chance to reset your Windows Updates? Any error messages?

According to the files you provided, your C: drive doesn't have a lot of free space. Have you recently cleared out temp files, etc using Disk Cleanup or some other recommended product like CCleaner? Can you move some data like music, videos, etc elsewhere (flash drive, external HDD?).

It also appears that you may not have any antivirus installed. If that's true you might consider installing Microsoft Security Essentials, a free, light weight security suite that plays well with other Microsoft products.

Microsoft Security Essentials - Microsoft Windows

It would also be a good idea to run some additional scans on your computer. No anti-malware product is 100% effective 100% of the time. (If there as such a thing we'd all be using it.) Some of the recommended free utilities are:

Windows Defender Offline

TDSSKiller

Malwarebytes

ESET Online Scanner

HitmanPro

SuperAntispyware

You also appear to have an outdated Intel HD graphics driver from 2011 and an older BIOS from 2010. While they may not be contributing to the Windows Update problem it's just something to keep in mind.

Intel Download Center

Software & Driver Downloads HP TouchSmart tm2-1070ca Notebook PC | HP® Support

 

[paulking]

1. NoelDP, what is CheckSUR.log? I did a global search on C: and it wasn't there.

2. Marsmimar, I have NOD32 ready to install, and was putting it off until the updates were installed. I guess that was a bad plan.

3. An update I did from the installation DVD moved the entire previous installation of Windows to backup. That's where 49 gigs of the space went. It's gone, along with some other stuff. I still find it a bit unsettling that Windows 7 takes up 51 gigs of my HD, since I don't even have the HP drivers installed yet.

One thing at a time, though. I'll reset the windows updates now... after installing NOD32.

 

[NoelDP]

C:\Windows\Logs\CBS\Checksur.log and ..CheckSUR.persist.log are updated every time the CheckSUR tool is run.

 

[paulking]

As far as can be surmised, I have reset Windows Update according to KB971058 on the MS support site you pointed to.

The commands regsvr32.exe *.dll (which I entered one at a time on a batch file) were half-successful. There were many dlls it could not load or register, and a ton of errors (about 40-50% of the files) came from that. This took a while to do, but not as long as it took to resolve the issue with NOD32 (licensing was messed up, advice from their troubleshooting page seemed to fix it). I am presently doing a scan of C: drive.

Also, "netsh reset winsock" didn't work. I didn't know Windows still used "winsock" in this day and age.

NoelDP: while Windows happily installed the Windows Update Readiness tool, I am confused: is this a program that the user actually runs? I can't find it anywhere on C: drive.

 

[paulking]

Thanks for pointing out the location, NoelDP. I found the log file, for your perusal.

 

[NoelDP]

I've seen worse

It'll take me a little while to produce the fix protocol - back with a Christmas present later

 

[NoelDP]

I've uploaded a file - packpk.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder packpk in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:
C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[paulking]

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

As I said before: I am confused: is this a program that the user actually runs? I can't find it anywhere on C: drive.

 

[NoelDP]

Just run the download again
The only reason it says 'installing' is that the tool uses the TrustedInstaller service to do a lot of the work.

 

[paulking]

I have posted both CheckSUR files, and another output ZIP from SF_Diagnostic_Tool.exe, since there were a few more BSODs to make life interesting. I am beginning to suspect a corrupt HD.

 

[NoelDP]

There does seem to be creeping corruption present - the errors found in the new report weren't present in the initial one.

Perhaps you should run a CHKDSK C: /F before doing anything else, and see what the report is (it's a Wininit event in the Applications Event log)



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

CHKDSK C: /F

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

Then Open Event Viewer
navigate to Windows Logs\Application
Look there for a Wininit event - the details can be copied to your response.

 

[paulking]

What I got when I did that was, at boot, there was a quick screen indicating that CHKDSK is running, but then it quickly booted into Windows. The Event Viewer, looking under Windows Logs\Application tells of no such "wininit" event, up to 15 minutes before I actually booted. Just to be sure, I booted with chkdsk again the second time, but writing down the time (according to Windows) that I rebooted. Looking at the event logs over that time showed no record that I have invoked chkdsk /f c: