Windows 10: Hello, there is such a critical error in the event log. What to do? ERROR 293

DriverMessage: "[0926-07:40:59:891][PID:1256][TID:01868][GFDrv][fatal][tls_callback_send:00193] Goodix>>> sent ret:9."ANDDriverMessage: "[0926-07:40:59:822][PID:1256][TID:01344][GFDrv][warn][get_msg_data:05494] Goodix>>> MCU has no config"

:)

 

Error in Event Viewer

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned, you have performed a repair installation on the computer and you see Event 508, 510 and 533 in Event Viewer.



I would like to inform that if you see any critical error in Event Viewer, please share the event logs with us to help you with the appropriate troubleshooting steps. Please follow the steps mentioned below to share the event logs:

1. Press Windows + X from the keyboard, select
   Event Viewer.
   
2. Expand Windows Logs from the left pane and select
   Applications.
   
3. Click Filter Current Log from extreme right pane. Then in the new windows check the box beside
   Error and click OK.
   
4. Now, look for a critical Error in the list and note down the message/information from the
   General Tab in the lower section.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Persistent Blue Screen Errors with Timestamped Event Log Details

I've been grappling with persistent blue screen errors on my system, and to understand the root cause, I've been closely monitoring the Event Log Viewer. What's particularly concerning is that these errors seem to be occurring consistently at specific times. Here's a breakdown of the errors along with their corresponding timestamps:

11:56:10 AM

• Error: MSSQL$SQLEXPRESS (Event ID: 8317)
  

11:55:46 AM

• Error: DistributedCOM (Event ID: 10010)
  

11:53:52 AM

• Error: volmgr (Event ID: 45)
  
• Error: Eventlog (Event ID: 1101)
  
• Critical: Kernel-Power (Event ID: 41)
  

11:29:35 AM

• Error: MSSQL$SQLEXPRESS (Event ID: 8317)
  

11:27:14 AM

• Error: volmgr (Event ID: 45)
  

11:09:02 AM

• Error: MSSQL$SQLEXPRESS (Event ID: 8317)
  

10:58:30 AM

• Critical: WinREAgent (Event ID: 4502)
  

10:52:51 AM

• Error: MSSQL$SQLEXPRESS (Event ID: 8317)
  

10:52:34 AM

• Error: DistributedCOM (Event ID: 10010)
  

10:50:32 AM

• Error: volmgr (Event ID: 45)
  
• Critical: Kernel-Power (Event ID: 41)
  

10:44:44 AM

• Error: Volsnap (Event ID: 36)
  

This pattern suggests a systemic issue rather than isolated incidents. Despite my attempts at troubleshooting, these errors persist. Any insights into resolving these timestamped errors and mitigating the blue screen crashes would be immensely helpful. Thank you for your assistance!ry

 

Tons of event viewer errors, warnings and criticals!


Have you actually got troubles with the pc? If not don't you worry about so called critical errors listed in the event viewer. What MS understands as critical error should not be confused with what common sense would understand under that term, the MS definition of a critical error is much broader. Generally if there is no actual problem with the pc it's not worth bothering since I have not seen a single Windows pc that does not show a critical error here and there in the event viewer. The event viewer is a nice tool to troubleshoot but only for that. Checking it without actually having troubles with that specific pc is like running to a doctor and make him conduct countless test only because you might someday get some sort of cancer. If the pc is doing fine don't spoil that positive experience by looking for troubles where there are none.