Handbrake Crashes

WhiteHawk77

WhiteHawk77

WhiteHawk77

Associate
Joined
9 Oct 2011
Posts
531
Location
UK
Hey there, I'm trying to convert bluray rips for streaming from a NAS and Handbrake either BSOD's my PC on the normal build or crashes itself if I try a nightly build.

Now It crashed my PC before, but this is a new motherboard and RAM and new drivers and as everything else seems to be fine it seems that Handbrake is just not stable on Windows 10 at least, so anyone know how to fix this or an alternative with options to pick the audio stream and forced only subtitles and good quality control.

Thanks.
 
I've had issues like that before. Usually caused by an unstable cpu or dodgy RAM. I would test the RAM. It might be easier to firstly drop the CPU speed back to stock or put some more voltage and try it again.

I use handbrake and it works fine in win 10 for me.
 
Handbrake uses Every thread & core of your CPU & uses instruction sets that are not used in other general applications. (AVX)

This instruction set is very proven to be untoralent to unstable CPU's
not even most CPU stress tests include this set...

I know ASUS tool does
https://youtu.be/Oxd651HEsXE?t=458

ive used handbrake on 300+ blurays without any issues going from SSD -> SSD 100% maxed on all cores for 18 hours without issue.
It will be a hardware issue/overclocking issue
 
As above, Handbrake is quite taxing, so oddly, it makes a good stress test :p.

I think there's a setting somewhere in the nightlies for GPU acceleration but I found the quality on that to be pretty poor.
 
Many use it instead of the likes of Prime to check for stable overclocks, so yeah, I'd go for either dodgy overclock or dodgy hardware (very likely the former of course).

I've had a couple of videos that Handbrake failed on, but it just resulted in an corrupt file rather than a system crash. I've been using it for years and I'm yet to see any blue screens or the likes.
 
Hey guys, thanks for the info, looks like it was an unstable OC.:rolleyes: or should that be :(

I went back to default speed and it did a full movie conversion, I then put it back to 4.5Ghz and also set the voltage back to 1.30 like I had it originally when I set the OC and it did the same movie again just fine so I guess 1.25 volts isn't enough for Handbrake, for everything else including Aida64 but not that, typical.

Anyway, anyone got any tips for Handbrake as I'm not a 100 percent happy with the results yet, I tried Big Hero 6 as a test as it's a CGI movie I could perhaps more easily see the quality differences between settings. The one I just did still looked grainy at 5GB and I want to keep the file size down to between 4-8GB roughly. The settings were:

High Profile MP4
Anamorphic: Strict
H.264
Encoder Tune: Film
Encoder Preset: VerySlow
Quality: 18
Audio: DTS-HD Master converted to AAC bitrate 256 Stereo
Subtitles: Forced only Burn in

Thanks for any help, as for the OC I'll drop the voltage bit by bit again and test with this instead of Aida64. :)
 
"Encoder Tune: Film" will prioritise grain (it means "photographic film", not "movie"), so unless the video you're converting was shot on film and you particularly want to preserve the film texture, set this to default. It should NEVER be set this way for animated films (they have no grain!).

You should probably also set a Denoise Filter if you haven't already, even if it's not a noisy source, as it really helps the compression ratio. Usually the "light" setting is fine.

Other than that, reduce the CQ parameter until you're happy. Although 20 is usually low enough and 18 is quite extreme already.

Edit: FYI, the preset (e.g. VerySlow) improves compression (reduces file size) but doesn't affect quality.
Also you could try H.265, it has 2x the efficiency.
 
Last edited:
joeyjojo said:
"Encoder Tune: Film" will prioritise grain (it means "photographic film", not "movie"), so unless the video you're converting was shot on film and you particularly want to preserve the film texture, set this to default. It should NEVER be set this way for animated films (they have no grain!).

You should probably also set a Denoise Filter if you haven't already, even if it's not a noisy source, as it really helps the compression ratio. Usually the "light" setting is fine.

Other than that, reduce the CQ parameter until you're happy. Although 20 is usually low enough and 18 is quite extreme already.

Edit: FYI, the preset (e.g. VerySlow) improves compression (reduces file size) but doesn't affect quality.
Also you could try H.265, it has 2x the efficiency.
Click to expand...

Thanks for the info, only reason I used the film option is that I came across that online but I think I'll leave it off, just did one without and it's a bit better with a 2.9GB file size with CQ at 20, think I'm on the right track now.
 
This is why overclocking stress tests are utterly useless. Said this many many times.

When someone says I have my i7 overclocked to 4.8ghz 24/7 stable I always have a little chuckle.

Have a nights worth of video encoding then come back to us with your claims of stability ;-)

OP, reset bios to defaults and try again
 
glen8 said:
This is why overclocking stress tests are utterly useless. Said this many many times.

When someone says I have my i7 overclocked to 4.8ghz 24/7 stable I always have a little chuckle.

Have a nights worth of video encoding then come back to us with your claims of stability ;-)

OP, reset bios to defaults and try again
Click to expand...

Not sure why people are missing my other post but I already mentioned that I have it back at 1.30 volts on 4.5Ghz and its stable, done several full movies now fine, will drop volts 0.01 at a time and test again with Handbrake.
 
WhiteHawk77 said:
Not sure why people are missing my other post but I already mentioned that I have it back at 1.30 volts on 4.5Ghz and its stable, done several full movies now fine, will drop volts 0.01 at a time and test again with Handbrake.
Click to expand...

glen8 isn't even right, x264 is no better than linpack or prime95 as long as they're used correctly.
 
joeyjojo said:
glen8 isn't even right, x264 is no better than linpack or prime95 as long as they're used correctly.
Click to expand...

I beg to differ. I've had overclocked machines run well past a 24hr peroid, yet crash after an hour of video encoding.

as mentioned above, video encoding can in certain situation stress your machine more than any stress test can.
 
had the same issue as OP with my 5930k, ran AIDA64 for 20+ hours with no problems.

After a couple of conversions in Handbrake my PC kept freezing, lowered my OC to 4.4Ghz and has been ok since.
 
The ultimate test for me, if I can last 24 hours encoding I know my oc is sound :-)

although always check your videos after. I managed to encode one, but noticed a few of the scenes had artifacts on. Change the oc settings, re-ran and it was fine. Put the settings back, and got artifacts again.
 
glen8 said:
The ultimate test for me, if I can last 24 hours encoding I know my oc is sound :-)

although always check your videos after. I managed to encode one, but noticed a few of the scenes had artifacts on. Change the oc settings, re-ran and it was fine. Put the settings back, and got artifacts again.
Click to expand...

This is precisely why it's not a good stability test, because when it does error it can silently continue.

In fact, H.264 contains a certain amount of error correction (error resiliency and concealment) so errors might not even appear as artefacts when viewed.

If you can get your CPU to a state where it can pass a linpack stress test (with enough memory and AVX) but not an x264 encode I'll be very interested.
 
You must log in or register to reply here.
Back
Top Bottom