Здравствуйте.
Перед Новым годом установил на ПК новый SSD (Goodram Iridium Pro), а вместе с этим в голове родилась идея установки долгожданной Windows 10 x64 (Корпоративная). Терабайтный жёсткий диск, разумеется, решил использовать для файлов.
На первый взгляд, всё было бы хорошо, если бы не одно НО. При нажатии на кнопку завершения работы, компьютер иногда выключался, а иногда перезагружался. Перечитав форумы, я настроил электропитание в ПУ, накатил последние обновления Windows, обновил BIOS, обновил драйверы, а также поменял значение в ветке: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\ReadyBoot на «4».
Теперь при нажатии кнопки выключения, компьютер выключается, но недавно в журнале ошибок Windows увидел ежедневную ошибку: Сеанс «ReadyBoot» остановлен из-за следующей ошибки: 0xC0000188
- System
- Provider
[ Name] Microsoft-Windows-Kernel-EventTracing
[ Guid] {B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}
EventID 3
Version 1
Level 2
Task 2
Opcode 14
Keywords 0x8000000000000010
- TimeCreated
[ SystemTime] 2017-01-05T10:39:11.649771400Z
EventRecordID 159
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 176
Channel Microsoft-Windows-Kernel-EventTracing/Admin
Computer pc-pavel
- Security
[ UserID] S-1-5-18
- EventData
SessionName ReadyBoot
FileName C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl
ErrorCode 3221225864
LoggingMode 276824064
FailureReason 0
Может быть кто-то с подобным уже сталкивался? Буду рад помощи от профессионалов! 
Currently, you are facing a delay in starting the PC. For so, whenever you have checked the Event Viewer, it is showing the message that ‘Session “PerfDiag Logger” stopped due to the following error: 0xC0000188′.
This is an OS (Operating System) component issue that commonly arises for some anonymous reasons. And if you are facing the same, you’re not alone. We’re here to help you.
You can easily solve this issue. In fact, I am writing this article to assist you fix the issue. Let’s explore this in details below.
Whenever the issue happens, you can apply a couple of things to fix it. Before diving into the details, let’s check the list of fixes first.
- Fix 1: Enable Superfetch Service
- Fix 2: Run DISM Health Scan
- Fix 3: Maximize Startup Event Trace Sessions File Size
- Fix 4: Recreate ‘setup.etl’ File
- Fix 5: Execute A Clean Boot
Fix 1: Enable Superfetch Service
When you face the issue, you can enable the Superfetch service. It will help you to get rid of the issue. I will attach the process below with some chronological steps.
Step 1: Tap the Windows key and type ‘services’. Accordingly, the app preface will be visible. You have to click on it.
Step 2: Consequently, the ‘Services’ window will appear. You have to find the ‘Superfetch’ from the services list. While finding, double-click on it.
Step 3: As a result, you will get the ‘Superfetch’ properties window. Here, you have to change ‘Startup type’ into ‘Automatic’. Then click on the ‘Start’ if the ‘Service status’ remains ‘Stop’. After that, press the ‘Apply’ tab and ‘Ok’ then.
In the end, close the ‘Services’ window and restart the PC.
Finally, check the error. Will it exist or not? If the fix doesn’t match your PC condition, you will have some other fixes to apply.
Fix 2: Run DISM Health Scan
Another way to resolve the issue is to run the DISM (Deployment Image Servicing and Management) health scan. You can try the process. I will attach the details below.
Step 1: Tap the Windows key and type ‘cmd’. Accordingly, the app preface will appear with some options. You have to click on the ‘Run as administrator’.
Step 2: Consequently, the ‘Command Prompt’ window will appear. You need to copy the below commands one by one and paste them into the window. You have to hit ‘enter’ each time you paste a command to execute it.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
The process may take a couple of moments to complete successfully. After completing it, you have to restart the PC as soon as possible.
Fix 3: Maximize Startup Event Trace Sessions File Size
Maximizing the ‘Startup Event Trace Sessions’ file size can fix the issue. The process will be given below.
Step 1: To apply the fix, you need the help of the ‘Command Prompt’ window. To do so, you need to follow the step 1 from the previous fix. Whenever you access the ‘Command Prompt’ window, type ‘perfmon’ into it. Then hit the ‘enter’ button.
Step 2: Consequently, the ‘Performance Monitor’ window will become evident on the screen. Here, you have to expand the ‘Data Collector Sets’ from the left menu pane.
Step 3: Then you have to click on the ‘Startup Event Trace Sessions’ option from the appeared list.
Step 4: After that, look at the right pane. From here, you have to find out the ‘ReadyBoot’. While finding it, double click on it.
Step 5: As a result, you will get the ‘ReadyBoot Properties’ window on the screen. Here you need to tap the ‘Stop Condition’ tab from the upper menu.
Step 6: Next, you need to change the ‘Maximum Size’ into ’40’ MB. Then, click on ‘Apply’ first and ‘Ok’ at the last.
In the end, close the ‘Performance Monitor’ and ‘Command Prompt’ windows.
After that, you have to restart the PC and check the existence of the issue.
Fix 4: Recreate ‘setup.etl’ File
The fix is rare but may work better for you. You need to follow the process step by step and be sincere while applying. I will include the process below.
Step 1: Tap the Windows and ‘R’ keys together. As a result, the ‘Run’ window will appear. You have to copy the below path and past it into ‘Open’ bar.
%windir%\panther
Then click on ‘Ok’.
Step 2: Consequently, you will reach the path destination. From here, you have to find out the ‘setup.etl’ file and rename it ‘setup.old’.
Step 3: After that, restart the PC. Accordingly, a new ‘setup.etl’ will be created automatically ignoring the ‘setup.old’ file.
Finally, check the issue. If somehow you still face it, the last option you will have in hand to resolve it.
Fix 5: Execute A Clean Boot
You have to execute clean boot to identify the reason and recover the issue permanently when none of the upper fixes work for you. You can follow the below steps to do so.
Step 1: Tap the Windows key and type ‘msconfig’. Accordingly, you will see the preface of the ‘System Configuration’ app with a couple of options. You have to click on ‘Run as administrator’.
Step 2: As a sequence, the ‘System Configuration’ window will appear. From here, you have to tap the ‘Services’ tab that stays on the top of the window. Then tick mark on the ‘Hide all Microsoft services’ box. After that, click on the ‘Disable all’ option.
Step 3: Next, tap the ‘Startup’ tab. From here, click on the ‘Open Task Manager’ option.
Step 4: While the ‘Task Manager’ appears, you need to tap the ‘Startup’ tab. Then, disable all the existed items from the list. After completing the task, close the window.
Step 5: As a result, you will be back on the ‘System Configuration’ window. Press ‘Ok’ to confirm the changes.
In the end, restart the PC.
Frequently Asked Questions
What Is Code 0x C0000188?
The error message 0xC0000188 is known as the Windows-specific error that commonly happens in Windows 10. It mainly happens due to a system error. You can fix this error by maximizing the file size of Startup Event Trace Sessions or by performing a clean boot.
What Is the Max File Size for Perf Diag Logger?
Max File Size for PrefDiag Logger is a Kkernel-Event Tracking error that can be found into the Event Viewer. You may find there that the Maximum file size for Pref Diag Logger is currently set to 209715200 bytes.
Final Words
Hopefully, the ‘Session “PerfDiag Logger” stopped due to the following error: 0xC0000188’ issue won’t arise anymore. I would like to request that you have just keep calm and apply the fixes one after another until success comes.
Many Windows 10/11 users have been experiencing an error that is causing their session \”Circular Kernel Context Logger\” to stop due to the following error 0xc0000188. This error can occur for different reasons, and it can be quite frustrating if you don’t know how to fix it. In this post, we will discuss some solutions that you can try to fix this error.
What is the Circular Kernel Context Logger?
The Circular Kernel Context Logger is a Windows feature that is used to collect performance data. It is part of the Event Tracing for Windows (ETW) framework and is used by Windows Performance Analyzer (WPA) and other system utilities to diagnose performance issues.
Common Causes of the Error 0xc0000188
The error 0xc0000188 can occur due to various reasons and conditions. Some of the most common reasons are:
- Third-party drivers conflict. The presence of certain third-party drivers can cause this error to occur.
- Damaged or corrupt system files. In some cases, damage or corruption of system files can cause this error.
- Outdated drivers or outdated Windows installation. The error can also occur if your system is not up to date.
- System conflicts or errors. System conflicts or errors can cause this error to occur.
How to fix the 0xc0000188 error on Windows 10/11
Method 1: Update your Drivers
Outdated drivers can cause the error 0xc0000188. So, make sure that all your drivers are up to date.
- Press the Win + X keys, and select Device Manager.
- Expand the device category for which you want to update the driver.
- Right-click on the device and select Update driver.
- Select Search automatically for updated driver software and follow the instructions.
Method 2: Use System File Checker (SFC) Tool
The System File Checker (SFC) tool checks the system files for corruption and replaces them if necessary. Follow the steps below to run the SFC tool:
- Press the Win + X keys and select Command Prompt (Admin).
- Type in the command:
sfc /scannowand press enter. - Wait for the process to complete.
Method 3: Use Deployment Image Servicing and Management (DISM) Tool
The Deployment Image Servicing and Management (DISM) tool can help repair the Windows image if the SFC tool fails to fix the error 0xc0000188. Follow the steps below to run the DISM tool:
- Press Win + X keys and select Command Prompt (Admin).
- Type in the command:
dism /online /cleanup-image /restorehealthand press enter. - Wait for the process to complete.
Method 4: Disable the Circular Kernel Context Logger session
If none of the above methods works, disabling the Circular Kernel Context Logger session can fix the error 0xc0000188. Follow the steps below to disable the session:
- Press Win + X keys and select Command Prompt (Admin).
- Type in the command:
logman stop "Circular Kernel Context Logger"and press enter. - Type in the command:
logman delete "Circular Kernel Context Logger"and press enter.
Conclusion
Fixing the error 0xc0000188 is not that difficult if you know what to do. The four methods discussed in this post will help you fix this error and get your system running smoothly again. It’s always a good idea to keep your system up to date and maintain it regularly to avoid any issues.
There exists an issue on the Windows Operating System where an affected user, after using their computer normally for a short amount of time, has their display replaced by an unrecognizable, inconsistent, grey display. When users affected by this specific issue open up their computer’s Event Viewer to see what went wrong, they see one or more listings of the following error message:
“Session ‘Circular Kernel Context Logger’ Stopped Due to the Following Error: 0xc0000188“
Doing even a light amount of research on this specific Event Viewer error message will bring to light the fact that it is considered to be a pretty common Windows error message and is nothing to be concerned over. However, it becomes quite concerning when paired with an affected user’s display going out and being replaced by a grey, completely unrecognizable joke of a display that renders their computer virtually unusable. This specific error message and this specific issue can be caused by an array of different things, chief among them being the affected user’s display drivers not working properly, the maximum file size of the Startup Event Trace Sessions being too small and the affected computer’s SETUP.ETL file being corrupt.
While this specific problem was first discovered on Windows 7, it can also affect versions of the Windows Operating System that were developed and released after Windows 7. Thankfully, though, there’s a lot a user affected by this problem can do to try and fix it. The following are the solutions that have proven to be the most effective when it comes to combating this issue:
Solution 1: Make sure that the Superfetch service is enabled and running
You might be seeing a horde of “Session ‘Circular Kernel Context Logger’ Stopped Due to the Following Error: 0xc0000188” error messages in your computer’s Event Viewer because a service known as Superfetch is, for some reason, disabled or otherwise not running on your computer. If that’s the reason why you’re experiencing this problem, all you need to do in order to get rid of it and never see this ugly error message ever again is make sure that the Superfetch service is not only enabled but is also running. To use this solution to try and resolve this problem, you need to:
- Press the Windows Logo key + R to open a Run dialog.
- Type services.msc into the Run dialog and press Enter.
- In the Services manager, scroll down and locate the Superfetch service, right-click on it and click on Properties.
- Open the dropdown menu in front of the Startup type: field and click on Automatic to select it.
- If the service was not already running, click on Start to begin running it. If the service was already running, simply skip this step and move on to the next one.
- Click on Apply and then on OK.
- Close the Services manager and restart your computer.
When the computer boots up, continue using it and check to see whether or not the problem still persists.
Solution 2: Increase the maximum file size of the Startup Event Trace Sessions
As stated before, another quite common cause of Windows users losing their display and having “Session ‘Circular Kernel Context Logger’ Stopped Due to the Following Error: 0xc0000188” error messages in their Event Viewer is the size of the Startup Event Trace Sessions not being adequate. If that’s the case, simply increasing the maximum file size of the Startup Event Trace Sessions should resolve the problem for you. To do so, you need to:
- Open the Start Menu.
- Search for “cmd“.
- Right-click on the search result titled cmd and click on Run as administrator to launch an elevated instance of the Command Prompt that has administrative privileges.
- Type the following into the elevated Command Prompt and press Enter:
perfmon
- The Performance Monitor should now show up on your screen. In the left pane of the Performance Monitor, double-click on Data Collector Sets to expand it.
- Click on Startup Event Trace Sessions under Data Collector Sets.
- In the right pane of the Performance Monitor, locate the ReadyBoot entry and double-click on it.
- Navigate to the Stop Condition tab and replace whatever is in the Maximum Size field with 40.
- Click on Apply and then on OK, close the Performance Monitor, close the elevated Command Prompt and restart your computer.
Check to see if the issue has been resolved when your computer boots up.
Solution 3: Make your computer replace the SETUP.ETL file with a new copy
If neither of the solutions listed and described above have worked for you, you can still try a hail Mary – forcing your computer to replace the SETUP.ETL file with a new copy. A corrupt SETUP.ETL file can also, in many cases, be the case of this issue, so making your computer replace its current SETUP.ETL file with a new one should take care of any corruption or other damage inflicted upon the old file. To make your computer replace its current SETUP.ETL file with a fresh one, you need to:
- Press the Windows Logo key + R to open a Run dialog.
- Type the following into the Run dialog and press Enter:
%windir%\panther
- In the instance of Windows Explorer that pops up on your screen, locate a file titled setup.etl, right-click on it and click on Rename.
- Rename the file to setup.old and press Enter to confirm the action.
- If asked whether you’re sure about changing the file’s extension, confirm the change.
- Restart your computer. When the computer boots up, it will automatically create a new SETUP.ETL file, completely disregarding the old one that you renamed. Once this is done, check to see if this solution managed to resolve this problem for you.
Kevin Arrows
Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.
Introduction
When it comes to performance monitoring in Windows operating systems, the Performance Diagnostics Logger plays a crucial role. It helps in gathering performance data, which can be invaluable for diagnosing issues and optimizing the performance of your system. However, many users have encountered the frustrating error message: «PerfDiag Logger Stopped Due to Error: 0xc0000188». This error can stem from various sources, including insufficient disk space, corrupted settings, or other system-level issues.
In this article, we will delve into the causes of this error, its implications, and provide you with comprehensive troubleshooting steps and solutions to resolve the issue effectively.
Understanding the Error: 0xc0000188
The error code 0xc0000188 is a Windows-related error that indicates a problem with the system’s logging functionality. Essentially, it means that the PerfDiag Logger encountered a situation where it could no longer maintain its operation due to either internal constraints or external conditions.
-
What is PerfDiag?
The Performance Diagnostics (PerfDiag) tool in Windows is designed to collect and analyze data concerning your computer’s performance. When enabled, this tool generates logs that help diagnose system-level problems efficiently. -
The Importance of Logging
Logs are vital for developers and users alike because they provide detailed information about system performance, application behaviors, and potential error messages. They allow users to identify bottlenecks in system performance and address underlying issues proactively.
Symptoms of the Error
When you encounter the PerfDiag Logger Stopped Due to Error: 0xc0000188, you may notice the following symptoms:
- The Performance Monitor might display an error message indicating that logging has stopped.
- You may experience poor system performance or sluggish behavior when running resource-intensive tasks.
- Other related performance tools and services may also exhibit abnormal behavior, indicating that logging has ceased.
Causes of the Error
Several factors can contribute to the PerfDiag Logger error 0xc0000188. Below are some of the most common causes that you should consider when troubleshooting.
-
Insufficient Disk Space
One of the primary reasons this error occurs is a lack of available disk space. The PerfDiag Logger requires sufficient storage to maintain its log files. When disk space runs low, logging will stop. -
Corrupted Log Files
If the existing log files become corrupted, it can impede the functionality of the PerfDiag Logger. Corruption can occur due to abrupt system shutdowns, file system errors, or malware infections. -
Incorrect Configuration
Sometimes, improper configuration settings can lead to issues with the PerfDiag Logger. Modifying the configurations incorrectly may lead to conflicts or bugs that prevent logging from operating. -
System File Corruption
Corrupted system files can affect various functionalities of Windows, including logging tools. System file corruption can occur due to hard drive failures, power outages, or improper shutdowns.
Step-by-Step Troubleshooting Guide
Now that we have established the background and potential causes of the error, let’s explore the methods you can use to resolve the PerfDiag Logger error 0xc0000188.
Step 1: Check Disk Space
The first and simplest step is to ensure that there is sufficient disk space on your hard drive. Here’s how to do that:
- Open File Explorer: Press
Windows + Eto open File Explorer. - Check the Drive: Right-click on the drive where Windows is installed (usually C:) and select
Properties. - Look at Available Space: Check how much free space is available. For optimal performance, it’s recommended to have at least 15-20% free space on your drive.
Resolution: If space is low, consider deleting unnecessary files, uninstalling unused applications, or moving data to an external hard drive or cloud storage.
Step 2: Clear Corrupted Log Files
If low disk space was not the issue, it may be worthwhile to clear the existing log files.
- Open Event Viewer: Press
Windows + R, typeeventvwr.msc, and pressEnter. - Navigate to Logs: In the Event Viewer, expand the
Windows Logsand look forApplications and Services Logs>Microsoft>Windows>Performance Diagnostic. - Delete Logs: Right-click on the folder and select
Clear Log. You can also save the log if you’d like for further analysis.
Note: Clearing the log files frets you of potential corruption and allows the tool to create fresh, error-free log files on the next run.
Step 3: Reset PerfDiag Configuration
Next, it might be beneficial to reset the PerfDiag settings to default.
- Access PerfDiag: Open a command prompt as an administrator. You can do this by searching for «cmd» in the start menu, right-clicking it, and selecting «Run as administrator.»
- Stop PerfDiag Logger: Enter the command:
perfdiag /stop - Reset Configuration: Follow up with the command:
perfdiag /reset
This action will reset PerfDiag and remove any problematic configurations that could be preventing it from logging.
Step 4: Run System File Checker
If the problem persists, it might be time to check for corrupted system files:
- Open Command Prompt as Admin: Similar to the previous step, launch Command Prompt with administrative privileges.
- Run SFC Scan: Enter the command:
sfc /scannow
This command will initiate a scan of your system files and repair any corrupted ones. The process can take some time, so be patient and allow it to complete.
Step 5: Check for Windows Updates
Ensuring your operating system is up to date is crucial in maintaining optimal performance and resolving unforeseen issues:
- Open Settings: Click on the Start menu, then on the gear icon to open Settings.
- Check for Updates: Go to
Update & Securityand selectCheck for updates. Install any available updates to ensure your system has the latest features and bug fixes.
Preventive Measures
To help prevent the PerfDiag Logger error from reoccurring in the future, consider the following preventive tips:
-
Maintain Disk Space: Regularly check your disk space and keep at least 15% free to ensure smooth operation of logging tools.
-
Regular Backups: Use backup solutions to maintain critical data. In addition, regularly back up your log files. This backup can often provide insights into previous issues.
-
Install Antivirus Software: Malware and viruses can corrupt files, including log files. Protect your system by using reputable antivirus software and conducting regular scans.
-
System Maintenance: Perform regular maintenance on your computer, including disk cleanups, defragmentation (for HDDs), and routine checks with the built-in Windows tools.
-
Update Regularly: Lastly, ensure that your operating system and all applications are updated to their latest versions. This reduces the chances of encountering bugs and conflicts.
Conclusion
The error message «PerfDiag Logger Stopped Due to Error: 0xc0000188» can be daunting, but by understanding its causes and implementing systematic troubleshooting steps, you can regain control over your system’s performance logging. Additionally, following the preventive measures highlighted will ensure that your Windows operating system runs efficiently, minimizing the chances of encountering similar errors in the future.
In summary, while encountering the PerfDiag logger error may be alarming, it is manageable. With adequate attention and maintenance, you can ensure that your system’s performance diagnostics work as intended, guiding you in optimizing your computer’s performance for years to come.