Bug Report 0.633b - QSVHelper.exe was killed, encode failed

[gdlk]

Got this with new release. I tried to stream gif image for test.

Encode parameters:
03:25:38: Video Encoding: QSV
03:25:38: fps: 30
03:25:38: width: 1920, height: 1080
03:25:38: target-usage: MFX_TARGETUSAGE_4_BALANCED
03:25:38: profile: MFX_PROFILE_AVC_HIGH
03:25:38: CBR: yes
03:25:38: CFR: yes
03:25:38: max bitrate: 4000
03:25:38: buffer size: 4000
03:25:38: rate control: CBR
03:25:38: -------------------------

 

[Kslay]

Happened to me as well, so I'm going to bump this thread.

Never had this issue until I updated to 0.633b. I have updated to 0.634b and still got the same issue. The log that I have attached is from 0.634b.

Like the OP, my CPU is an i7 3770k, however I was using a much, much higher bitrate as I was recording locally.

Log name for i7 3770k + 0.634b = 2014-15-2138-39.log

One thing to point out is that I have another computer running an i7 4770k still using 0.633b and have had no issues using quicksync. I was recording locally as well, for about 20 minutes.

Log name for i7 4770k + 0.633b = 2014-09-15-2134-07.log

 

[PixelPolish]

Same here on v0.637b. Tried everything short of re-installing the system and it's driving me nuts :(

 

[Lain]

Just so people know, if you're ever wondering why you see a lack of QSV-related responses from me it's because it's not my area of expertise, I've actually never used it myself, nor did I develop it personally. I don't really know anything about it myself.

However I do notice that you're trying to do 1080p 60fps, which might bring out some problems. If you have QSV problems and downgrading completely fixes the issue with the exact same settings, you *might* want to contact palana about it.

 

[gdlk]

Still have this problem (latest release) with i7-3770k on different bitrate and fps. As i can see this problem never occurs with later Intel CPU series.

Here some logs that might be helpfull.

 

[Vechlor]

Uncheck "Use Multithreaded Optimizations", this seems to have fixed the random crashing. See my log file for more details.

OBS v0.637b - 64bit
Using latest Intel HD2500 Driver - win64_153329

Update:

Nope, seems to crash just like before.

 

[gdlk]

Uncheck "Use Multithreaded Optimizations", this seems to have fixed the random crashing. See my log file for more details.

OBS v0.637b - 64bit
Using latest Intel HD2500 Driver - win64_153329

didn't work for me, got 'Terminating QSVHelper.exe after timeout' as well.

 

[PixelPolish]

didn't work for me, got 'Terminating QSVHelper.exe after timeout' as well.

Didn't work for me either. I had to give up QuickSync entirely and go back to the old ways - constant crashes were not worth it. But damn the performance was good during those brief moments between the crashes :(

 

[gdlk]

It seems QSV works stable at Windows 8.1. Since I've installed it I didn't get this crash anymore (OBS working already for 8 hours).
As a little bonus of 8.1 you don't have to have virtual monitor for using QuickSync.
Hope this will help for over streamers. It's my problem solution for now.

 

[Diablocalypse]

Ty, i try tomorrow and i give my result.

 

[gdlk]

Yep, still working perfect on Win8.1.

 

[Vechlor]

Thanks for posting back.

I'll probably give Windows 10 a try soon, which I hope solves the crashing as it did for you. Until then, I'm stuck on Win7, which has been running perfect for years, but I've just started using OBS recently and Nginx for 1080p streaming (thanks to those who provided guides).

Also, I've tried other software with QSV capture recording without any problems, but it's not the same as OBS :) That just tell's me that the latest Intel drivers and igpu configuration works fine and should for OBS.

For now, I'm using local recordings, near lossless with a small cpu hit.

Spoiler: Encode Settings

As an alternative to QSV lossless recording with a minimal cpu hit, these settings below allow me to capture near lossless quality, native resolution and better audio for the same cpu cost of a 720p Twitch stream, then I upload straight to Youtube, they don't have the best encode quality for fast motion, but I can store my source videos there for download later. Can't wait for them to add 48/60fps support. The down side is I won't be streaming live until QSV/Nginx is working again, I won't go back to 720p.

