z170 OC Formula Event Viewer Error
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=1717
Printed Date: 04 Jun 2025 at 11:55pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: z170 OC Formula Event Viewer Error
Posted By: MikeGamerGuy
Subject: z170 OC Formula Event Viewer Error
Date Posted: 12 Jan 2016 at 10:40am
|
I've got an event viewer error occuring on every boot, and it has been occuring since before I installed any graphics card. The log shows it occured for the first time before I even typed my computer's name during the Windows 7 x64 install. and I don't know whether to ignore it or not. No crash seems to be associated with it. Background information. I am RMA'ing a EVGA 980Ti FTW because it is faulty, crashing in Farcry 4 randomly (event viewer showing a TDR referencing nvlddmkm). It also failed EVGA OC Scanner X's PhysX 3 Fluid GPU test with the the same file referenced saying the hardware was not installed or the installation was corrupted. My EVGA 970 FTW performs just fine, though I have not played games extensively with it installed in this system yet. I've installed, uninstalled, and reinstalled all the latest drivers a couple of times now. At the behest of Asrock tech support, and against my instincts, I stuck the driver CD in and let it install whatever it wanted. I then went about reinstalling all the latest drivers manually after that didn't resolve the event viewer error. I've run passmark's Memtest 86 in UEFI mode and passed all tests. I've run Folding at Home for hours and hours and the system is stable, with only a couple "true" early_unit_end's occuring for the same project number 10xxx on the CPU slot with the core status 72 (114). After investigating that, they could just be normal since there were no machine instability messages. Prime 95 is stable, but I haven't run a marathon of tests with it yet. Temps are good. That concludes the backstory. :) https://pchound.com/cZUHVW/" rel="nofollow - PC Hound Part List - i7 Skylake/980 Ti/OC Build CPU: https://pchound.com/1324330/intel-core-i7-6700k-8m/" rel="nofollow - Intel Core i7-6700K 8M ($420 - Custom) Motherboard: https://pchound.com/1337466/asrock-z170-oc-formula/" rel="nofollow - ASRock Z170 OC Formula ($238 - Custom) Memory: https://pchound.com/1338313/corsair-16gb-2-x-8gb-vengeance-lpx/" rel="nofollow - CORSAIR 16GB (2 x 8GB) Vengeance LPX ($125 - Custom) Video Card: https://pchound.com/1339346/evga-geforce-gtx-980-ti-06g-p4-4996-kr/" rel="nofollow - EVGA GeForce GTX 980 Ti 06G-P4-4996-KR ($640 - Custom) Power Supply: https://pchound.com/1220391/evga-850w-220-g2-0850-xr/" rel="nofollow - EVGA 850W 220-G2-0850-XR ($110 - Custom) Storage: https://pchound.com/930123/wd-1tb-black-series-wd1003fzex/" rel="nofollow - WD 1TB BLACK SERIES WD1003FZEX ($75 - Custom) Storage #2: https://pchound.com/974214/samsung-500gb-850-evo-mz-75e500bam/" rel="nofollow - SAMSUNG 500GB 850 EVO MZ-75E500B/AM ($155 - Custom) Case: https://pchound.com/448114/nzxt-phantom-820-series-ca-ph820-g1-820/" rel="nofollow - NZXT Phantom 820 Series CA-PH820-G1 820 ($235 - Custom) CPU Cooler: https://pchound.com/441286/noctua-nh-d15/" rel="nofollow - Noctua NH-D15 ($90 - Custom) Optical Drive: https://pchound.com/1233436/asus-drw-24b1stblkbas/" rel="nofollow - ASUS DRW-24B1ST/BLK/B/AS ($20.38 - Custom) Total: $2,108.38 Price may include shipping, rebates, promotions, and tax Generated by https://pchound.com" rel="nofollow - PC Hound TLDR: This event viewer error occurs every time the system boots: Event 56, Application Popup Driver ACPI returned invalid ID for a child device (5). No crashes seem to be associated with this error. Ignore or keep investigating?
|
Replies:
Posted By: MikeGamerGuy
Date Posted: 12 Jan 2016 at 3:00pm
| Asrock tech support told me to exchange the board since the driver CD didn't fix it. Not sure if something was lost in translation when I was trying to explain things or not. Since I literally have no idea what child device (5) means, I'm just going to unhook everything I can from the MB and see if it goes away. Then I'll install windows on a different ssd and see if it goes away. I've already started the RMA with newegg though. |
Posted By: wardog
Date Posted: 12 Jan 2016 at 4:44pm
|
Mike, when you installed the drivers for the board did you d/l ALL of the latest from the boards ASRock page or did you use the included Support CD? |
Posted By: wardog
Date Posted: 12 Jan 2016 at 4:49pm
|
Also, more importantly, is your board running the latest NON-Beta BIOS release? |
Posted By: wardog
Date Posted: 12 Jan 2016 at 5:10pm
In doing some Googling, it appears that when you update your BIOS doing so should fix this: See Dean_peps reply of OCT 10 2015, where he posts a response from ASUS he received http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-event-id-56/aed11fed-4475-4a9a-ad87-4320200dc160?page=4" rel="nofollow - http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-event-id-56/aed11fed-4475-4a9a-ad87-4320200dc160?page=4 |
wardog wrote:Posted By: MikeGamerGuy
Date Posted: 12 Jan 2016 at 5:41pm
| Latest bios. Just did a clean reinstall of windows 7. The error still popped up. I've tried it both ways now. The first time I installed all the latest drivers from asrock's download site. Tech support had me run the support disk on top of that. I reinstalled windows tonight and just ran the support disk and the same thing occurred. I'm installing windows on different SSD now to rule out the SSD. I've built a few systems before this one. This one has been days of, you know, tediousness. My video card was definitely bad. The motherboard came with an invalid MAC address. I should have just sent it back then instead of fixing it, but then I wouldn't have found out the 980ti was bad until later. So far I've managed to unplug or swap out everything connected to the motherboard other than the CPU. If this install is bad I guess I'll just chalk it all up to horrible luck. |
Posted By: wardog
Date Posted: 12 Jan 2016 at 6:28pm
|
For what you've dealt with there, heck yea, return it. Do you have any !'s in Device Manager by chance? Like a missing ACPI driver? If you do, PM me and I'll direct you if you don't have an idea what I'm discussing. BRB in about an hour. Have to go and start Wifeys truck and shovel. |
Posted By: MikeGamerGuy
Date Posted: 12 Jan 2016 at 6:53pm
| No problems in device manager. I'm giving up. It's either the processor or the motherboard, or something like an unsupported feature that the asrock tech doesn't know about. He told me to send it back so I'm gonna send it back, because if I don't, I know I'm going to regret it. Thanks for trying guys. |
Posted By: Xaltar
Date Posted: 12 Jan 2016 at 7:25pm
|
That error is fairly common with the GTX 9xx series and could stem from quite a few sources. The most common source is drivers followed by a defective GPU followed by power problems. If it is driver related then performing a fresh install as you say you did should have corrected it, another option is to use DDU and uninstall from safe mode and try a few different driver versions and see if that clears the issue. The error also occurs fairly frequently on factory overclocked GPUs that for one reason or another are not stable at their factory overclock. Loading MSI afterburner and dropping the clocks to stock or lower will clear the issue in a case like this. RMA the GPU if this works. Another GPU fault is inadequate power getting to the GPU. There are 2 things you can try here: 1. Set "Power management mode" in Nvidia control panel to "prefer best performance" instead of "adaptive". This has corrected the issue for many users. 2. If that still does not work then use MSI Afterburner and set "Power limit" to about 70% and test for TDRs. If this works then the issue is due to a power problem, either in the GPUs power system or the power going to the GPU is unstable or inadequate. Inadequate/unstable power could be caused either by an unstable PSU/poor connection or, an issue with the motherboard not providing enough power to the PCIe slot. Be sure you have both the 8 and 4 pin connectors on your motherboard connected and that they are properly seated. If after all this you still have the issue then sending back the board is the only remaining option.
|
Posted By: MikeGamerGuy
Date Posted: 12 Jan 2016 at 8:35pm
| It occurred initially without a graphics card even being installed. All good tips though, thanks. |
Posted By: wardog
Date Posted: 12 Jan 2016 at 9:26pm
Yeppers. In a box, add a mailer sticker and BuhBye. Best shots are best shots. The trick is knowing when to give up. Give up way way before you end up bald up top. I'm living proof I do not follow my own advice, just ask my Wife. She'll tell ya all the late nighters I've spent :) Hopefully you have better luck with whatever your next one is |
Posted By: Xaltar
Date Posted: 12 Jan 2016 at 11:03pm
I see, in that case RMA is the best option. As Wardog said, there comes a time to just throw in the towel and send it back before it drives you completely insane/bald
 |
Posted By: MikeGamerGuy
Date Posted: 28 Jan 2016 at 5:03pm
|
I'm back. I have the same error on the new motherboard. Apparently it's a widespread error in the z170 chipset, not brand specific. http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-event-id-56/aed11fed-4475-4a9a-ad87-4320200dc160?page=1" rel="nofollow - Source thread here. I'll read it more thoroughly for tip tomorrow I guess. And I also found this article about a http://arstechnica.com/gadgets/2016/01/intel-skylake-bug-causes-pcs-to-freeze-during-complex-workloads/" rel="nofollow - confirmed bug that will require a bios update in Skylake processors... hooray /sarcasm. Hopefully someone else doesn't waste a week waiting on a new motherboard like I did. :)
|
Posted By: wardog
Date Posted: 28 Jan 2016 at 6:47pm
|
The "confirmed bug" link/error has already been patched. Intel last week released a BIOS patch for all Skylake boards to ALL the manufacturers to incorporate into a new BIOS. For your Z170 OC Formula this updated BIOS, P2.10, can be found in your boards BIOS Downloads now. ""1.Update microcode to 0x74."" represents the BIOS ASRock incorporated the 'data' Intel supplied them. |