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 Search  Events   Register Register  Login Login

Windows Event Error 56 and Skylake
 Post Reply Post Reply Page  123>
Author
Message Reverse Sort Order
  Topic Search Topic Search  Topic Options Topic Options
tlawr View Drop Down
Newbie
Newbie


Joined: 16 Sep 2016
Status: Offline
Points: 1 		Post Options Post Options   Thanks (0) Thanks(0)   Quote tlawr Quote  Post ReplyReply Direct Link To This Post Topic: Windows Event Error 56 and Skylake
    Posted: 16 Sep 2016 at 1:17pm
Hi!

I'm using the ASRock H110M-HDV motherboard. (Pentium G4500 Windows7 64bit)

I have 2 errors when Windows startup on BIOS 1.50.

  Event 56, Application popup
       "Driver ACPI returned invalid ID for a child device (1)."
       "Driver ACPI returned invalid ID for a child device (5)."

When I've updated BIOS from 1.50 to 1.90, "Driver ACPI returned invalid ID for a child device (5)." disappears, but
"Driver ACPI returned invalid ID for a child device (1)." still remains.

If possible, please fix in the next version up.

thank you.
Back to Top
Pr0digy View Drop Down
Newbie
Newbie
Avatar

Joined: 31 May 2016
Location: Denver
Status: Offline
Points: 1 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Pr0digy Quote  Post ReplyReply Direct Link To This Post Posted: 31 May 2016 at 11:28pm
Just wanted to check to see if plans are in place for this fix to make it to the Z170 Fatality i7 Pro gaming board?

Thanks!
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: 27 May 2016 at 1:26pm
I've updated to the BIOS release 3.20 5/5/2016 - on a ASRock Z170 Extreme4 - and the error ID 56 has gone for good, while the release 2.90 didn't solve it earlier on.

I've noticed in the Boot menu the CSM (Compatibility Support Module) has been deprecated. I used to set <Launch Storage OpROM Policy> to <UEFI only> to make sure the M.2 SSD would boot, but I take it isn't necessary anymore as the compatibility had been expanded natively. Right?
On the download page http://www.asrock.com/mb/Intel/Z170%20Extreme4/?cat=Download&os=BIOS
I'm reading:
1.Update NTFS module.
2.Support 4K native HDD

Back to work now. Thank you to ASRock staff for the fix.


Edited by bitpicker - 27 May 2016 at 1:27pm
Back to Top
invasmani View Drop Down
Newbie
Newbie


Joined: 28 Apr 2016
Status: Offline
Points: 3 		Post Options Post Options   Thanks (0) Thanks(0)   Quote invasmani Quote  Post ReplyReply Direct Link To This Post Posted: 13 May 2016 at 5:31am
Not sure isn't event ID 56 tied to ReadyBoot not being set in log mode circular and the max file size being reached triggering it as a result or is that a separate unrelated event viewer issue?

Bios 3.30 also doesn't have the 76 microcode so flashing it if you skip bios 3.10 at least still allows for SkyOC, but seems ot run 73 microcode rather than 74 microcode that bios 3.00 ran.  On the plus side the bios itself has a few minor differences. If bios 3.30 is indeed a fix it's probably worth flashing to even for those wishing to retain the SkyOC feature. For me atm event ID 56 isn't showing up, but idk if it's due to bios 3.30 or something else I tweaked with the OS itself.


Edited by invasmani - 13 May 2016 at 5:32am
Back to Top
invasmani View Drop Down
Newbie
Newbie


Joined: 28 Apr 2016
Status: Offline
Points: 3 		Post Options Post Options   Thanks (0) Thanks(0)   Quote invasmani Quote  Post ReplyReply Direct Link To This Post Posted: 28 Apr 2016 at 1:09pm
Originally posted by parsec parsec wrote:

The other possibility for a UEFI/BIOS fix is one I won't mention.
I won't "leap ahead" and mention names or point fingers at your evil friend Grintel, but "it's what's inside that counts" like "the next big idea is inside" you like that microcode bug that deliberately prevents any possibility of a stable overclock ever again w/o buying artificially cost inflated unlocked CPU for OCing lets just release every non OC CPU flawed from the start and rule out that possibility entirely! LOLClap Bravo Intel you make us all savor the day AMD releases something anything at all to make us consider them a viable alternative.
Back to Top
urbancamper View Drop Down
Newbie
Newbie


