Windows Event Error 56 and Skylake

Thank You for replying.

I'm not sure but i think it was stable after fresh install of W10 for couple of days than i did some updates. Later I read somewhere that the crashes might be caused by one of the updates so I uninstalled all of them but it didn't fixed it. Yesterday I noticed that my build was 10240 but WU was not finding any new updates. After googling I learned that after uninstalling updates you have to download the installer from microsoft software download site and update through that. So I did that and now I'm at build 10586 with all updates. So far no crash but I didn't run any game yet because of lack of time. Also I remember that couple of hours before resolving my error ID 19 i tried unplugging every thing and plugging it back ,trying different ports. It ended with everything plugged to usb 3/3.1 ports and not using usb 2.0 ports after that some hours later I found this thread and did as advised ,raised the vcore. With all the enthusiasm that there are no ID 19 errors I started doing stress tests ,playing game for almost three hours and no crash. Then after playing I did some OC & some stress tests. I thought the problem is solved so I've plugged everything back to usb ports how it was before solving the ID19 error. By that i mean ,mouse & keyboard to usb 2.0 ports and the rest to 3.0/3.1 ports. Next day I turned on the pc and started playing and it crashed after hour or so. Now I dont use the usb 2.0 and so far so good. I don't know if the usb ports are related or if it was the Win Update ,maybe it is just some coincidence. This time I will hold my enthusiasm and after doing some gaming will report back.

Anyway thanks PainterArt for responding and trying to help! I appreciate it.    


Edited by bezel - 28 Nov 2015 at 2:49am

@ PainterArt and bezel

Since BIOS 2.10 updated the ME, shouldn't updated drivers and INF be installed ?

I wonder ....

Device Drivers as OS software specific. A bios does not install device drivers. The OS does.

USB drivers and devices can conflict with other drivers or vice a versa. It is not unusual with USB problems. The problem is it can also be other things or happen sporadically. Some other install is probably the reason for a USB device driver problem.

The easiest way to view a crash dump file is with Blue Screen View (free) http://nirsoft.net/utils/blue_screen_view.html
You have to the dump file enabled. More information is on the link webpage. The possible driver problem will be highlighted in pink.
Lots of other great small utilities a nirsoft also see what is hanging for programs that freeze.

My Z170 board's Windows 10 installation is running fine, and I would not have even bothered looking into this "error" if I had not seen this thread.

Personally, I have seven entries with the 56 Event ID, over the past nine days of saved Event Log entries.

Let's look at this "error" one more time...

The description for Event ID 56 from source Application Popup 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 you look through your Event logs, the majority of entries are of the Level Informational. When you highlight an Event, at the bottom of the Event Viewer screen we see the General and Details tabs. The text shown for the General tab for an event is called the Description for an Event ID.

For example, for Event ID 98, this is the Description that appears related to my PC:

Volume C: (\Device\HarddiskVolume4) is healthy.  No action is needed.

Now back to the "error" message for Event ID 56. The description (the text describing the Event) cannot be found.

The error is the text associated with Event ID 56 (whatever that is) cannot be found.

Frankly, I would expect the event whose ID is 56, would be logged as occurring if it was of significance, even if it does not have a description. But apparently the fact that the description for Event ID 56 is missing, causes the message resource description missing error text to be used in place of the actual event description text.

So is this simply the Event ID 56 Event Log entry with the missing description text error in place of the true description text? Or is the entry simply an error message that the description text of Event ID 56 is missing?  

Application Popup is the source of Event 56, whatever this event is. Microsoft cannot tell us what Application Popup is?

We also know, "the message resource is present but the message is not found in the string/message table".

Whomever designed Application Popup, create a message resource for event ID 56 that is related to it, so it would be displayed in Event Viewer, but the description text is missing from the message resource. The message resource is data about the event, which is used by the Event monitoring system.

So again, the "error" here is the description of Event ID 56 from the source Application Popup cannot be found in the string/message table of the message resource.

If we give Microsoft the sentence above, I imagine that any qualified Microsoft software engineer would be able to tell us more about this situation.

Unfortunately, I doubt that Windows 10 is able to log events that occur when the UEFI/BIOS UI is running, as useful as that would be.

I've overclocked through the BIOS the Vcore voltage by setting the Offset Mode in the OC Tweaker to 160 mV reaching 1312V in the BIOS and peaking 992 in A-Tuning on system idle. Only an increased temperature of 5C.