Question / Help Quick Sync causes PC crash after Windows reinstall.

Hawky

New Member
I reinstalled Windows a few days ago. And now for some reason quick sync is not working in OBS. I have 2 instances of OBS set up. One records my game with H.264 and the other records my webcam with Quick Sync. Both at 1080p and 30fps. This worked perfectly fine before I reinstalled Windows but now that I've reinstalled Windows anytime I start a recording my PC freezes after 3 seconds. No bluescreen, just freezes. Only way to recover is through a hard shutdown. (Holding power button for 5 seconds)

If I set up both instances of OBS to use H.264 instead of Quick Sync it sorta works. My PC lags a lot though and my Game instance of OBS gives me high encoding warnings. But if I set my webcam instance to 720p instead of 1080p it works fine but my PC stutters occasionally. Nevermind still lags.

Here are some logs when my PC crashes because of Quick Sync:
Webcam instance of OBS (Quick Sync, 1080p, 30FPS): https://gist.github.com/anonymous/7d953486041ab907f004
Game instance of OBS (H.264, 1080p, 30FPS): https://gist.github.com/anonymous/ce055721109f74c47047

Here are some logs with both instances set up as H.264 (1080p on both):
Webcam instance of OBS (H.264, 1080p, 30FPS): https://gist.github.com/anonymous/534b52a09194d2daf48d
Game instance of OBS (H.264, 1080p, 30FPS): https://gist.github.com/anonymous/b872c540b39406a36a6c

Here are some more logs with both instances set up as H.264:
Webcam instance of OBS (H.264, 720p, 30FPS): https://gist.github.com/anonymous/5902d8cd2b2fa9c898ef
Game instance of OBS (H.264, 1080p, 30FPS): https://gist.github.com/anonymous/ec5c0098e5195a3bf7fc

System specs:
Windows 10 Pro x64
Core i7 4790k at stock speed
MSi GeForce GTX 970 4G stock speed
16GB 1866MHz ram
240GB M.2 SSD (Boot Drive)
1TB 7200RPM HDD (Recording Drive)

Things I've tried:
Updating drivers
Rolling back drivers
Reinstalling Windows
Lowing settings (We're talking 240p here guys)
Updating BIOS
Rolling back BIOS
 

Hawky

New Member
Figured it out. Had to go back to an even earlier BIOS. I'm gonna contact MSi now and inform them about this issue.
 
Top