1. Register NOW and become part of this fantastic knowledge base forum! This message will go away once you have registered.

Cubase crashes then Data Execution Prevention come up

Discussion in 'Cubase' started by qwerty11, Jul 14, 2009.

  1. qwerty11

    qwerty11 Guest

    So I have had multiple cubase crashing problems. I decided to just go on an reformat the brand new computer and start over with a clean slate. So I did.

    I installed all the updates for everything and took off recording. Well as soon as I started recording MIDI through my Tascam US 144 after about 5 beats the recording part just took off. It went from 200 beats to 800 in a fraction of a second. Then it crashed.

    A nice little message came up saying cubase needs to close. When I clicked close a bubble came up in the bottom right hand corner saying Windows Data Execution Prevention was activated and killed the program. So I went into the Data Execution Prevention tab and turned off DEP for Cubase. I started cubase over and it crashed again with the same message.

    Any Ideas?a
  2. TheJackAttack

    TheJackAttack Distinguished Member

    Well I'd say it's related to the MIDI feature. To make sure stick a mic on your tv speaker and record long enough to tell if Cubase crashes.

    What is your OS, CPU, RAM, external HDD?
  3. qwerty11

    qwerty11 Guest

    Vista 64
    Intel Duel Core 7400
    4gb ram
    500 gb external.

    I'm wandering if the Tascam is faulty.

    I am using a Triton keyboard.
  4. TheJackAttack

    TheJackAttack Distinguished Member

    I guess it is too obvious to ask if you have the 1.12 firmware update installed....
  5. qwerty11

    qwerty11 Guest

    Yea everything is updated
  6. TheJackAttack

    TheJackAttack Distinguished Member

    Have you tried recording just a microphone or just MIDI? If things crash with a mic input same as MIDI you might indeed have a faulty unit.

    Also, another longshot, what about the BIOS on your mobo? Even new computers don't always ship with the latest versions.

    When I have encountered DEP errors I have often not bothered to find them. I have usually just reformatted the machine. It's been about six years since a machine I've maintained displayed one though and that had to do with a botched dot net update.
  7. Contact your Steinberg distributor and they'll advise you what to do. I live in Canada and SB Canada have given me awesome support by email or phone.
  8. TheJackAttack

    TheJackAttack Distinguished Member

    DEP errors wouldn't have anything to do with Cubase I don't imagine. Usually they result from user error in tweaking system settings and services and the occasional botched driver install.

    Of course I could be wrong and it really is some conflict with Cubase but I an doubtful.
  9. djmukilteo

    djmukilteo Well-Known Member

    Just a thought...but I have seen MIDI stack overflows cause crashes like that....whats happening is the MIDI buffer isn't being emptied fast enough to keep up and locks up when it's full.....typically this happens with poorly written drivers from the interface...try disconnecting the MIDI and see if it records normally
  10. Space

    Space Well-Known Member

    "I decided to just go on an reformat the brand new computer and start over with a clean slate. "

    I think there is more going on here then you(OP) are telling about. A dep error is the OS you are using telling you that something is being executed in a memory area not used for executable data.

    "The primary benefit of DEP is it helps block a class of security intrusions. Specifically, DEP can help block a malicious program in which a virus or other type of attack has injected a process with additional code and then tries to run the injected code."

    The Tascam comes bundled with Cubase. Sure that every possible computer configuration can not have been tested, you may have a unique situation.

    I wonder if the axiom "loose nut on the keyboard" applies to this issue?

    Edit: Midi is a master and slave relationship.

Share This Page