Presentmon Initialization Error

[RuddroKRM1]

Facing this problem.
My config
i7 7700k
Z270
GTX1070
16 GB DDR4 3200MHZ

[markgalvan-intel]

It appears the PresentMonService might not be started. Can you please try restarting the service? Steps to do so are:

1. Open the Services applet.
2. Look for "PresentMonService" and start it. If it is already running you can try restarting it or restarting your computer.

Please let us know if this addresses the issue.

[RuddroKRM1]

I have tried the your steps but still the issue remains the same.

[markgalvan-intel]

When checking on PresentMonService what is the "Status" displayed in the Services applet? When you start it does it stay in the "Running" state?

[RuddroKRM1]

Yes.

[AntareSkorpion]

I'm running into this issue in one of my PC's as well.
Presentmon service also confirmed as running.

[markgalvan-intel]

Thanks for the information. We have been unable to reproduce the issue locally. Would it be possible to gather some logs from the system to help in the debug effort? We can provide the necessary steps to generate logs for both Intel PresentMon and the PresentMonService. Please let us know if this is something you are willing to try.

Thanks!

[AntareSkorpion]

Sure, what are the steps?

[siberx]

I am seeing the same issue as well. I went digging and found the following gets added to cef-debug.log every time I try to start the GUI:

[0416/203056.457:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[0416/203056.534:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[0416/203056.667:ERROR:gpu_channel_manager.cc(955)] Failed to create GLES3 context, fallback to GLES2.
[0416/203056.667:ERROR:gpu_channel_manager.cc(966)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.

My service is also in normal "Running" state and a reboot had no effect. The default.log file in the same folder remains empty. I haven't been able to find any other related logs with anything in them, and don't know where the service logs to (if anywhere) by default.

AMD 5900x
X570
GTX 1080
32GB DDR4-3600

[markgalvan-intel]

This is great. The high level steps for gathering logs from PresentMonService and Intel PresentMon are as follows:

1. Stop PresentMonService from the services applet.
2. Enable logging in PresentMonService by adding a logging parameter to the Start Parameters.
3. Restart PresentMonService.
4. Enable logging in Intel PresentMon by updating the Intel PresentMon shortcut to include a logging parameter.
5. Launch Intel PresentMon from the altered shortcut.
6. When issue is seen, close Intel PresentMon and stop PresentMonService once again.
7. Gather the logs.

Detailed steps for setting up logging for PresentMonService and Intel PresentMon are below. If you have any questions please don't hesitate to ask!

Enabling PresentMonService Logs
Enabling log generation in the service requires creating a temporary directory where the log file will be saved and adding the start parameter "--log-dir " for PresentMonService.

First, create the temporary directory in any convenient location where you have write access. I created mine in "c:\temp\pm2":

Second, in the services applet update the properties of PresentMonService:

Third, update the Start parameters by adding in the "--log-dir" start parameter along with the directory name where the log will be saved and then hit the "Start" button.

Once the error occurs hit the "Stop" button and the full log will be written to the specified directory:

The log file from PresentMonService saves the name of the computer of where it was generated so if you want to remove it from the log feel free to do so. The computer name is located on the second line as shown here:

Enabling Intel PresentMon Logs
Enabling log generation for the Intel PresentMon application is done by altering the Intel PresentMon shortcut to include "--p2c-verbose". This will dump logs out to "AppData\Local\Intel\PresentMon\logs" in the file "default.log".

First, open the properties of the Intel PresentMon shortcut:

Second, add in "--p2c-verbose":

Once the shortcut is updated, relaunch Intel PresentMon and then close it after the error screen is shown. Upon closing the application the "default.log" file should be generated.

[siberx]

Thanks for the clear guides, didn't actually know you could temporarily pass launch parameters to a windows service like that; cool trick.

I have attached the logs generated from both the service and the GUI app, hopefully this helps track down the problem. Let me know if you need any more info.
pm-srv-err-20240417-204800.328.log
pm-srv-info-20240417-204759.328.log
pm-srv-warn-20240417-204800.328.log
default.log

[markgalvan-intel]

This is great! We'll dive into the logs and see if we can determine the root cause of the issue. Very much appreciate your time and help!

[AntareSkorpion]

Hi again, Here are my logs as well.
pm-srv-err-20240419-123442.11708.log
pm-srv-info-20240419-123442.11708.log
pm-srv-warn-20240419-123442.11708.log
cef-debug.log
default.log

this machine is running the following specs.
CPU - i9-9900K
GPU - RTX 2080
RAM - 32 GB

I'm deploying Presentmon on a lab with 4 machines. Two of them work just fine, two of them, not so much.
Of the two not working, only this one displays this error. The other one just crashes when starting a capture. But we'll cross that bridge when we get there, after figuring out this one.

Additionally, other tools that also run on the presentmon service (i.e. capframeX) seem to work just fine.

Thanks in advance for the help!

[markgalvan-intel]

Hello! Thank you so much for the logs @siberx and @AntareSkorpion. With them we were able to piece together what is happening and reproduce on our side. We are working on a fix and will give details as we make progress. Really appreciate the help in this effort!