Windows 10: event log warning

hello, im having this warning every 0.5 sec. its a new computer.. source: WHEA LOGGERevent id 17A corrected hardware error has occurred.Component: PCI Express Root PortError Source: Advanced Error Reporting PCI ExpressPrimary Busevice:Function: 0x0:0x6:0x0Secondary Busevice:Function: 0x0:0x0:0x0Primary Device NameCI\VEN_8086&DEV_A74D&SUBSYS_00000000&REV_01Secondary Device Name:should I ignore it ? thanks :

:)

 

warnings and errors in event log

On both of my computers that are running Windows 11 I have found numerous warnings and errors in the event log. Has anyone else experienced this and do I need to be concerned.

 

Isn't it a bug in windows event log? TypesSupported dosnt work!

Hello ,

Good to see you in Microsoft Community.

If you want to configure the Windows event log to write only error, warning, or failure messages into log files, you can try the following steps:

HLM\SYSTEM\CurrentControlSet\Services\EventLog\TypesSupported is a parameter in the Windows registry used to configure event log levels. It determines which event levels should be logged. Before setting this parameter, it is necessary to understand the values and meanings associated with it:

• 0x00000001: Indicates that the Critical level of the event log should be logged.
  
• 0x00000002: Indicates that the Error level of the event log should be logged.
  
• 0x00000004: Indicates that the Warning level of the event log should be logged.
  
• 0x00000008: Indicates that the Information level of the event log should be logged.
  
• 0x00000010: Indicates that the Verbose level of the event log should be logged.
  
• 0x00000020: Indicates that the Audit Success level of the event log should be logged.
  
• 0x00000040: Indicates that the Audit Failure level of the event log should be logged.
  

To make Windows Event Viewer only log Warning, Error and Audit Failure level logs, follow these steps:

1. Open the Registry Editor and navigate to the follow path
   
   
   
   
   
   
2. Find the TypesSupported item corresponding to the appropriate event log level respectively, and modify its DWORD value data to 0x00000046, which is 0x00000002 + 0x00000004+ 0x00000040.
   
3. Save the changes and close the Registry Editor.
   
   Disclaimer: Generally, modifying registry subkeys or workgroups is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows (microsoft.com) to view the article.
   

If anything is unclear, please do not hesitate to let me know.

Best Regards,

| Microsoft Community Support Specialist

 

ESENT Event ID 508,510 and 533 warnings in Event Viewer

Hello Summez,

We appreciate the time and effort you have put in to resolve the issue.

If the ESENT Event Ids have stopped logging in Event Viewer, we might be looking at a positive picture here. Also, certain Windows components were fixed after running SFC and DISM tools.

However, if you still see any issues, I suggest you to check if the same issue occur when logged in through a different Local Administrator user account.



Follow the steps mentioned below:

• Assuming that you are already logged on to your user account in Windows 10, click the Start button.
• From the Start menu, click your name from the top of the left pane.
• From the displayed options click Sign out.
• From the login screen, click to the different user account you want to switch to.

However, if you do not have a separate user account, I suggest you to create another Local administrator user account by referring to the Microsoft article here: Set
up accounts.

Write to us again, in case you need further assistance on the issue.

Thank You.