Weekly Windows update - causes display lockup after reboot (Win 7 64-bit)

[cool8man]

My setup is Windows 7 (64-bit) running on a 2009 MacBook Pro (Nvidia GPU). Using latest Nvidia drivers for Geforce 9400M. Boot Camp version is 3.2


This annoying problem has been ongoing for me for years. After I download and install the weekly Windows Updates the following happens:


The computer reboots after update like it's supposed to and seems fine. However once the display goes to sleep the computer apparently freezes up and the display/computer will never resume again. The only thing I can do is hold down the power button and shutdown. (Very dangerous scenario if something I'm working on doesn't autosave.)

This only ever happens if I perform a windows update and it only happens one time immediately after the update. Otherwise the computer functions normally and has no problems with the display or system sleeping.

 

[Quad5Ny]

Open up Event Viewer and post the event logs from the time of the lockups.

Start Menu > Type in "Event Viewer" > Press Enter

 

[cool8man]

Open up Event Viewer and post the event logs from the time of the lockups.

Start Menu > Type in "Event Viewer" > Press Enter

These are the errors and warnings I have for the past 24 hours:


Log Name: System
Source: Service Control Manager
Date: 5/13/2011 4:34:09 AM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MBP
Description:
The lxecCATSCustConnectService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.


Log Name: System
Source: Service Control Manager
Date: 5/13/2011 4:34:09 AM
Event ID: 7009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MBP
Description:
A timeout was reached (30000 milliseconds) while waiting for the lxecCATSCustConnectService service to connect.

Log Name: System
Source: Service Control Manager
Date: 5/13/2011 4:34:12 AM
Event ID: 7023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MBP
Description:
The Windows Modules Installer service terminated with the following error:
%%16405


Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 5/13/2011 4:51:49 AM
Event ID: 4
Task Category: Logging
Level: Warning
Keywords: Session
User: SYSTEM
Computer: MBP
Description:
The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 5/13/2011 4:33:26 AM
Event ID: 1530
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: MBP
Description:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-1869090512-1445535300-4267580786-1001:
Process 5064 (\Device\HarddiskVolume3\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-1869090512-1445535300-4267580786-1001

Log Name: Application
Source: Bonjour Service
Date: 5/13/2011 4:33:24 AM
Event ID: 100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MBP
Description:
492: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)
Event Xml:


Log Name: System
Source: Microsoft-Windows-WLAN-AutoConfig
Date: 5/13/2011 4:33:29 AM
Event ID: 4001
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: MBP
Description:
WLAN AutoConfig service has successfully stopped.

Log Name: System
Source: Microsoft-Windows-WLAN-AutoConfig
Date: 5/13/2011 4:33:29 AM
Event ID: 10002
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: MBP
Description:
WLAN Extensibility Module has stopped.

Module Path: C:\Windows\System32\bcmihvsrv64.dll


Those were the errors in the past 24 hours. These are the warnings:

Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 5/13/2011 4:51:49 AM
Event ID: 4
Task Category: Logging
Level: Warning
Keywords: Session
User: SYSTEM
Computer: MBP
Description:
The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 5/13/2011 4:33:26 AM
Event ID: 1530
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: MBP
Description:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-1869090512-1445535300-4267580786-1001:
Process 5064 (\Device\HarddiskVolume3\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-1869090512-1445535300-4267580786-1001

Log Name: System
Source: Microsoft-Windows-WLAN-AutoConfig
Date: 5/13/2011 4:33:29 AM
Event ID: 4001
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: MBP
Description:
WLAN AutoConfig service has successfully stopped.

Log Name: System
Source: Microsoft-Windows-WLAN-AutoConfig
Date: 5/13/2011 4:33:29 AM
Event ID: 10002
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: AA-MBP
Description:
WLAN Extensibility Module has stopped.

Module Path: C:\Windows\System32\bcmihvsrv64.dll

 

[Quad5Ny]

I don't see anything in the logs that would cause your computer to just lock up. You have to make note of the time when this happens and then check the logs for any errors.


Also, did you disable Superfetch because you have a SSD? If you did, have you messed around with any other Default Windows Services/Settings?

If you disabled Superfetch and want to get rid of the ReadyBoot errors, follow the steps Here to stop the ReadyBoot trace on every boot.

 

[cool8man]

I'm so used to this blank display lock-up happening after each update that I've even tried rebooting the computer multiple times after an update just to see if that would prevent it from happening. Nope. After every windows update that requires a restart my computer needs to lock-up once. There doesn't seem to be anything I can do to stop it from happening.

Also, did you disable Superfetch because you have a SSD? If you did, have you messed around with any other Default Windows Services/Settings

I didn't disable Superfetch myself, but I have installed software from Intel that might have done that. As far as default windows services settings I have turned off some startup applications in msconfig, but that's about it.

These errors all started happening between 4:30-4:50 so I would think that was the period where the blank screen locked up. There isn't much logged between that time and when I discovered the computer locked up.