1hr of video+audio is about 10GB. This can be reduced by a lot using 2pass 5200Kbits re-encoding. OBS uses about 10-20% cpu usage on a i5 3550 system with 16GB memory.

Settings > Encoding:
Video: x264, CBR: unchecked, Quality: 10, MaxBitrate: 5000?, CustomBuffer: Checked, Buffer Size: 0.
Audio: AAC, 48kHz, Bitrate: 192, Channel: Stereo.

Broadcast Settings: File Output Only, FLV (best if OBS decides to cash) or MP4 format.

Video: Native Resolution, FPS:30 (48/60 = higher cpu cost, Youtube doesn't support yet)

Advanced: Use defaults except for Preset: ultrafast, Profile: High, Keyframes: 0, Use CFR, Custom x264 Encoder Settings: crf=20 (lower = larger file size, slightly better quality), no-fast-pskip=true (good for lower bitrates and fast motion, less blocking, fonts look sharper, lines etc., don't need at high bitrates) deblock=1:1 (optional, don't need at high bitrates)

 

[Johnz]

im also getting this problem

 

[PrinceVinc]

I have that problem aswell i7-4790k latest driver. So it does occur on later CPU's!

 

[Insire]

I had the problem yesterday aswell. Disabling "Use Multithreaded Optimizations" seems to have worked for me. 2h+ stream and no crash.

cpu: i7 4770k oc
windows 7 64bit ultimate
obs: 0.637b 64bit

 

[Void4ever]

I'd like to bump this too. I was all excited because i finally have the bandwidth to stream but I'm getting "QSVHelper.exe was killed, encode failed" as well. I can stream using the old method but man what a difference when i was using QuickSync.

Current version of OBS 0.638b
Intel(R) Graphics Driver: 10.18.10.3960
i7 4770k

I haven't had a lot of time to test, but i'd be willing to try some older intel drivers, i'll try that when i get off work tomorrow. Also the OP says he started getting it with the new version. I'm curious what was the last version of OBS that this worked with? I would be willing to go backward until the dev's figured it out.

Void4ever

 

[Insire]

I had the problem yesterday aswell. Disabling "Use Multithreaded Optimizations" seems to have worked for me. 2h+ stream and no crash.

cpu: i7 4770k oc
windows 7 64bit ultimate
obs: 0.637b 64bit

scrap that, streamed today - still crashes
version: 0.638b

 

[Void4ever]

Looking at my post from last night i'm not sure where i got that driver number, the driver i was using last night was 15.36.7.64.3960

I went ahead and downgraded tonight to 15.36.3.64.3907, still the same error although this time i got a bit more info and it popped up the crashdump. I notice no one else has included the dump or dump log file, just the general log file from OBS. I'll attach all 3 to my post, hopefully they are of more use.

I'm going to poke around and try older versions of OBS i think.

Void4ever

 

[Void4ever]

OK so i tried 4 different versions. Starting just before the version OP said stopped working, and worked my way backward. All of them crashed out, but i took notes for each.

632b - same crash issues, same behavior

631b - instead of crashing out and dying like newer versions, OBS starts eating CPU and memory creating massive log files filled with
"Warning -- Terminating QSVHelper.exe after timeout"

63b - same issue as 631b, log file fun time!

625b - Crashed after about 10 minutes, this one actually gave a crash dump. I did notice once in a while in the bottom left corner OBS flashing red saying "warning, taking to long to encode, skipping frames"
Interestingly enough though the skip frame counter shows no lost frames, although I'm fairly certain thats connection based.

I hesitate to go any further back as i see some of the patch notes talk about quicksync causing streams to bug out.

All of these tests were run with intel drivers 15.36.3.64.3907 released on 8/29.

Void4ever

 

[akskiller]

I wanted to try quick sync too and got this error withing 30 seconds of starting to stream. I did some testing and found that I had to change the video adapter to my on board graphics which in my case is Intel HD Graphic 4600. After 1 hour of streaming I didn't get any error.