Blue Screen Craches Related to Gupdate Conflict with Display Driver

cyberbiker said:

For the last few week I was having a lot of blue screens and audio/video distortions on my Asus 1005PE. An error often came up after the distortions indicating the display driver (Intel Graphics Media Accelerator 3150) had failed and reset. I used Cmputer Manager (C:\Windows\SysWOW64\compmgmt.msc) to isolate the problem and found the only commmon item just before the crashes in Event Viewer had to do with a service called gupdate, related to a Google Update. There were multiple Google Update listings in Task Schedular and in Services they were automatic. By changing them from automatic to manual in Services the problem seems to have been eliminated.


A search of gupdate on Sevenforums indicates others have had various problems with it too. Here is an example of the listing in Event Viewer.
-----------------------------

Log Name: Application
Source: gupdate
Date: 6/15/2011 11:23:27
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Cyberbiker-PC

Description:
The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Service stopped

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="gupdate" />
<EventID Qualifiers="0">0</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-06-15T18:23:27.000000000Z" />
<EventRecordID>161529</EventRecordID>
<Channel>Application</Channel>
<Computer>Cyberbiker-PC</Computer>
<Security />
</System>
<EventData>
<Data>Service stopped</Data>
</EventData>
</Event>

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.