Cubase crashes then Data Execution Prevention come up

  • Thread starter Thread starter qwerty11
  • Start date Start date
Q

qwerty11

New member
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?
 
qwerty11 said:
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?
Click to expand...

Midi recording takes very liitle computer power unless you put a very heavy VSTi on it. But should still not be a problem.

It sound to me a potential hardware problem.

Put your question on the Cubase forum, maybe someone had the same problem.

Cheers
Wim
 
Is your dongle plugged in correctly? That's happened to me a couple of times and it turned out that the dongle was half out.
 
You must log in or register to reply here.
Back
Top