Outlook locks up computer after resume from standby or hibernation

[Warren]

I just migrated from Office 2003 & Outlook Express to the Office 2007
Enterprise suite with Outlook. That all seemed to go well and everything is
working with one exception. If an Outlook window is open/visible when the
system goes into standby (or hibernation) and then is subsequently re-awaken,
as soon as the Outlook window reappears, the video signal is turned off
(screen goes black and monitor reports a loss of video) and the system is
locked up until a hard reset is performed. If Outlook is closed at the time
of the standby/resume then Outlook can be started without a problem. If
Outlook is minimized at the time of the standby/resume then the system will
run properly after the resume up to the point that the Outlook window is
restored and then it again freezes in the same manner as described before.
This is a Win XP system with SP3 and is fully up to date with all patches
according to both the Microsoft Update and Office Update web sites. The ATI
video drivers are the latest available from ATI/AMD. The Mb BIOS is the
latest available. The system passes the Office 2007 diagnostics without any
problems being identified. The number of startup programs have been minimized
without making a difference. Other Office 2007 programs do not present this
same behavior if left open over a standby/resume The system was 100% stable
for many months prior to this.

Any ideas?

 

[DL]

Check in Event Viewer for relevent err's that appear on standby resumption

 

[Warren]

I just triggered the fault so I could look at what it does to the event logs.
Unfortunately the information there is a bit sparse. Only in the System log
did I find one informational item and it was written after the recovery
reboot"

"
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1000
Date: 11/29/2008
Time: 5:15:09 PM
User: N/A
Computer: WARREN
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e
(0xc0000005, 0xbf038ecc, 0xa6cdd724, 0x00000000). A full dump was not saved.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"

This was the last event before the lockup and it's not obvious to me that it
had anything to do with it:

"
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 11/29/2008
Time: 5:07:37 PM
User: N/A
Computer: WARREN
Description:
The Windows Image Acquisition (WIA) service entered the running state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"

Other than directly involving Microsoft, is there a more appropriate place
to be asking about this other than this particular forum?

Thanks for taking the time to read my question and offer a suggestion.

 

[DL]

Nothing helpfull there then
You say it was previously stable, are you able to recollect anything that
has changed, eg driver update?

 

[Warren]

Only thing changed in the recent past have been the montlhy updates from
Microsoft and of course the big change to Office 2007 and all its attendant
patches.

 

[DL]

Has it been ok since the upgrade to Office 2007 or did the problem occur as
soon as the upgrade took place?

 

[Warren]

The problem started with the upgrade. So far it has always locked up every
time the conditions outlined at the start of this thread have been present
and it has done this ever since (& only since) the upgrade to Office (and
specifically Outlook) 2007 was installed.

 

[Warren]

OK, I think I may have this resolved. After much thrashing about this morning
with the installation and removal of ATI video drivers (and, along the way,
reinstallation of the current Abit motherboard chipset drivers) I have
fallen back to older (a bit more than a year) video drivers that more closely
match what the video card was delivered with rather than the more recent (a
bit more than a month old) ones that were in use. The system no longer hangs
upon resume with this older driver (or perhaps it was the re-installation of
the MB chipset driver). Anyway it's working now and I'm grateful for that and
also your suggestions. Thanks!

 

[DL]

Glad its now all ok

OK, I think I may have this resolved. After much thrashing about this
morning
with the installation and removal of ATI video drivers (and, along the
way,
reinstallation of the current Abit motherboard chipset drivers) I have
fallen back to older (a bit more than a year) video drivers that more
closely
match what the video card was delivered with rather than the more recent
(a
bit more than a month old) ones that were in use. The system no longer
hangs
upon resume with this older driver (or perhaps it was the re-installation
of
the MB chipset driver). Anyway it's working now and I'm grateful for that
and
also your suggestions. Thanks!

 

[Warren]

Just as a final followup, after several days of good behavior from the system
I tried re-installing the newer ATI driver and the problem returned.
Re-installation of the old ATI driver again fixed the problem. That says that
the problem is with the ATI driver and Outlook and has nothing to do with the
MB chipset driver.

 

[Jayv007]

Warren,
I googled the problem I have been having and it appears it has some
similarities. I first thought it was something to do with the verizon p.c.
monitor i was running. Deleted that, computer didnt freeze up allday. left
outlook 2007 open, froze up in 10- min. so decided it was outlook. since the
p.c. monitor constantly communicates with outlook, it needs to be running.
Any suggestions on what to look for? I see you did something with the video
ati file.