Crash in app using Haali splitter

We have been using the KLite codecs for a very long time (literally years) for video playback.  Very recently we have begun to have crashes that the event log reports originating with the Haali splitter (see log below).  I know that a crash report isn't much to go on but I'm hoping for any information that can direct us to a pattern.

The crash happens only when looping video for ~30 minutes or more.  The video is short (only 5 seconds) but is 'complete' as far as I know.  The video is .mp4 (there are multiple videos but all can be described similarly) and is a video we have been using for quite some time previously without problems.

Looking at what's changed:
1. We know the crashes can occur on Windows 10, as this has been reproduced.  The crash may have occurred on a Windows 7 machine but that hasn't been reproduced yet.
- We know that Windows 10 Media Center (or whatever it's called) began shipping with new codecs that have been known to cause weird results.  To the best of my knowledge, this is not installed on the problem systems.
2. We update our system with new NVidia graphics cards and currently use the GTX 960 with the latest drivers.  The graphics cards have changed, and obviously drivers are constantly changing.

We know the Haali splitter hasn't changed in quite some time.  So the problem is using it in a new system.

What I hope to get out of all this:
1. Has anyone experienced crashes on Windows 10 that can be traced to the Haali splitter?
2.  Is there a simple test that can be made to test the Haali splitter on a looping video so we can test if it's Haali by itself or a combination with something else?
3. Has anyone experienced crashes with the GTX 960 or any of the latest Nvidia cards?  Are they 'known' to have problems?
4.  Does anything else jump out?  A lot of the time it's knowing where to look that make the difference.

Below is the crash log.  Thanks for any help!

Log Name:      Application
Source:        Application Error
Date:          3/2/2016 3:49:48 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-VM5T1E8
Description:
Faulting application name: MyApp.exe, version: 5.0.0.30, time stamp: 0x56d73761
Faulting module name: splitter.ax, version: 1.13.138.14, time stamp: 0x516a7e40
Exception code: 0xc0000005
Fault offset: 0x00018707
Faulting process id: 0xa70
Faulting application start time: 0x01d174c250d015b9
Faulting application path: C:\Program Files (x86)\XXX\XXX5\MyApp.exe
Faulting module path: C:\Program Files (x86)\K-Lite Codec Pack\Filters\Haali\splitter.ax
Report Id: 7b167b96-1d28-45c2-b80a-1ada45d09c62
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
   <Provider Name="Application Error" />
   <EventID Qualifiers="0">1000</EventID>
   <Level>2</Level>
   <Task>100</Task>
   <Keywords>0x80000000000000</Keywords>
   <TimeCreated SystemTime="2016-03-02T20:49:48.000000000Z" />
   <EventRecordID>12766</EventRecordID>
   <Channel>Application</Channel>
   <Computer>DESKTOP-VM5T1E8</Computer>
   <Security />
 </System>
 <EventData>
   <Data>MyApp.exe</Data>
   <Data>5.0.0.30</Data>
   <Data>56d73761</Data>
   <Data>splitter.ax</Data>
   <Data>1.13.138.14</Data>
   <Data>516a7e40</Data>
   <Data>c0000005</Data>
   <Data>00018707</Data>
   <Data>a70</Data>
   <Data>01d174c250d015b9</Data>
   <Data>C:\Program Files (x86)\XXX\XXX5\MyApp.exe</Data>
   <Data>C:\Program Files (x86)\K-Lite Codec Pack\Filters\Haali\splitter.ax</Data>
   <Data>7b167b96-1d28-45c2-b80a-1ada45d09c62</Data>
   <Data>
   </Data>
   <Data>
   </Data>
 </EventData>
</Event>

Why aren't you using LAV Splitter? That is what the codec pack uses by default.

I don't know how recently we've tested it, but that last time we tried it it we weren't able to seek accurately enough or grab frames properly from the LAV filters. There were also some reliability issues. If that has been improved, I will recommend looking at it again.

We are trying out the latest release of the LAV filters right now, to see if they will work as a replacement for what we have been using.

Thanks.

It looks like the LAV splitter will work for us. Thanks for attention and keep up the good work!

Development of Haali Splitter was stopped a few years ago. So any problem you have with that won't be fixed.

LAV Splitter is actively maintained and very reliable. If you do encounter a file it has troubles with, just come here with a sample and I will get it fixed.