errors in Win 8.1 system event viewer related to amdkmdap and monblanking.

I am experiencing repeated errors in Win 8.1 system event viewer related to amdkmdap and monblanking. The timing seems to coincide with logons to gotomypc. Does anyone else experience this?

Find more posts tagged with

Comments

leslie colston

If you look in eventvwr.msc, it only happens when gotomypc is hit. This has happened to me 2 different weekends resulting in auto reboots. Unfortunately, the last one resulted in, and my error, loss of about an hour's worth of work on Visio because I had failed to save and accidentally left file open Friday afternoon. I have been using G2P since like 2012 and never had a problem. I have disabled the monitor disable for now to hopefully avoid the problem.

Michael16

Leslie, you are experiencing crashing? These event viewer warnings alone shouldn't be the cause of any crashing. There might be another factor coming into play here; Specifically, the errors you are receiving might actually indicate an error with the monblanking driver being able to load and our hardware overlay is kicking-in, which is known to have compatibility issues with integrated Intel HD display adapters.

As for the new certificate, it will be rolled-out automatically in an updated version of the monblanking driver.

leslie colston

I'm @ the same build

David M11

Do you know which build/version will have this? I'm on 9.1 (1875) now.

leslie colston

I see you posted that there would be a new certificate. Will G2P automatically search and find the new certificate? My host computer has crashed 2 different times when logging in to it. I need this to work.....

Katie111

I'm looking forward to that.

Michael16

I have good news everyone: the errors are occurring because of an outdated certificate for the monblanking driver, and we will be shipping the new one out in future builds of G2P.

David M11

When I wake the monitor from sleep (computer doesn't sleep) I get 3 of these Event 104 errors for Video5, Video4 & Video3 (my PC has a separate video card so there are 2 DP ports on it, plus 2 on the motherboard and 1 VGA). I get the same Event 104 from nvlddmkm for Video0 and Video1. I also get 4 Event 104 from monblanking, posted below.

Log Name:      System
Source:        igfx
Date:          08/06/2016 11:17:23 AM
Event ID:      104
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      mycomputer.company.com
Description:
The description for Event ID 104 from source igfx 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:

\Device\Video5
MonblankingDriver

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">;
<System>
    <Provider Name="igfx" />
    <EventID Qualifiers="32768">104</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-06T18:17:23.941075100Z" />
    <EventRecordID>7177</EventRecordID>
    <Channel>System</Channel>
    <Computer>mycomputer.company.com</Computer>
    <Security />
</System>
<EventData>
    <Data>\Device\Video5</Data>
    <Data>MonblankingDriver</Data>
    <Binary>0000040002003400000000006800008000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name:      System
Source:        monblanking
Date:          08/06/2016 11:17:23 AM
Event ID:      104
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      mycomputer.company.com
Description:
Someone sent a power request to display driver
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">;
<System>
    <Provider Name="monblanking" />
    <EventID Qualifiers="32768">104</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-06T18:17:23.941075100Z" />
    <EventRecordID>7174</EventRecordID>
    <Channel>System</Channel>
    <Computer>mycomputer.company.com</Computer>
    <Security />
</System>
<EventData>
    <Data>\Device\0000005d</Data>
    <Data>MonblankingDriver</Data>
    <Binary>0000040002003400000000006800008000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

Michael16

What specific error messages is everyone receiving? I'm having trouble finding the exact message, but if it's the one I think it is, it has to do with the driver being unable to communicate with the monitor. Installing specific model monitor drivers can fix all the extra messages, especially if Windows is using the generic PnP driver (generic non-PnP should work).

Katie111

Yes, sort of. I get a solid green screen and the only indication that anything is happening is the cursor moving around on it. Once the connection ends it reverts to normal.

David M11

If you don't have the service running, will the screen blank when you connect remotely?

Katie111

Since this has been the case for years with no action from them, my solution was to turn off the monblanking service in Windows using 'net stop monblanking' . I put this in a scheduled task to run at login. You'll also need to run this whenever you upgrade to a new version of GTMPC.

David M11

Same Issue in Windows10. Based on the information provided by GTMPC, this is my design so I think it should be changed from a warning event to an informational event.

Katie111

I have the same issue running version 8.4 (1704) on Win 7. When is this going to be fixed?

Otmer

Until this issue is fixed, is there a way to turn off these event log entries? Every time I check the logs on every host that I have GTMPC on I have to filter the logs to see the real errors in them. Every hour and a half 6 entries are logged (3 monblanking and 3 for the display driver

Kyle Halversen

Hi David,

GoToMyPC installs a monblanking driver that is used to blank out the screen. In the latest version of GoToMyPC (Version 8.3 Build 1611) the driver writes information into the Windows Event Viewer for diagnostic and troubleshooting purposes that we did not include with previous versions of GoToMyPC. Monblanking events tend to get logged when you have a GoToMyPC session with your computer and you have your GoToMyPC Preferences set to blank out your screen. They will also appear if you add or remove a display, install a driver, and may get logged during other display changes. Screen blanking related activity may also be triggering the driver of your computer's display to also log information in the Event Viewer.

While it is normal for information from monblanking to be present in the event viewer, if you'd like to post the description of the event log information, I may be able to provide an additional explanation. Although some events from the monblanking driver are labeled as "Warning" in the event type, not all of these messages are actually a cause for concern. We are aiming to reduce the amount of activity that our monblanking driver writes to the event viewer with the next release of GoToMyPC.

Quick Links

Join the conversation!

If you found this discussion useful, why not register/sign-in? It only takes a minute to share your feedback, ask a question, or vote for a new feature!