logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
rman0268  
#1 Posted : Tuesday, July 28, 2020 12:45:15 AM(UTC)
rman0268

Rank: Newbie

Groups: Registered
Joined: 7/28/2020(UTC)
Posts: 3
United States
Location: Birmingham, AL

Hello Forum,

I have had this issue for the past two Sundays. vMix is running with no issues send a record fead to an internal HD, a stream to FB and a stream to YouTube. Without any warning the program just shuts down. Last Sunday it was late enough in the service that I did not restart. This Sunday I was able to restart the program and restart all three feeds very quickly.

Any idea what could be happening? Are there error logs somewhere that I can access?

My PC is a Dell XPS i7 with an NVIDIA GC. Not exactly sure about the ram. I am capturing video from two sources, an HDMI-USB using an external capture device and we just installed a black-magic SDI capture card for our Marshall PTZ camera.

Any help or advice would be greatly appreciated.

Randy Mann
admin  
#2 Posted : Tuesday, July 28, 2020 2:11:22 AM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 5,137
Man
Location: Gold Coast, Australia

Was thanked: 4135 time(s) in 1487 post(s)
Hi Randy,

Please drop us an email and send a support report (as described below after selecting Technical Support) to help us investigate this issue:

https://www.vmix.com/contact-us.aspx

Regards,

Martin
vMix
emmy92  
#3 Posted : Monday, November 23, 2020 3:08:15 AM(UTC)
emmy92

Rank: Newbie

Groups: Registered
Joined: 11/23/2020(UTC)
Posts: 2
Romania
Location: Cluj Napoca

I have the same issue. Happened once yesterday and twice today. If you manged to solve the problem, please post here. Tanks
twokingsfilms  
#4 Posted : Tuesday, November 24, 2020 8:39:46 AM(UTC)
twokingsfilms

Rank: Member

Groups: Registered
Joined: 5/19/2020(UTC)
Posts: 23
United States

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
I've experienced this over 10 times in the past few months. After speaking with Martin a few times via email, it appears that sometimes this issue is called by an unknown issue involving NDI sources. Does your project use NDI inputs?
rman0268  
#5 Posted : Tuesday, November 24, 2020 10:42:45 AM(UTC)
rman0268

Rank: Newbie

Groups: Registered
Joined: 7/28/2020(UTC)
Posts: 3
United States
Location: Birmingham, AL

Sorry I never updated. I logged a ticket with vMix support and sent in my logs. Turns out one of my NDI sources was causing the issue. Updated all NDI software on all devices to the latest version. I have not had the shutting down issue since.

Hope this helps.

Randy
niemi  
#6 Posted : Wednesday, November 25, 2020 8:36:37 AM(UTC)
niemi

Rank: Advanced Member

Groups: Registered
Joined: 2/16/2017(UTC)
Posts: 178
Location: Denmark

Thanks: 27 times
Was thanked: 18 time(s) in 15 post(s)
Originally Posted by: rman0268 Go to Quoted Post
Sorry I never updated. I logged a ticket with vMix support and sent in my logs. Turns out one of my NDI sources was causing the issue. Updated all NDI software on all devices to the latest version. I have not had the shutting down issue since.

Hope this helps.

Randy


Which NDI source caused vMix to shut down?
thanks 1 user thanked niemi for this useful post.
Switch on 7/30/2023(UTC)
rman0268  
#7 Posted : Wednesday, November 25, 2020 10:04:23 PM(UTC)
rman0268

Rank: Newbie

Groups: Registered
Joined: 7/28/2020(UTC)
Posts: 3
United States
Location: Birmingham, AL

Not sure. Our network wasn’t fast enough to support our PTZ camera feed so we moved it to SDI.

We still occasionally control the e camera via NDI though. The only other NDI source we are using is the PP7 pc.

Hope that helps.
RJF  
#8 Posted : Thursday, November 26, 2020 1:57:58 AM(UTC)
RJF

Rank: Member

Groups: Registered
Joined: 12/4/2016(UTC)
Posts: 16
Man
France
Location: Strasbourg

Thanks: 3 times
Hi !

vMix shut down unexpectedly (NO warning !) 2 times with in some few hours on monday during stream and today when I was testing the system doing a stream on restream (with H264 1080p 6mbps AAc 128 kbps CBR).
We are using NDI :
-8 NDI inputs from Microsoft Teams from a Lan PC
-1 NDI input from vMix desktop Capture - another LAN PC (using Zoom)
-1 NDI feed from a third LAN PCs using another zoom session team (receiving 8 inputs from). On


