Handbrake: Handbrake Crashing on creators update?

Created on 7 Apr 2017  路  8Comments  路  Source: HandBrake/HandBrake

Please describe the problem or feature request in detail:

When opening handbrake and having nothing in it everything seems to work fine, after i add a file and want to add it to queue and then show queue it crashes.

i've tried converting file's just letting it go and not showing the que and it works but after 10-20 sec if i switch to a browser handbrake crashes.

What are the steps to reproduce this problem:

1st way add file and add to queue then press show queue

2nd way add a file to convert, select preset and press start, wait 20-30 sec, then switch the focused screen from handbrake a browser or program.

What version of HandBrake you are running:

1.0.3 and i tried nightly 20170405

What operating system and version and you running (e.g. OSX 10.11, Windows 7, Ubuntu 14):

windows 10 pro 64 bit Creators update ( 1703 / 15063.13)

Was there any error message or error dialog, if so please detail or provide screenshots:

no just windows reporting that it crashed.

Please provide the full activity log for the encode or scan attempt. You may attach the log as a file, post a pastebin URL to the log, or place the log inline below:

activity log : https://pastebin.com/pvqBVBXE

i was also able to find these in windows event viewer :

Application: HandBrake.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFE7E6BFD0C

and this one :

Faulting application name: HandBrake.exe, version: 1.0.3.0, time stamp: 0x58b202c6
Faulting module name: d3d9.dll, version: 10.0.15063.0, time stamp: 0x631de416
Exception code: 0xc0000005
Fault offset: 0x000000000000fd0c
Faulting process id: 0xdc
Faulting application start time: 0x01d2af958e3fbd0d
Faulting application path: C:\Program Files\HandBrake\HandBrake.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: f406a378-771d-457b-81e8-81cb9d37e443
Faulting package full name:
Faulting package-relative application ID:

Invalid or Not Supported

Most helpful comment

Another user on our forum reported the same thing. Except rivatuner was also affecting it.

It would appear GPU monitoring applications are triggering many applications to fail with an error message such as this.

All 8 comments

Looks like it's crashing in Direct3D. Could be a system issue. We'll take a look, but in the meantime, try updating your graphics drivers and DirectX if they aren't current.

driverwise this happend on the nvidia geforce 378.92 drivers that came with the creators update and the 381.65 drivers recently released.

direct X wise for windows 10 it seems to be windows update or nada,direct-X end user runtime didn't install anything

Unfortunately something graphics related is broken on your system.

A quick google of the error code turns up quite a few going back several years with other applications. There may be solutions out there if you google the exception code with the d3d9.dll filename.

If it's happening when opening the queue window without an encode even running it's not a good sign. My guess is there is a pretty bad driver bug or something got corrupted on your system during the update.

Since this isn't a HandBrake bug, I'll close this off for now, however if yourself or anyone else does see this, please feel free to report back. Especially if you find a solution!

I should have added, I have this running on Creators update without issue, so I suspect that's not the root of the issue.

well i ran sfc /scannow, cleaned registry with CC cleaner and disabled my av as per the usual fixes for 0xc0000005 atleast as far as i could find still nothing, guess i'll just wait for windows update or a clean install to fix whatever got borked by the upgrade.

edit: i do not know how... i do not know why but it was MSI Afterburner, turned it off and handbrake works flawlessly

Another user on our forum reported the same thing. Except rivatuner was also affecting it.

It would appear GPU monitoring applications are triggering many applications to fail with an error message such as this.

More specifically it is the RTSS program and its OSD monitoring that causes the inability to launch Handbrake, MSI Afterburner itself works fine with HB. If you are using RTSS, make sure to either turn off global application detection, or add Handbrake to the list and turn off detection.

Can confirm Rivatuner after Windows 10 Creators Update. My graphics card is a GTX 1070. Adding HandBrake to Rivaturners exclude list fixes the issue.

Event 1026, .NET Runtime

Application: HandBrake.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF86E8EFD0C

Event 1000, Application Error

Faulting application name: HandBrake.exe, version: 1.0.7.0, time stamp: 0x58ea9d2f
Faulting module name: d3d9.dll, version: 10.0.15063.0, time stamp: 0x631de416
Exception code: 0xc0000005
Fault offset: 0x000000000000fd0c
Faulting process id: 0x29f8
Faulting application start time: 0x01d2ba03eb348df1
Faulting application path: C:\Program Files\HandBrake\HandBrake.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: 8400a524-56ea-4d91-b0dc-7da94a92c773
Faulting package full name: 
Faulting package-relative application ID: 
Was this page helpful?
0 / 5 - 0 ratings