OBS Freezing once opened for 40 to 50 min. Using Windows 11 22h2 (OS Build 22621.105) release preview

Kh3699

New Member
I have no clue what is going on. I set a timer to see how long it takes before OBS deices to freeze, the time it takes to freezes seems to be between 40 and 50 min of having it open. Nothing has changed with OBS except one thing, my OS, I upgraded to Windows 11 22h2 (OS Build 22621.105) release preview a day ago. The freezing started to happen right after I went from Windows 11 22h1 (original release) to 22h2. Perhaps my logs can tell you a reason why. Graphics Drivers are up-to-date (RTX 3080 12gb) I even DDU uninstalled and reinstalled all drives related to graphics just to make sure it wasn't an issue. This freezing happens while streaming, recording or just having the program open (no streaming or recording). I also have OBS.live added on to OBS (StreamElements).
 

Attachments

  • 2022-06-22 20-07-37.txt
    131.7 KB · Views: 6

PaiSand

Active Member
You're using SE.live plugin. Please contact them for support.
Alternatively, uninstall it. Then uninstall and reinstall OBS in order to fix the changes made by this plugin. Now please do a test stream/recording of more than 30 seconds and post the log file here.

Also, win11 isn't recommended for production. Less if you use a release preview.
 
Last edited:

Kh3699

New Member
I've uninstalled SE.Live did a test recording of 30+ seconds, here is the new log file
 

Attachments

  • 2022-06-23 14-43-16.txt
    11.5 KB · Views: 6

PaiSand

Active Member
Like I said before, you're using the windows 11 insiders build wich may break more things than fix. If it was working, then you installed this unstable not supported versions of the OS, is clear from where the issues are coming. Go back to the working version of the OS. Be adviced that windows may not work the same way as before after using an unstable version of it.
 

Kh3699

New Member
Thanks for the help, PiaSand. I didn't want the answer to be just roll back to Windows 11 22h1 from 22h2. Was hoping there might be more to it than just a rollback for a fix. It looks like that might be the right option to fix this. I have rolled back from Windows 11 22h2 to 22h1.
 
Top