I have last version of Windows 10 - 20H2 - verison 19042.630 - Windows Feature Experience Pack 120.2212.31.0

- twice has to do with Windows.Storage.Search.dll
- 1 with cbfsMntNtf5.dll
- 1 with ntshrui.dll
- 1 with ntdll.dll


Also had this "Event ID 642 ESENT error" from Windows that I repaired 2 days ago thanks to this article : https://www.thewindowscl...sent-error-on-windows-10
Below copy of xml files of all errors I have these last days

Thank you
Etienne



Nom du journal :Application
Source : Application Error
Date : 25/11/2020 16:14:40
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : Screen1
Description :
Nom de l’application défaillante vMix64.exe, version : 23.0.0.66, horodatage : 0x5fa393f2
Nom du module défaillant : Windows.Storage.Search.dll, version : 6.2.19041.546, horodatage : 0xbdc7aa5d
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000034c55
ID du processus défaillant : 0x%9
Heure de début de l’application défaillante : 0x%10
Chemin d’accès de l’application défaillante : %11
Chemin d’accès du module défaillant: %12
ID de rapport : %13
Nom complet du package défaillant : %14
ID de l’application relative au package défaillant : %15
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-25T15:14:40.6756568Z" />
<EventRecordID>4608</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Screen1</Computer>
<Security />
</System>
<EventData>
<Data>vMix64.exe</Data>
<Data>23.0.0.66</Data>
<Data>5fa393f2</Data>
<Data>Windows.Storage.Search.dll</Data>
<Data>6.2.19041.546</Data>
<Data>bdc7aa5d</Data>
<Data>c0000005</Data>
<Data>0000000000034c55</Data>
</EventData>
</Event>



Nom du journal :Application
Source : Application Error
Date : 23/11/2020 22:25:37
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : Screen1
Description :
Nom de l’application défaillante vMix64.exe, version : 23.0.0.66, horodatage : 0x5fa393f2
Nom du module défaillant : ntshrui.dll, version : 6.2.19041.610, horodatage : 0x80fd59b2
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000001215f
ID du processus défaillant : 0x%9
Heure de début de l’application défaillante : 0x%10
Chemin d’accès de l’application défaillante : %11
Chemin d’accès du module défaillant: %12
ID de rapport : %13
Nom complet du package défaillant : %14
ID de l’application relative au package défaillant : %15
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-23T21:25:37.2636643Z" />
<EventRecordID>4292</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Screen1</Computer>
<Security />
</System>
<EventData>
<Data>vMix64.exe</Data>
<Data>23.0.0.66</Data>
<Data>5fa393f2</Data>
<Data>ntshrui.dll</Data>
<Data>6.2.19041.610</Data>
<Data>80fd59b2</Data>
<Data>c0000005</Data>
<Data>000000000001215f</Data>
</EventData>
</Event>



Nom du journal :Application
Source : Application Error
Date : 23/11/2020 19:56:30
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : Screen1
Description :
Nom de l’application défaillante vMix64.exe, version : 23.0.0.66, horodatage : 0x5fa393f2
Nom du module défaillant : cbfsMntNtf5.dll, version : 5.1.164.296, horodatage : 0x5610fdfd
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000001d9b1
ID du processus défaillant : 0x%9
Heure de début de l’application défaillante : 0x%10
Chemin d’accès de l’application défaillante : %11
Chemin d’accès du module défaillant: %12
ID de rapport : %13
Nom complet du package défaillant : %14
ID de l’application relative au package défaillant : %15
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-23T18:56:30.1625481Z" />
<EventRecordID>4228</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Screen1</Computer>
<Security />
</System>
<EventData>
<Data>vMix64.exe</Data>
<Data>23.0.0.66</Data>
<Data>5fa393f2</Data>
<Data>cbfsMntNtf5.dll</Data>
<Data>5.1.164.296</Data>
<Data>5610fdfd</Data>
<Data>c0000005</Data>
<Data>000000000001d9b1</Data>
</EventData>
</Event>



