ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Windows Event Error 56 and Skylake
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Windows Event Error 56 and Skylake

 Post Reply Post Reply Page  <123>
Author
Message
bezel View Drop Down
Newbie
Newbie


Joined: 25 Nov 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote bezel Quote  Post ReplyReply Direct Link To This Post Posted: 28 Nov 2015 at 2:47am
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
Back to Top
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Posted: 28 Nov 2015 at 5:06am
Having a USB driver or device causing crashes and in conflict is not uncommon. You do not say whether the USB 2.0 port is on your motherboard or an add-in card.
Regardless you can go into your device manager locate your usb 2.0 hub driver and right click to get properties, go top power management tab and unclick "Allow the computer to turn off this device to save power" Click on OK, and see if that does anything.
Secondly since it may not have caused problem previously, under Driver Tab in Properties of of the usb 2.0 hub try roll back driver if available.
Lastly is to uninstall the usb 2.0 driver under the same driver tab and then let windows reinstall the appropriate driver.

Back to Top
wardog View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 15 Jul 2015
Location: Retired in AZ
Status: Offline
Points: 4051
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 28 Nov 2015 at 2:35pm
@ PainterArt and bezel

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

I wonder ....
< id="kpm_plugin" ="application/x-KPMPlugin">
Back to Top
bezel View Drop Down
Newbie
Newbie


Joined: 25 Nov 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote bezel Quote  Post ReplyReply Direct Link To This Post Posted: 28 Nov 2015 at 7:42pm
@wardog
Yes I know that. I have the 2.10 BIOS and latest drivers & INF installed.

@PainterArt
As for USB drivers ,Win10 installed all of them (2.0/3.0/3.1) I did not install any other USB drivers.
I have Asrock z170 Extreme+ and I am using only mobo ports. Now I remember that after checking different ports and not using 2.0 I still got a crash so maybe its just a coincidence with updating Win10 to build 10586. Still didn't had time to run some game and see if it's fixed. But since the update when idle/web browsing/youtube @1080p60 there were no crash so it's looking good.

I'll post when done with testing.     
Back to Top
PainterArt View Drop Down
Newbie
Newbie


Joined: 31 Oct 2015
Status: Offline
Points: 13
Post Options Post Options   Thanks (0) Thanks(0)   Quote PainterArt Quote  Post ReplyReply Direct Link To This Post Posted: 29 Nov 2015 at 2:42am
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.

Back to Top
bitpicker View Drop Down
Newbie
Newbie
Avatar

Joined: 31 Mar 2016
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote bitpicker Quote  Post ReplyReply Direct Link To This Post Posted: 31 Mar 2016 at 10:41am
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 the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
ACPI
5
the message resource is present but the message is not found in the string/message table.

Still getting this error from day 1 at every boot. I'm on a Win 10 x64 system with i7-6700K, 16GB G.Skill TridentZ DDR4 3200, ASRock Z170 Extreme4, Msi GTX960 4G, Corsair CX 600WM and Samsung 951 256G m.2 AHCI PCIe x4 (system), HDD internal and 2 externals on USB3.0, BD-RE... the usual.

The working CPU temperature is normal, I OC to 4.4 once with excellent stability. At default the RAM isn't correctly configured, but adding the XMP profile DDR4 3200 16-16-16-36 does it. In Windows all the devices are recognized and configured. I didn't update Windows still (disconnected), but I've flashed the BIOS to the latest firmware 2.90. Windows never crashed on me although I experience short PC freezes only in the BIOS, but it always comes back. 
Disabling the CPU C states in the BIOS or disabling and/or uninstalling Realtek Audio drivers in Windows, won't do the job. The Error event ID 56 still persist. 

I haven't tried playing with the Voltage yet. Can anyone elaborate further on how to go about increasing the CPU voltage?

Is there a solution to this issue as of today?

I'm reading worrying opinions about the Skylake CPU being defective and such... Can anyone shed some light on this very recurring problem, it seems.


Edited by bitpicker - 31 Mar 2016 at 11:12am
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 3479
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 31 Mar 2016 at 12:51pm
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? Confused  LOL

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.



Back to Top
bitpicker View Drop Down
Newbie
Newbie
Avatar

Joined: 31 Mar 2016
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote bitpicker Quote  Post ReplyReply Direct Link To This Post Posted: 31 Mar 2016 at 3:50pm
Thanks for the reply Parsec. I will point out that it isn't circumscribed to Windows 10 and it also effects non-Skylake CPUs and ASUS MoBo. It has been found in Windows 7 where apparently the event viewer gives a tiny bit more info:

Driver ACPI returned invalid ID for child service(5)

I've always tried to set up the CPU Voltage through the BIOS OC Tweaker/Volt Configuration, but the offset mode is a tad counterintuitive to me and I didn't wanted to go all out with the fixed mode. However using the ASRock A-Tuning the information about the CPU is very clear. With everything on "Auto" in the Volt Configuration I'm running a Vcore around 0.800 V. It seems well under-clocked!

I have been shying out of OC thus far, but I will experiment now and report about this ID 56 issue. I was frustrated when the BIOS upgrade didn't seem to help, so my only chance to a fix resides in CPU voltage tweak. Somehow.

On windows forums there a discussion started last summer that has reached 17 pages so far, but nobody has a solution yet. I read of some users that finally got ridden of it, but they don't know how that really happened (!). Here's the link:
https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-event-id-56/aed11fed-4475-4a9a-ad87-4320200dc160


Back to Top
bitpicker View Drop Down
Newbie
Newbie
Avatar

Joined: 31 Mar 2016
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote bitpicker Quote  Post ReplyReply Direct Link To This Post Posted: 31 Mar 2016 at 5:34pm
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.

The event ID 56 persisted though.

I'll try OC more later. 
Back to Top
ASRock_TSD View Drop Down
ASRock_Official
ASRock_Official


Joined: 20 Mar 2015
Status: Offline
Points: 1182
Post Options Post Options   Thanks (0) Thanks(0)   Quote ASRock_TSD Quote  Post ReplyReply Direct Link To This Post Posted: 08 Apr 2016 at 12:17pm
Dear All,
This is ASRock Technical Support Department.


Regarding the Event ID 56 issue, the issue is a common issue on Windows 10 which mean it will happen on all Skylake platform. (However it's not 100% that everyone will meet it)
Please refer the Microsoft official community thread : http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-event-id-56/aed11fed-4475-4a9a-ad87-4320200dc160?auth=1

Although there seems no critical issue with the Event ID 56, we still have a solution for it.
And now we are updating the BIOS for all platforms, we will release them to the website ASAP.

Thank you for your patience.
If any, please feel free to contact us!

Kindest Regards,
ASRock TSD 
Back to Top
 Post Reply Post Reply Page  <123>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.06
Copyright ©2001-2016 Web Wiz Ltd.

This page was generated in 0.109 seconds.