Win 7 - regular BSOD events after a failed MS update

I am running Win 7 Pro SP1 (x32) on an Acer Travelmate laptop.

I was doing the '2nd Tuesday' updates (some 31 important updates
relating to MS Office and Windows 7) when it got stuck. I cancelled the
installation with the aim of re-starting it later. Since then I have
been getting a BSOD after a few minutes into booting up my machine.
Bootup goes well, I get to see my desktop, everything is fine (internet,
sound) but when I run a simple app e.g. browser, I get a BSOD.

What I have tried so far:

- I tried to go to a previous 'Restore point' to see if I could revert
whatever damage was done. While trying this in 'normal' mode I got a
BSOD. So I booted up in 'Safe Mode' and tried again. This time the
restore worked. However the BSODs keep happening.

- I ran a sfc /scannow. In normal mode it gave me a BSOD. When I did it
in 'Safe Mode' it worked its way to 100%. The message I got was
"Windows Resources Protection found corrupt files but was unable to fix
some of them. Details can be found in CBS.log"

I looked in CBS.log (which is large, nearly 14,658 KB) but I do not know
what to look for.

My question: Where is the best place to go to have the CBS analysed, and
how to fix the corrupt files.

Any pointers greatly appreciated.

Tnanks

On 16/07/2015 07:45, occam wrote:
I am running Win 7 Pro SP1 (x32) on an Acer Travelmate laptop.

I was doing the '2nd Tuesday' updates (some 31 important updates
relating to MS Office and Windows 7) when it got stuck. I cancelled the
installation with the aim of re-starting it later. Since then I have
been getting a BSOD after a few minutes into booting up my machine.
Bootup goes well, I get to see my desktop, everything is fine (internet,
sound) but when I run a simple app e.g. browser, I get a BSOD.

What I have tried so far:

- I tried to go to a previous 'Restore point' to see if I could revert
whatever damage was done. While trying this in 'normal' mode I got a
BSOD. So I booted up in 'Safe Mode' and tried again. This time the
restore worked. However the BSODs keep happening.

- I ran a sfc /scannow. In normal mode it gave me a BSOD. When I did it
in 'Safe Mode' it worked its way to 100%. The message I got was
"Windows Resources Protection found corrupt files but was unable to fix
some of them. Details can be found in CBS.log"

I looked in CBS.log (which is large, nearly 14,658 KB) but I do not know
what to look for.

My question: Where is the best place to go to have the CBS analysed, and
how to fix the corrupt files.

Any pointers greatly appreciated.


OK, I found a "How to analyze the log file entries that the Microsoft
Windows Resource Checker program generates" he
http://support.microsoft.com/kb/928228

.... but it doesn't help in case of what to do about a "cannot repair" entry.

BTW, there are a dozen or so "[SR] Cannot repair member file" in the
CBS.log

"occam" wrote in message
...
On 16/07/2015 07:45, occam wrote:
I am running Win 7 Pro SP1 (x32) on an Acer Travelmate laptop.

I was doing the '2nd Tuesday' updates (some 31 important updates
relating to MS Office and Windows 7) when it got stuck. I cancelled the
installation with the aim of re-starting it later. Since then I have
been getting a BSOD after a few minutes into booting up my machine.
Bootup goes well, I get to see my desktop, everything is fine (internet,
sound) but when I run a simple app e.g. browser, I get a BSOD.

What I have tried so far:

- I tried to go to a previous 'Restore point' to see if I could revert
whatever damage was done. While trying this in 'normal' mode I got a
BSOD. So I booted up in 'Safe Mode' and tried again. This time the
restore worked. However the BSODs keep happening.

- I ran a sfc /scannow. In normal mode it gave me a BSOD. When I did it
in 'Safe Mode' it worked its way to 100%. The message I got was
"Windows Resources Protection found corrupt files but was unable to fix
some of them. Details can be found in CBS.log"

I looked in CBS.log (which is large, nearly 14,658 KB) but I do not know
what to look for.

My question: Where is the best place to go to have the CBS analysed, and
how to fix the corrupt files.