Nom du journal :Application
Source : Application Error
Date : 21/11/2020 02:54:54
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : Screen1
Description :
Nom de l’application défaillante vMix64.exe, version : 23.0.0.66, horodatage : 0x5fa393f2
Nom du module défaillant : Windows.Storage.Search.dll, version : 6.2.19041.546, horodatage : 0xbdc7aa5d
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000034c55
ID du processus défaillant : 0x%9
Heure de début de l’application défaillante : 0x%10
Chemin d’accès de l’application défaillante : %11
Chemin d’accès du module défaillant: %12
ID de rapport : %13
Nom complet du package défaillant : %14
ID de l’application relative au package défaillant : %15
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-21T01:54:54.7380181Z" />
<EventRecordID>3398</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Screen1</Computer>
<Security />
</System>
<EventData>
<Data>vMix64.exe</Data>
<Data>23.0.0.66</Data>
<Data>5fa393f2</Data>
<Data>Windows.Storage.Search.dll</Data>
<Data>6.2.19041.546</Data>
<Data>bdc7aa5d</Data>
<Data>c0000005</Data>
<Data>0000000000034c55</Data>
</EventData>
</Event>



Nom du journal :Application
Source : Application Error
Date : 20/11/2020 16:12:59
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : Screen1
Description :
Nom de l’application défaillante vMixNDIHelper.exe, version : 5.0.0.1, horodatage : 0x5e2947f2
Nom du module défaillant : ntdll.dll, version : 10.0.19041.610, horodatage : 0xe5d7ed5c
Code d’exception : 0xc0000374
Décalage d’erreur : 0x00000000000fed29
ID du processus défaillant : 0x12c4
Heure de début de l’application défaillante : 0x01d6bf4bfa93b4ab
Chemin d’accès de l’application défaillante : C:\Program Files (x86)\vMix\ndi\vMixNDIHelper.exe
Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\ntdll.dll
ID de rapport : 7a551efd-6e12-475c-a0c2-aa41162740cb
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-20T15:12:59.0941526Z" />
<EventRecordID>3346</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Screen1</Computer>
<Security />
</System>
<EventData>
<Data>vMixNDIHelper.exe</Data>
<Data>5.0.0.1</Data>
<Data>5e2947f2</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.610</Data>
<Data>e5d7ed5c</Data>
<Data>c0000374</Data>
<Data>00000000000fed29</Data>
<Data>12c4</Data>
<Data>01d6bf4bfa93b4ab</Data>
<Data>C:\Program Files (x86)\vMix\ndi\vMixNDIHelper.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>7a551efd-6e12-475c-a0c2-aa41162740cb</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
RJF  
#9 Posted : Saturday, November 28, 2020 11:01:54 PM(UTC)
RJF

Rank: Member

Groups: Registered
Joined: 12/4/2016(UTC)
Posts: 16
Man
France
Location: Strasbourg

Thanks: 3 times
Hi all,

Received a quick answer from Martin per email.
All problems solved : vmix rock stable now ! :-)
Big thanks
About "Event ID 642 ESENT error" (or other numbers) which is related to the last Windows update to version 2004, there's a fix here :
https://thegeekpage.com/...ent-error-in-windows-10/
spino  
#10 Posted : Sunday, November 29, 2020 5:08:08 PM(UTC)
spino

Rank: Advanced Member

Groups: Registered
Joined: 12/20/2016(UTC)
Posts: 179
Man
Italy
Location: Milano

Was thanked: 21 time(s) in 13 post(s)
Originally Posted by: RJF Go to Quoted Post
Hi all,

Received a quick answer from Martin per email.
All problems solved : vmix rock stable now ! :-)




How?

emmy92  
#11 Posted : Sunday, November 29, 2020 7:16:48 PM(UTC)
emmy92

Rank: Newbie

Groups: Registered
Joined: 11/23/2020(UTC)
Posts: 2
Romania
Location: Cluj Napoca

I use VMIX Desktop Capture on two other computer as sources. Updated them both and so far all good
cendrick  
#12 Posted : Monday, November 30, 2020 9:53:04 AM(UTC)
cendrick

Rank: Newbie

Groups: Registered
Joined: 11/29/2020(UTC)
Posts: 1
United States
Location: Kentucky

Originally Posted by: RJF Go to Quoted Post
Hi all,

Received a quick answer from Martin per email.
All problems solved : vmix rock stable now ! :-)
Big thanks
About "Event ID 642 ESENT error" (or other numbers) which is related to the last Windows update to version 2004, there's a fix here :
https://thegeekpage.com/...ent-error-in-windows-10/


Yes, please tell us what solved your case? Would love to have a log on this in case I need it in the future...Thank You!
RJF  
#13 Posted : Friday, December 11, 2020 8:38:28 AM(UTC)
RJF

