Windows 10: Event 16, The IOMMU fault reporting has been initialized

​

IOMMU or Input-Output Memory Management Unit, is a primary component in the Memory Management System of modern-day computing devices, responsible for handling memory management requests from hardware devices like Graphics cards, network interface cards, and storage controllers. If you are receiving Event 16, The IOMMU fault reporting has been initialized error in the Event log, […]

This article Event 16, The IOMMU fault reporting has been initialized first appeared on TheWindowsClub.com.

read more...

 

Iommu

Lets create list of motherboards that support iommu.
MSI 890XFA-D65 and D70 D65 requires custom bios from biso mods.

 

Event Viewer problem with latest Windows Build 1607

After installing the new Windows build 1607, the Event Viewer stopped recording events under Diagnostic Performance. (Before 1607 I checked the files located under Windows.old dated 9/23/2016 and located this file which indeed did have a list of events
recorded.)

Since the initial 1607 download there have been two new builds automatically installed on my laptop.



The last step in an automatic download is the RESTART. Prior to my rebooting, I checked the Diagnostic Performance and for sure, these had the list of events.



Rebooting by me, causes the Diagnostic Performance errors to disappear.

As suggested earlier I have run the SFC/DISM commands with no errors reported.

Any Ideas?

Nancy

 

Where are application error event reports placed?

I have an application (FahCore_a7.exe) failing. The event Windows log for the application failure shows:

Faulting application name: FahCore_a7.exe, version: 0.0.0.0, time stamp: 0x57e1e600
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x8274fd8b
Exception code: 0xc0000028
Fault offset: 0x0000000000004b90
Faulting process id: 0x4834
Faulting application start time: 0x01d342a962ca70b6
Faulting application path: C:\ProgramData\FAHClient\cores\fahwebx.stanford.ed u\cores\Win32\AMD64\AVX\Core_a7.fah\FahCore_a7.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: d137c9d5-7742-498c-84fe-e1d5a2042064
Faulting package full name:
Faulting package-relative application ID:


I would assume the report (id d137c9d5-7742-498c-84fe-e1d5a2042064) might tell me more.

Haven't gone down this road before so I'm pretty ignorant about how to trouble shot the problem.

Thanks for any help or suggestions!!