Any pointers greatly appreciated.


OK, I found a "How to analyze the log file entries that the Microsoft
Windows Resource Checker program generates" he
http://support.microsoft.com/kb/928228

... but it doesn't help in case of what to do about a "cannot repair"
entry.

BTW, there are a dozen or so "[SR] Cannot repair member file" in the
CBS.log



If you'll change the "[SR]" to "[SR] Cannot" in your batch file (or command
line, however you are running it), you'll get a lot less lines in
sfcdetails.txt.
AFA troubleshooting the errors that can't be fixed, I found Google to be the
most help, even though that wasn't always helpful. There were some entries
that I never did find a solution to, but the machine runs fine anyhow. Go
figure.

Have you used something like BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html or WhoCrashed
http://www.resplendence.com/downloads to analyze your crash dump? That
might be the first place to start.

Did you restore from your most recent point, or did you go back another day
or two? Have you booted into safe mode and uninstalled the latest updates?
If you look in your update history, does it show that any of the most recent
ones failed? Those might be the ones that are giving you problems.
--
SC Tom

On 16/07/2015 13:39, SC Tom wrote:


"occam" wrote in message
...
On 16/07/2015 07:45, occam wrote:
I am running Win 7 Pro SP1 (x32) on an Acer Travelmate laptop.

I was doing the '2nd Tuesday' updates (some 31 important updates
relating to MS Office and Windows 7) when it got stuck. I cancelled the
installation with the aim of re-starting it later. Since then I have
been getting a BSOD after a few minutes into booting up my machine.
Bootup goes well, I get to see my desktop, everything is fine (internet,
sound) but when I run a simple app e.g. browser, I get a BSOD.

What I have tried so far:

- I tried to go to a previous 'Restore point' to see if I could revert
whatever damage was done. While trying this in 'normal' mode I got a
BSOD. So I booted up in 'Safe Mode' and tried again. This time the
restore worked. However the BSODs keep happening.

- I ran a sfc /scannow. In normal mode it gave me a BSOD. When I did it
in 'Safe Mode' it worked its way to 100%. The message I got was
"Windows Resources Protection found corrupt files but was unable to fix
some of them. Details can be found in CBS.log"

I looked in CBS.log (which is large, nearly 14,658 KB) but I do not know
what to look for.

My question: Where is the best place to go to have the CBS analysed, and
how to fix the corrupt files.

Any pointers greatly appreciated.


OK, I found a "How to analyze the log file entries that the Microsoft
Windows Resource Checker program generates" he
http://support.microsoft.com/kb/928228

... but it doesn't help in case of what to do about a "cannot repair"
entry.

BTW, there are a dozen or so "[SR] Cannot repair member file" in the
CBS.log



If you'll change the "[SR]" to "[SR] Cannot" in your batch file (or
command line, however you are running it), you'll get a lot less lines
in sfcdetails.txt.
AFA troubleshooting the errors that can't be fixed, I found Google to be
the most help, even though that wasn't always helpful. There were some
entries that I never did find a solution to, but the machine runs fine
anyhow. Go figure.

Have you used something like BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html or WhoCrashed
http://www.resplendence.com/downloads to analyze your crash dump? That
might be the first place to start.

No, but I will definitely look into those. Thanks.


Did you restore from your most recent point, or did you go back another
day or two? Have you booted into safe mode and uninstalled the latest
updates? If you look in your update history, does it show that any of
the most recent ones failed? Those might be the ones that are giving you
problems.

There was only one (most recent) restore point, to which I reverted. (I
remember reducing the space allocated to restore points to a bare
minimum some time ago in order to not carry more that 2 restore points
at any time.)

Thanks for your feedback

"occam" wrote in message
...
On 16/07/2015 13:39, SC Tom wrote:


"occam" wrote in message
...
On 16/07/2015 07:45, occam wrote:
I am running Win 7 Pro SP1 (x32) on an Acer Travelmate laptop.