Joined: 12 Apr 2016
Status: Offline
Points: 9 		Post Options Post Options   Thanks (0) Thanks(0)   Quote urbancamper Quote  Post ReplyReply Direct Link To This Post Posted: 25 Apr 2016 at 9:22pm
I was getting the event 56 popup error as well on my i5 6600k on an AsRock z170 pro4s mb, Windows 7 Sp1 os. That is until this morning. New bios for that board 3.30 has changed that. i now get 0 errors on startup. 

I would venture a guess that if they are not out yet, bios for most, if not all boards will be getting an update to solve this problem. Nice job AsRock. 

Now if you could just solve my not wake from sleep issue.(not really a big deal)


Edited by urbancamper - 25 Apr 2016 at 9:23pm
Back to Top
jameswhit View Drop Down
Newbie
Newbie


Joined: 25 Apr 2016
Status: Offline
Points: 1 		Post Options Post Options   Thanks (0) Thanks(0)   Quote jameswhit Quote  Post ReplyReply Direct Link To This Post Posted: 25 Apr 2016 at 4:51pm
Hi!
You need to nalyse the Event Error log. You can use the Advanced Filtering methods of Event Log Explorer for the mentioned Event Description and filter the events by Event Description. ad this http://eventlogxp.com/blog/advanced-filtering-how-to-filter-events-by-event-descriptions/. 
Back to Top
Vladimir View Drop Down
Newbie
Newbie
Avatar

Joined: 19 Apr 2016
Location: Russia
Status: Offline
Points: 1 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Vladimir Quote  Post ReplyReply Direct Link To This Post Posted: 19 Apr 2016 at 4:42am
I confirm it. I have my new PC-build:
asrock z170 pro4s
intel i-5 6500 
16 gb ddr4  (4x4gb Corsair Vengeance LPX CMK16GX4M4A2400C14) 
ASUS GTX 950  Strix (2 GB)
 Similar problem (freezing PC, and reboot only by hard reset) was present both in W7, and W10. At present i'm using W10, on every startup I have two errors:

1. 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
1

the message resource is present but the message is not found in the string/message table
2. 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 

And I notice that crashing PC usually(not always) take place after this errors.

PC. Sorry for my horrible english. 


Edited by Vladimir - 19 Apr 2016 at 4:57pm
Contact mail: maksimovzioc@gmail.com
Back to Top
urbancamper View Drop Down
Newbie
Newbie


Joined: 12 Apr 2016
Status: Offline
Points: 9 		Post Options Post Options   Thanks (0) Thanks(0)   Quote urbancamper Quote  Post ReplyReply Direct Link To This Post Posted: 12 Apr 2016 at 5:18am
This is not just happening with Windows 10. I have a similar problem with my new Windows 7 Skylake build. A modest budget build. 15 6600k / Asrock Z170 PRO4S / 8gb GSkill ddr4 2400. 

The error on startup: Event 56, Application popup / Driver ACPI returned invalid ID for a child device.  

i first noticed it it after the computer froze playing BF4. On restart the above error showed up. Also on every restart since. It may be related to the other problem I have. The computer does not wake from sleep state without pressing the power button down till it shuts off. Then pressing it again and it wakes, bypassing my password. 

I don't know anything for sure here. This is a new build. I have not done any overclocking on it. 

I posted this here because i noticed others are having event 56 errors.
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996 		Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 08 Apr 2016 at 1:21pm
Originally posted by bitpicker bitpicker wrote:

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. 


Why do you think this error 56 is related to over clocking?

I recently reset all the UEFI options to their defaults, reset the basic things I need (RAID, CSM, video card not IGP, etc) with zero changes to the OC Tweaker settings, except setting CPU Ratio to Per Core, which sets the multipliers to the stock Intel values for my processor. That removes the Multi-Core Enhancement option, so there is nothing at all that is in any way an over clocking setting.

Do I still see a few ID 56 events? Sure.

Can anyone in this thread correlate a problem they have in Windows with event ID 56?

I can't because I don't have any problems in Windows.

While IMO that thread in the MSoft Community forum is a mess, at least it seems accepted that this "issue" is not unique to one mother board manufacture. I'm also surprised that MSoft would allow that thread to go on as long as it has without some definitive information from them about this.

So a UEFI/BIOS update is the fix for this situation? That implies that this message is being created accidentally by some process. The other possibility for a UEFI/BIOS fix is one I won't mention.
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 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.109 seconds.