Screen goes blank momentarily.

[Peter Jason]

Some times when I'm using the computer the screen goes black (like
when turned off) for about 3 seconds and then comes back on by itself.

This has been happening for weeks now and happens about twice/day.

The closest error message I can find in Windows7 Computer Management
is:

***
Activation context generation failed for "c:\program files\microsoft
security client\MSESysprep.dll".Error in manifest or policy file
"c:\program files\microsoft security client\MSESysprep.dll" on line
10. The element imaging appears as a child of element
urn:schemas-microsoft-com:asm.v1^assembly which is not supported by
this version of Windows.
***

though this is about ten minutes before the event.


Incidentally, how does one use the "Performance Monitor" in Computer
Management. All there is is a blank chart? Can this be used to give
a bar chart of errant events?

Peter

 

[Gene E. Bloch]

Incidentally, how does one use the "Performance Monitor" in Computer
Management. All there is is a blank chart? Can this be used to give
a bar chart of errant events?

Click on the green Plus Sign and add something to view.

 

[charlie]

Some times when I'm using the computer the screen goes black (like
when turned off) for about 3 seconds and then comes back on by itself.

This has been happening for weeks now and happens about twice/day.

The closest error message I can find in Windows7 Computer Management
is:

***
Activation context generation failed for "c:\program files\microsoft
security client\MSESysprep.dll".Error in manifest or policy file
"c:\program files\microsoft security client\MSESysprep.dll" on line
10. The element imaging appears as a child of element
urn:schemas-microsoft-com:asm.v1^assembly which is not supported by
this version of Windows.
***

though this is about ten minutes before the event.


Incidentally, how does one use the "Performance Monitor" in Computer
Management. All there is is a blank chart? Can this be used to give
a bar chart of errant events?

Peter

Some video cards and driver versions may be involved (ATI/AMD, NVIDIA).
In previous versions of the drivers, there may have been errors logged
that basically said that the video card/driver combination did not
respond within a time limit. The usual applications were game related,
with complex graphics and high speed changes, such as "first person
shooters", with often four core CPUs.