I have OBS Studio version 32.0.02(64 bit) installed on a Windows 11 Pro 10.026100 build with SK Hynix Patriot DDR4-3200 (1600 MHz) 32G RAM, Intel core i7 12700K, on a MSI Pro Z-690A (MS-7D25) motherboard with AMI BIOS 1.E0 from 09/11/2023. The graphics is run by Intel UHD Graphics 770. This has worked well enough for all I need (no gaming). I have done a lot of multitasking, often a number of tabs open in Chrome, OBS Studio running and often recording streaming content short videos. None of this has been a problem even while sometimes running multiple streaming videos on different Chrome tabs (paused). But recently I'm getting momentary freezes where I lose control of my cursor. Often just control tabbing over to the running OBS Studio window and back to Chrome returns my cursor, but it's annoying to have to do that.
I've checked my audio output devices and their drivers. Intel puts an update checker in my system tray that assures I always keep its cpu and gpu drivers up to date. I'm connected to a large screen Insignia-TV for my monitor. That has also never been a problem, and I recently replaced my old three year old one with a new version of the same product. None of the freezing started until recently (after months of the new video device connection). I have occasionally in the past used a VB Audio Virtual Cable that I use to be able to create transcripts from audio files, but I haven't used that in a while and only rarely.
I checked my HDMI cable connections. It's a high quality cable with gold connectors. I also checked cpu and gpu usage by running processes in Sysinternals Process Explorer. The highest cpu use is 93.41% for System Idle Process, also very low private bytes and Working Set (except for the usual many processes of Chrome, but even those are insignificant in cpu usage. I checked my Device Manger and nothing strange shows up there, everything reporting working. I could check the audio drivers, but most likely I think it would be the Insignia ones. I just don't know. I checked my OBS logs for the past hour when this had happened, but maybe it's best to start fresh and see if and when it happens again then send you the entire log.
For a maybe preliminary thought, here's what I see in the log during that period I mention when I did get a bunch of those cursor freezes:
15:11:40.076: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' invalidated. Retrying (source: Desktop Audio) 15:11:40.102: WASAPI: Default output device changed 15:11:41.326: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.335: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.340: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.349: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.361: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.366: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.368: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.370: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.376: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.385: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.390: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.391: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.393: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.393: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.944: WASAPI: Default output device changed 15:11:43.102: WASAPI: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' [48000 Hz] initialized (source: Desktop Audio) 15:11:43.103: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' invalidated. Retrying (source: Desktop Audio) 15:11:43.118: WASAPI: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' [48000 Hz] initialized (source: Desktop Audio)
I hope that is not redundant. I'll also attach the latest log file, but tell me if I should start fresh and reproduce the problem, then send you the latest log file.
I also checked my system Chrome settings and disabled using hardware acceleration. And, in my Windows System Settings I made sure no energy saving profiles were set or energy saving or sleep on, etc. I uploaded the current log file and analyzed it. Here's the log url: https://obsproject.com/logs/5AiRcFqOeHNnKRQR
The analysis told me what I already knew - that my gpu won't run both OBS Studio and any gaming, and that's why I never do any gaming. In addition, it told me I was running a .5% rendering lag and suggested enabling vsync or setting a reasonable frame rate limit that my UHD 770 gpu can handle without hitting 100% usage. I could use a little bit of help with that.
I'm trying running OBS Studio in admin mode (I hadn't thought of that). Anyway, as I mentioned, I don't do any gaming at all.
Here are my Intel UHD 770 graphics metrics:
There were also OBS Qt bug entries in the log file. I read about how OBS Studio uses that framework in rendering its user interface when the OBS window is shown or resized. Could that be glitching when I switch application focus between Chrome and OBS Studio? I mentioned that I found switching out of the Chrome window, into the OBS window, and back to Chrome, generally returns control of my frozen cursor in Chrome back to me.
Anyway, hoping for some help from you guys. Thanks.
I've checked my audio output devices and their drivers. Intel puts an update checker in my system tray that assures I always keep its cpu and gpu drivers up to date. I'm connected to a large screen Insignia-TV for my monitor. That has also never been a problem, and I recently replaced my old three year old one with a new version of the same product. None of the freezing started until recently (after months of the new video device connection). I have occasionally in the past used a VB Audio Virtual Cable that I use to be able to create transcripts from audio files, but I haven't used that in a while and only rarely.
I checked my HDMI cable connections. It's a high quality cable with gold connectors. I also checked cpu and gpu usage by running processes in Sysinternals Process Explorer. The highest cpu use is 93.41% for System Idle Process, also very low private bytes and Working Set (except for the usual many processes of Chrome, but even those are insignificant in cpu usage. I checked my Device Manger and nothing strange shows up there, everything reporting working. I could check the audio drivers, but most likely I think it would be the Insignia ones. I just don't know. I checked my OBS logs for the past hour when this had happened, but maybe it's best to start fresh and see if and when it happens again then send you the entire log.
For a maybe preliminary thought, here's what I see in the log during that period I mention when I did get a bunch of those cursor freezes:
15:11:40.076: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' invalidated. Retrying (source: Desktop Audio) 15:11:40.102: WASAPI: Default output device changed 15:11:41.326: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.335: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.340: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.349: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.361: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.366: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.368: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.370: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.376: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.385: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.390: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.391: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.393: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.393: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce. 15:11:41.944: WASAPI: Default output device changed 15:11:43.102: WASAPI: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' [48000 Hz] initialized (source: Desktop Audio) 15:11:43.103: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' invalidated. Retrying (source: Desktop Audio) 15:11:43.118: WASAPI: Device 'INSIGNIA-TV (HD Audio Driver for Display Audio)' [48000 Hz] initialized (source: Desktop Audio)
I hope that is not redundant. I'll also attach the latest log file, but tell me if I should start fresh and reproduce the problem, then send you the latest log file.
I also checked my system Chrome settings and disabled using hardware acceleration. And, in my Windows System Settings I made sure no energy saving profiles were set or energy saving or sleep on, etc. I uploaded the current log file and analyzed it. Here's the log url: https://obsproject.com/logs/5AiRcFqOeHNnKRQR
The analysis told me what I already knew - that my gpu won't run both OBS Studio and any gaming, and that's why I never do any gaming. In addition, it told me I was running a .5% rendering lag and suggested enabling vsync or setting a reasonable frame rate limit that my UHD 770 gpu can handle without hitting 100% usage. I could use a little bit of help with that.
I'm trying running OBS Studio in admin mode (I hadn't thought of that). Anyway, as I mentioned, I don't do any gaming at all.
Here are my Intel UHD 770 graphics metrics:
There were also OBS Qt bug entries in the log file. I read about how OBS Studio uses that framework in rendering its user interface when the OBS window is shown or resized. Could that be glitching when I switch application focus between Chrome and OBS Studio? I mentioned that I found switching out of the Chrome window, into the OBS window, and back to Chrome, generally returns control of my frozen cursor in Chrome back to me.
Anyway, hoping for some help from you guys. Thanks.