Vienna Symphonic Library Forum
Forum Statistics

199,039 users have contributed to 43,151 threads and 258,882 posts.

In the past 24 hours, we have 6 new thread(s), 14 new post(s) and 63 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. [SOLVED] Vienna Ensemble Pro 5 Crashes when connecting to DAW

  • [SOLVED] Vienna Ensemble Pro 5 Crashes when connecting to DAW

    E
    E

    Hey Everyone, 

    I have an issue that didn't exist until I moved my desk and reconnected everything. I have 2 slave windows 7 computers and my main sequencer 2013 mac pro running DP 9. One slave machine connects fine while the other crashes VE PRO. The crash log is below. Any thoughts?

    Problem signature:

      Problem Event Name:BEX64

      Application Name:Vienna Ensemble Pro x64.exe

      Application Version:5.4.0.13741

      Application Timestamp:5541fe55

      Fault Module Name:Kontakt 5.dll

      Fault Module Version:5.5.1.451

      Fault Module Timestamp:55688699

      Exception Offset:00000000001faa6a

      Exception Code:c0000409

      Exception Data:0000000000000000

      OS Version:6.1.7601.2.1.0.256.48

      Locale ID:1033

      Additional Information 1:9819

      Additional Information 2:9819410204c3e16a283a5c642f9bbd93

      Additional Information 3:21fe

      Additional Information 4:21fec6d60b5d67f31de13c53ee99ccbe

     

    Read our privacy statement online:

      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

     

    If the online privacy statement is not available, please read our privacy statement offline:

      C:\Windows\system32\en-US\erofflps.txt
  • PaulP
    VSL Team
    PaulP

    Hi Elvis, 

    The log points to Kontakt, clearly: 

    Fault Module Name:Kontakt 5.dll

    Best,
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • E
    E

    Thanks Paul, 

    I got it working just fine. I copied the kontakt dll vsts within Program Files/Native Instruments/VST Plugins 64 from the working slave computer and pasted them in the corresponding file directory on the corrupted non wokring slave computer. Everything worked well. I don't know what got corrupted but I hope this helps anyone with similar problems.