Vienna Symphonic Library Forum
Forum Statistics

195,311 users have contributed to 42,976 threads and 258,204 posts.

In the past 24 hours, we have 1 new thread(s), 10 new post(s) and 66 new user(s).

  • 64bit Ensemble crashes PC....HELP

    Hi all.....64bit Ensemble crashes PC....HELP...........Blue screen of death with text saying Physical Memory Dump.........Every morning it does this....And after about 2 to 5 computer restarts (1 hour ++) it will kick in and work........any tweaks I need to perform to XP64bit?....what do I do...thanx. (I'm speaking of stand-alone) AND.........I have a Dakota Card and it has 2 midi ports......Ensemble sometimes "drops" 1 OR both of the ports....I suspect this all has to do with tweaks that need to be performed to XPpro 64 someone PLEASE help me. SvK

  • I'm running 2QuadCore@2.66Ghz with 8 gig RAm XP64 proffessional. Dakota soundcard for Audio/Midi SvK

  • svk,

    I'm running VE on XP64 with Frontier WaveCenter PCI cards -- which I suppose would have similar drivers to your Dakota. I've found that if I tried to launch VE 64 bit version, I would get a crash everytime with a mem dump having to do with the Frontier drivers.

    This might work for you/it might not.... but try it if you havent'. Launch an instance of VE 32 bit first, then close it and launch the VE 64 bit. That solved my crashes. But I have to launch the 32 bit at least one time after booting the computer. After that, I can just launch the 64 bit.

    I've sent an email with the mem dump attached to Frontier Design tech support, but have never heard back from them. If this solution works for you, you might send them an email with your memory dump attached.

    Hope it helps,

    Mahlon


  • AFAIK, BSOD is a driver related problem. The first thing to do is check that you have the latest driver for the soundcard.

    DG


  • Mahlon.....will try...thanx....SvK

  • Mahlon... A completely seperate issue: After a while the MIDI (using dakota midi) stops working...SvK

  • Hi DG.....what about NO MIDI after 3 gig? thanx SvK

  • the bluescreen should tell a few relevant informations (error type and number as well as some addresses), the memory dump is a little bit hard to read, a drwatson log would be easier to scan for the origin of the bluescreen (if the machine had the time to write something to a log).

     

    often the reason is a *IRQ not less or equal* wich would point to a driver or device error (sometimes only colliding drivers for different devices)

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • last edited
    last edited

    @svonkampen said:

    Hi DG.....what about NO MIDI after 3 gig? thanx SvK

    Unless it's the bug that Paul was talking about on the other, other thread, I'm not sure. It sounds like there is something 32bit in the chain causing a problem, but why is should stop at 3GB, rather than 4GB, I don't know. I think some other users had problem with a soundcard software mixer that was a 32bit plug, but it all seems rather convoluted to me. I have zero problems, but then again I have no soundcard. Sorry not to be of more help.

    DG

  • Stephen, were you able to look at the text on the blue screen when the memory dump happens? It will often have the culprit for crash. In my case, wcpci.dll (IIRC) was the problem. At least that might let you know if it's a video card or soundcard problem.

    Still haven't heard back from them. But with VE3 coming maybe I won't have to.

    Best,[pi]
    Mahlon


  • http://frontierdesign.com/Products/Dakota

    I couldn't find anywhere that the drivers have been updated for 64bit.


  • last edited
    last edited

    @Peter Alexander said:

    http://frontierdesign.com/Products/Dakota

    I couldn't find anywhere that the drivers have been updated for 64bit.

    Peter,

    I believe they should be here: http://www.frontierdesign.com/Products/Dakota/Downloads

    Steven,

    Which build of VE are you using? I remember having problems with midi not responding for which I was kindly offered a fix from VSL. Some of this is documented by rgames as well in this thread: http://community.vsl.co.at/forums/t/17408.aspx and here http://community.vsl.co.at/forums/t/17546.aspx

    In my case (and since we're both using FrontierDesign drivers, it may apply to you), the BSOD crashes were unrelated to the "midi not responding".  Or at least as far as I could tell. Perhaps ask Paul about it, and mention my delimna of about 6 weeks ago.

    Mahlon