Bug Report Just updated several plugins for OBS and now it keeps crashing

Hey so I was just prompted to download several new updates for some plugins and now OBS keeps crashing. I have a copy of the CrashLog but I don't understand why it's crashing.... It says that the crash occurred in the "nvcuvid.dll" module. What can I do to fix this? I have a streaming schedule set up and I'm kinda worried this is going to keep me off it. I've never experienced a crash in OBS that couldn't be fixed with running as admin but even that crashes too...
 

R1CH

Forum Admin
Developer
Make sure your video drivers are up to date, as the NVENC code was updated to require more recent driver versions.
 
/start CrashLog
OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.

This crash appears to have occured in the 'c:\windows\system32\nvcuvid.dll' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 66EFA9C4 (c:\windows\system32\nvcuvid.dll)
OBS version: Open Broadcaster Software v0.63b
Windows version: 6.2 (Build 9200)
CPU: Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
00CDDB04 66EFA9C4 00000000 0D6ECDA0 180A8108 00CDF3AC nvcuvid.dll!0x66efa9c4
00CDDB08 66E805BF 180A65C8 00000000 18FD28AC 18FD28A8 nvcuvid.dll!0x66e805bf
00CDDB40 66E86524 00000000 180A7AD8 75741D00 00000000 nvcuvid.dll!0x66e86524
00CDDB68 66E7F0D7 180A7AD8 75741D00 00000000 40200200 nvcuvid.dll!0x66e7f0d7

A minidump was saved to C:\Users\Mike\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-09-08_3.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module
/end CrashLog

So I'm going to make sure they are up to date as well. Hopefully, it's not as simple as that.
 
Yeah... It was the new update for my Nvidia driver... I'm fine... I think it would be really cool if there was a statement saying that the NVENC needed updated drivers, I would have looked for that update then.... Oh well. Problem solved.
 
Top