Rank: Member

Groups: Registered
Joined: 12/4/2016(UTC)
Posts: 16
Man
France
Location: Strasbourg

Thanks: 3 times
Hi !

I think this was mere due to corrupt Windows install (I updated from a 3 years old version to the last one : 20H2)
The point is when you update windows, you should too update your drivers to the last version (use Driver Booster for example : https://www.iobit.com/fr/driver-booster.php)
I also had some few problems with "Intel Rapid Storage" : I uninstalled and put the last version too.

Also because I'm using a lot NDI through my LAN with different laptops, I unintalled all "old versions" of Newtek NDI Tools and re-installed the last version (v4.5 : https://ndi.tv/tools/#download-tools) on ALL computers in my LAN.
In vMix, I uninstalled also all VST3 plugins to be sure they couldn't create conflicts.


Below is the answer Martin sent to me (per email). I'm very thankfull especially he answered very quickly (was a bit desperate) and gave some methods to solve my problem.


"A few things you can try:

1. If it happens consistently, run vMix with different inputs removed until you can narrow down the cause.
2. Check for Windows Updates and also driver updates for things like the graphics card.
3. If it has happened recently, see if any recent programs have been installed and uninstall them to see if it helps.
4. Close any other open programs, especially any that interface with vMix (such as Companion or StreamDeck) to see if these are the cause.

The above steps are not permanent suggestions, but merely to track down the cause, once the cause is known we can take it from there.
If all else fails, you may be looking at faulty hardware, in which case the following steps are advised:

1. Run Windows Memory Diagnostic in the start menu to check for memory errors.
2. Run FurMark to check for faulty graphics card:
https://geeks3d.com/furmark/
3. Run CoreTemp to see if there is a CPU fan issue causing overheating:
https://www.alcpu.com/CoreTemp/ (more than 80 degrees Celsius on a Desktop indicates a cooling issue)
4. Windows may need to be reinstalled in case some components have become corrupt."
caspy  
#14 Posted : Friday, December 11, 2020 8:39:22 AM(UTC)
caspy

Rank: Member

Groups: Registered
Joined: 6/29/2020(UTC)
Posts: 16
Russian Federation
Location: Moscow

Was thanked: 1 time(s) in 1 post(s)
Originally Posted by: RJF Go to Quoted Post
Hi all,

Received a quick answer from Martin per email.
All problems solved : vmix rock stable now ! :-)
Big thanks
About "Event ID 642 ESENT error" (or other numbers) which is related to the last Windows update to version 2004, there's a fix here :
https://thegeekpage.com/...ent-error-in-windows-10/


Could you please share details?
There seems to be a large number of users with the same trouble.
videokadr  
#15 Posted : Tuesday, February 16, 2021 11:21:00 PM(UTC)
videokadr

Rank: Newbie

Groups: Registered
Joined: 2/16/2015(UTC)
Posts: 6
Man
Location: Poland


I had the same symptom. One Macbook source with NDI signal was connected to the project via the network. Vmix crashed 2 times without any warning. I think the Macbook is the cause.
The Macbook has a downside. I've been working with PC source via NDI for a very long time and it has never happened to me. I plugged in first time Macbook and it's "NASA we have a big problem".
videokadr  
#16 Posted : Thursday, February 18, 2021 4:27:54 AM(UTC)
videokadr

Rank: Newbie

Groups: Registered
Joined: 2/16/2015(UTC)
Posts: 6
Man
Location: Poland


I'm sure this is a problem with the Macbook connected via NDI.
Today there were 2 PC laptops connected via NDI, for several hours, Vmix worked very stably.
The problem is with Macbook who do not have a j45 socket, you need to use some adapters that can cause problems or exacerbate them.
Never ever connect any bad Macbooks via NDI, it causes problems.
Vince Beck  
#17 Posted : Thursday, February 18, 2021 6:16:54 AM(UTC)
Vince Beck

Rank: Advanced Member

Groups: Registered
Joined: 7/28/2019(UTC)
Posts: 351
United States
Location: Santa Rosa

Thanks: 1 times
Was thanked: 51 time(s) in 51 post(s)
We've done it in the past succesfully. You really want to use a dock like the Caldigit TF3, forget dongles.

The biggest issue with the Macbook Pro is that they overheat easy, so your 3Ghz CPU turns into a 2 Ghz CPU really fast once it's throttling.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.