I was doing the '2nd Tuesday' updates (some 31 important updates
relating to MS Office and Windows 7) when it got stuck. I cancelled
the
installation with the aim of re-starting it later. Since then I have
been getting a BSOD after a few minutes into booting up my machine.
Bootup goes well, I get to see my desktop, everything is fine
(internet,
sound) but when I run a simple app e.g. browser, I get a BSOD.

What I have tried so far:

- I tried to go to a previous 'Restore point' to see if I could revert
whatever damage was done. While trying this in 'normal' mode I got a
BSOD. So I booted up in 'Safe Mode' and tried again. This time the
restore worked. However the BSODs keep happening.

- I ran a sfc /scannow. In normal mode it gave me a BSOD. When I did
it
in 'Safe Mode' it worked its way to 100%. The message I got was
"Windows Resources Protection found corrupt files but was unable to fix
some of them. Details can be found in CBS.log"

I looked in CBS.log (which is large, nearly 14,658 KB) but I do not
know
what to look for.

My question: Where is the best place to go to have the CBS analysed,
and
how to fix the corrupt files.

Any pointers greatly appreciated.


OK, I found a "How to analyze the log file entries that the Microsoft
Windows Resource Checker program generates" he
http://support.microsoft.com/kb/928228

... but it doesn't help in case of what to do about a "cannot repair"
entry.

BTW, there are a dozen or so "[SR] Cannot repair member file" in the
CBS.log



If you'll change the "[SR]" to "[SR] Cannot" in your batch file (or
command line, however you are running it), you'll get a lot less lines
in sfcdetails.txt.
AFA troubleshooting the errors that can't be fixed, I found Google to be
the most help, even though that wasn't always helpful. There were some
entries that I never did find a solution to, but the machine runs fine
anyhow. Go figure.

Have you used something like BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html or WhoCrashed
http://www.resplendence.com/downloads to analyze your crash dump? That
might be the first place to start.

No, but I will definitely look into those. Thanks.


Did you restore from your most recent point, or did you go back another
day or two? Have you booted into safe mode and uninstalled the latest
updates? If you look in your update history, does it show that any of
the most recent ones failed? Those might be the ones that are giving you
problems.

There was only one (most recent) restore point, to which I reverted. (I
remember reducing the space allocated to restore points to a bare
minimum some time ago in order to not carry more that 2 restore points
at any time.)

Thanks for your feedback

You're welcome :-)

Had any success fixing it yet?
--
SC Tom

On 16/07/2015 7:45 AM, occam wrote:
I am running Win 7 Pro SP1 (x32) on an Acer Travelmate laptop.

I was doing the '2nd Tuesday' updates (some 31 important updates
relating to MS Office and Windows 7) when it got stuck. I cancelled the
installation with the aim of re-starting it later. Since then I have
been getting a BSOD after a few minutes into booting up my machine.
Bootup goes well, I get to see my desktop, everything is fine (internet,
sound) but when I run a simple app e.g. browser, I get a BSOD.

What I have tried so far:

- I tried to go to a previous 'Restore point' to see if I could revert
whatever damage was done. While trying this in 'normal' mode I got a
BSOD. So I booted up in 'Safe Mode' and tried again. This time the
restore worked. However the BSODs keep happening.

- I ran a sfc /scannow. In normal mode it gave me a BSOD. When I did it
in 'Safe Mode' it worked its way to 100%. The message I got was
"Windows Resources Protection found corrupt files but was unable to fix
some of them. Details can be found in CBS.log"

I looked in CBS.log (which is large, nearly 14,658 KB) but I do not know
what to look for.

My question: Where is the best place to go to have the CBS analysed, and
how to fix the corrupt files.

Any pointers greatly appreciated.



I have finally gotten to the root of the problem, described he

http://www.sevenforums.com/bsod-help...aged_area.html

Summary:
Looks like MSE and Windows Update messed with each other, which can be
avoided by temporarily turning off MSE and letting the update do its thing.

Solution: temporarily turn off MSE, do updates, resume MSE.

[Note: This is an excellent example why to be scared of automatic update
policy of Win 10. ]