Windows 10: Session "PerfDiag Logger" stopped due to the following error: 0xC0000188

I am trying to debug a very slow login 1.5 minutes after typing in my PIN on Windows 10 x64 Pro after the May 2020 automatic Windows update. Previously, Windows would log in 10 or 15 seconds. But now, the spinner loop spins for 1.5+ minutes before showing me my wallpaper. And even then, it's another full minute before it shows the desktop icons so I can do anything.


It's a newly built machine, only a few months old. Therefore, I think all the drivers are up to date. I updated my GeForce driver anyway.


I started with this error in the event log:


Session "PerfDiag Logger" stopped due to the following error: 0xC0000188


I see 1 in February, 4 in March, 2 in April, 3 in May, and 4 in June in only two days!.


I searched the net for the error, but could not find anything. Is there someone on this forum who can tell me how to fix this error?

:)

 

"Circular Kernel Context Logger" stopped due to the following error

Perhaps:
Fix: Session Stopped Due to the Following Error 0xc0000188 - Appuals.com

may help.

 

Session "PerfDiag Logger" failed to start error: 0xC0000035 Event ID 2

Not Alone same issue, then followed by
event id 3 Session "PerfDiag Logger" stopped due to the following error: 0xC0000188
and
event id 4 The maximum file size for session "PerfDiag Logger" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\system32\WDI\LogFiles\ShutdownPerfDiagLogger.etl". The maximum files size is currently set to 26214400 bytes.
I was able to increase the bytes. But still get event id 2, 3, 4, I guess they are all related

Needless to say DISM tool clean bill of health and sfc scannow no errors

Holding my breath for solution Dis user

 

BSOD: session "eventlog-airspacechannel" stopped due to the following error: 0xc0000188

My PC went to sleep mode after 10 min and woke up while crashing
(BSOD) and creating a memory dump.

I could trace the crash to this event : session "eventlog-airspacechannel" stopped due to the following error: 0xc0000188.

It seems to be related to an eventlog as set by the Performance monitor (see this

The fix suggested in that post, is to set the Log mode to "circular"(see picture)





My questions are:

• How can an event log crash my system?
• Why do I need to log this event in the first place? Can I disable it?

My specs: Windows 10 pro 64-bit version 1703 (build 15063.250) with Office 2010.

Not sure if it should be posted here, instead of TechNet, but I give it a try here, first.

Cheers,

Dave