virb edit 5.1.0 crashing

Former Member
Former Member
Just updated to virb edit 5.1.0 and tried to edit a 360 video. Virb edit crashes immediately when trying to create a video or do a playpack. Gives error VIRM edit has stopped working. Event log has this after crash.

Faulting application name: VirbEdit.exe, version: 5.1.0.0, time stamp: 0x59308ae5
Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xa82cc161
Exception code: 0xc0000374
Fault offset: 0x000d9a8a
Faulting process id: 0x15f0
Faulting application start time: 0x01d2dc6c4db73e5d
Faulting application path: C:\Program Files (x86)\Garmin\VIRB Edit\VirbEdit.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ee32a7dd-c994-47f6-a223-0ab51c644568
Faulting package full name:
Faulting package-relative application ID:

Any idea what is causing? Newly installed MSI Trident 3 PC with Windows 10

br,

-Mika
  • I owe you a crash report:
    My Edit crashes after importing some files. G-Metrix are fine, 1-2 Clips also, then after less percent of optimization 1 or 2 % it crashes.

    Anwendung: VirbEdit.exe
    Frameworkversion: v4.0.30319
    Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
    Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 1A0E1188


    Name der fehlerhaften Anwendung: VirbEdit.exe, Version: 5.1.0.0, Zeitstempel: 0x59308ae5
    Name des fehlerhaften Moduls: mfx_mft_h264ve_32.dll, Version: 6.15.6.2, Zeitstempel: 0x556d7255
    Ausnahmecode: 0xc0000005
    Fehleroffset: 0x00051188
    ID des fehlerhaften Prozesses: 0x1a2c
    Startzeit der fehlerhaften Anwendung: 0x01d2dd3c3f9111f1
    Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Garmin\VIRB Edit\VirbEdit.exe
    Pfad des fehlerhaften Moduls: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll
    Berichtskennung: e29f6fd1-248c-4182-ae28-850dcfd1a2e5
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


    Sorry, but I only have them in german.
    It is easily repeatable: I just have to import more then 2 clips at once.
  • Maps gone

    5.1.0 Is a disaster for my system. Gone back to 4.2.3 which always worked well. Now my complete video database will no longer show google or bing maps, great for setting start times for laps. Anyway to undo the database upgrade that was done?
  • Maps Back! Yeah

    5.1.0 Is a disaster for my system. Gone back to 4.2.3 which always worked well. Now my complete video database will no longer show google or bing maps, great for setting start times for laps. Anyway to undo the database upgrade that was done?


    Went into control panel, add/remove programs and removed Virb Edit. Reinstalled Virb Edit 4.2.3 and the databade must have rebuilt itself??? ALL GOOD!
  • Former Member
    0 Former Member over 8 years ago
    RE: Garmin Virb Edit Crash

    @OVERMMI1
    I'm assuming you are using a Virb 360 and not some other camera like a Rico Theta or something. Did your videos import successfully from your camera into VirbEdit?

    Everyone else:
    Were your crashes / failures connected to projects created in prior versions of VirbEdit or were they new videos you created after upgrading to 5.1? Did the problems you observed occur with 2D or 360 videos? We want to get these issues figured out and fixed as soon as possible. Sorry for the rocky launch, and thank your for your help!



    Hello,

    Yes, I'm trying to import video from Nikon Keymission 360. Still waiting for my Virb 360 to arrive...;) I got things solved by uninstalling, installing the 4.23 version and then doing on upgrade within Virb Edit software. My problem was causing when installing 5.1 version as an clean installation.
  • Former Member
    0 Former Member over 8 years ago
    @Ducati1098s
    Our database upgrade process in non destructive, so if you go back to 4.2.3 your database will still be there, just like you left it.

    @OVERMMI1
    Glad to hear things are working. Usually we've found that a clean install fixes many problems rather than causing them. Thanks for the follow up info, this is good to know!
  • Hi Purdington and thanks for looking into this.

    I am using a Virb XE filming in 1080p60. All my videos are imported in previous versions of Virb Edit but that is a simple copy-file-and-add-to-database-operation right?
    Nothing is reencoded when importing from cam to Virb Edit?

    The program crashes whenever trying to playback any video, edited or just imported from the cam it doesn't matter.

    Made a backup of my database, unistalled Virb Edit and removed all files manually under C:\Users\MyUser\AppData\Local\Garmin and C:\Users\MyUser\AppData\Roaming\Garmin.
    Reinstalled Virb Edit 5.1.0 and imported my database but program still crashes.

    Have tried all the different enocders and decoders but with the same result.

    Have tried with a videofile recorded on a different cam but also with the same result.


    I have exactly the same issue, same situation with same camera.
    I have Windows7 x64 with a GTX790

    I import a video from Virb EX, video shows up in library, I create a new video, drag the video from library to time line and crash!
  • Former Member
    0 Former Member over 8 years ago
    @HerrRiebmann

    Name des fehlerhaften Moduls: mfx_mft_h264ve_32.dll, Version: 6.15.6.2, Zeitstempel: 0x556d7255

    This report indicates the crash is occurring in the Intel drivers on your machine, specifically the Intel Quicksync API. Have you tried updating your drivers directly from Intel's website?
    Also, try switching your encoder/decoder settings to ffmpeg and see if changing either or both makes a difference since ffmpeg does not use intel technology in VirbEdit.
  • Former Member
    0 Former Member over 8 years ago
    +1 crash with virb Edit 5.
    Same description of user RuiTerrinha: I import a video from Virb EX, video shows up in library, I create a new video, drag the video from library to time line and crash!
    Back to 4.2.3 all ok.
    Windows 7 64bit Gtx 550i
  • Former Member
    0 Former Member over 8 years ago
    Same issue as original post

    Mine is also crashing out when I attempt to edit a video.

    Faulting application name: VirbEdit.exe, version: 5.1.0.0, time stamp: 0x59308ae5
    Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xa82cc161
    Exception code: 0xc0000374
    Fault offset: 0x000d9a8a
    Faulting process id: 0x4678
    Faulting application start time: 0x01d2e8a7b8e3f3ca
    Faulting application path: C:\Program Files (x86)\Garmin\VIRB Edit\VirbEdit.exe
    Faulting module path: C:\windows\SYSTEM32\ntdll.dll
    Report Id: dbbf23b6-cb28-431f-8956-fc1c4064671f
    Faulting package full name:
    Faulting package-relative application ID:

    Running Windows 10 Pro x64 Version 1703 Build 15063.413
    3.6GHz Intel i7-6850K
    32GB RAM
    GTX 1080 with 382.53 drivers
    8GB Graphics RAM
    Display Resolution 2560x1600 x 2
    1.3TB of free space
  • @HerrRiebmann

    This report indicates the crash is occurring in the Intel drivers on your machine, specifically the Intel Quicksync API. Have you tried updating your drivers directly from Intel's website?
    Also, try switching your encoder/decoder settings to ffmpeg and see if changing either or both makes a difference since ffmpeg does not use intel technology in VirbEdit.


    The drivers are up to date. I´ll try another encoder and see what happens!

    [EDIT]
    Okay, changing both options to ffmpeg, make importing work again.
    Exporting makes no difference. It works with Media foundation and ffmpeg.
    Also used DXVA as a third option.

    To ensure it was related to that, I changed back to Media foundation and ta ta ta taaaaaa: Import and optimization also work! Strange, but the issue is solved by doing nothing. No windows update, no Virb Edit update... Must be black magic from Purdington on my computer ;)

    After changing everything around, I ran the system check to get the right de-/encoder. It says it was positive, but the setting did not change. So I changed it manually and restart the test. Same result: Both values stay the same.