Link to home
Start Free TrialLog in
Avatar of mitch10021
mitch10021

asked on

Win7 does BSOD upon boot after installation of any Windows Updates

I have a recurring problem with my Win 7 64-bit machine that first occurred a few months ago: any time I allow Windows to install an update, the next reboot produces a BSOD with the error page_fault_in_nonpaged_area.

I have set Windows update to not install any updates automatically -- but nevertheless, it installed a couple of "critical updates" in the last few days without my intervention, so I got another BSOD this evening.

When I get the BSOD, System Repair fails. I have to boot into Safe Mode, run System Restore using a restore point before the update was installed, and then the machine will boot into "regular" Windows.  

Obviously this is not an acceptable situation for the long term.

The most recent STOP codes were:

Problem signature:
  Problem Event Name:      BlueScreen
  OS Version:      6.1.7600.2.0.0.768.3
  Locale ID:      1033

Additional information about the problem:
  BCCode:      50
  BCP1:      FFFFF880009AAFF8
  BCP2:      0000000000000000
  BCP3:      FFFFF800032C8680
  BCP4:      0000000000000000
  OS Version:      6_1_7600
  Service Pack:      0_0
  Product:      768_1

I have tried to upload the minidump file but I am unable to do so -- Windows keeps telling me I don't have permission, even though I am logged in as Administrator.  I then tried to get around the problem by zipping the DMP file -- but Windows wouldn't let me do that, either, and then after the zip process failed, the DMP file disappeared.  However, here's the log from the failed System Repair:

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ¿4/¿8/¿2011 10:50:00 PM (GMT)
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk1
Windows directory = F:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 281 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 109 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 374 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 2293 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 796 ms

Root cause found:
---------------------------
Unknown Bugcheck: Bugcheck 50. Parameters = 0xfffff880009aaff8, 0x0, 0xfffff8000327e680, 0x0.

Repair action: System Restore
Result: Cancelled

Repair action: System files integrity check and repair
Result: Failed. Error code =  0x490
Time taken = 871328 ms

---------------------------
---------------------------
 

Any help would be most appreciated.


Avatar of remixedcat
remixedcat
Flag of United States of America image

is the windows update service setup to manual or automatic or delayed start? is it disabled?

Please check that and let me know.
Avatar of noxcho
Why is your Windows folder located on F: drive?
I had one on D: before and it was fine.
I would like to have a look on Windows Disk Management from mitch's PC.
same here.
Avatar of mitch10021
mitch10021

ASKER

Windows Update Service is set to Delayed Start.  The setting for Windows Update in Control Panel is "Check for updates but let me choose whether to download and install them."

Windows is actually installed on my C: drive -- I don't know why it says F:\windows.

Attached is a screenshot of the Windows Disk Management interface.  
Disk-Management.JPG
ok then so it shouldn't be a services problem then unless the windows update files that perform the updates got corrupted....
if they did then you'd have to repair windows.
My understanding is that with Windows 7, the ability to do a repair install is a lot more limited than with XP -- my computer came with Windows, so I have an OEM Win 7 DVD, and I've read that a repair install cannot be performed with an OEM disk.

BTW, I ran sfc /verifyonly and it found no problems.
have you contacted your manufacturer and asked them for a disk that can?
ASKER CERTIFIED SOLUTION
Avatar of remixedcat
remixedcat
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Do you disconnect your Lacie, IOmega and MyBook external drives when making repair? If not then disconnect all of them except system drive and try repair again.
remixedcat: Thanks for that link.  I do have Kaspersky installed so perhaps there is some connection -- although I have a 64 bit system and it appears the problem referenced in that linked discussion was limited to 32 bit systems.

noxcho: I will definitely try that the next time this happens (although hopefully it won't happen again).

I had a problem like that related to service startup that was causing a BSOD. it was after installing the platform update for server 2008 that is required for IE9.
How did you resolve the problem?  
I had to reinstall. repairs did not work. :-(
it BSODed before it got past the little progress bar animation. could not get to safe mode :-( Good thing I had my hot recovery partition. (I have two server 2008 installs for this purpose)
Please set the SATA mode in BIOS.
Let's get us minidump file. Can you change its extention to .png instead of .dmp and load here?
Here's a minidump file -- it's not from a BSOD that followed a reboot-after-update (that's the one that disappeared, as described in my original post); rather, it's from a BSOD that occurred after trying to repair the system after the BSOD.


041011-24492-01.dmp
One other new symptom: since yesterday, the two USB ports on the front panel of the computer don't work. They don't recognize any devices plugged in (e.g., a USB flash drive, an iPhone), and the iPhone won't even charge from either of those USB ports.  I am getting really tempted to restore my boot drive from a drive image. My fear is that the underlying problem, whatever it is, is present in the drive images on my backup drive, too.

The other action I am contemplating was inspired by the discussion linked above: uninstalling Kaspersky IS, then trying to use Windows Update to bring the system up to date, and then reinstalling Kaspersky.  But I'm just afraid it will be a waste of time, or, even worse, I'll wind up with a totally unusable system. (That shouldn't happen, I know, because I have my drive images -- created with ShadowProtect Desktop -- on an external hard drive, and that external hard drive is copied to a second external hard drive, so I do have a belt-and-suspenders backup that ought to work. Plus I have data backed up in the cloud via CrashPlan. But I just don't want to have to deal with a situation like that if it should happen.)  
mabye your OS got corrupted.... if so the best thing is to repair or re-install.

let's hope those backups aren't corrputed!
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
noxcho: I think that makes sense. I will run memtest as a first step and see if it turns up any problems with the RAM.  (I'm almost hoping it's a problem with RAM because replacing that will be easier than reinstalling Windows.) I'll report back.

Some progress:  I ran memtest and it showed no errors. Then I uninstalled Kaspersky Internet Security altogether, and then dared to install a Windows Update.  I decided to try installing SP1 to see if I could successfully get it out of the way, and in fact the installation worked -- I wound up with  a Windows 7 SP1 system that booted successfully. Next I plan to install the remaining updates that are recommended by Windows Update -- but I'm going to install them one at a time, rebooting each time even if not required by the update installation -- to make sure that they don't screw up the system, and if one of them does screw up the system, I'll know exactly which one it was.

Eventually, I have to reinstall my security software, but I'm seriously considering something other than Kaspersky in light of the aggravation it caused.
I recommend Sophos or ESET anti-virus they are both excellent.
I used to use ESET but I switched to Kaspersky about three years ago.  ESET was no longer getting good scores in the various antivirus tests.  But maybe I should reconsider it now.  
Have a look on F-Secure antivirus. My personal experience with it is very positive.