Kore 1.0.2 crashes with NTDLL.DLL

Overloading the CPU of 55-60%, the system crashes with Microsoft classic windows error: This program has been stopped....
The event viewer reports that the error is caused by KORE.EXE 1.0.2.6 in confict with NTDLL.DLL.

The PC is powerful, I think enough RAM and CPU, well optimized to me. No latency, no waits inside Kore or other software, everything runs fast.
Is it possible I cannot load more than 1 VST (sometimes 2) and keep them active in the same time, otherwise the system uses too much CPU and crashes...???

My gear:
HP DC7600 Intel Dual Core 2 x 3.0 GHz, 2 GB ram, 2 x 250 GB hd 7200 rpm s-ata 3.

 

Welcome

I'd think there's something else going on to be honest; I run at 90% CPU with KORE quite often on my 3500+, but that's also four instances of Reaktor, two of Absynth and a number of effects that I'm running to get there...

ew

 

hallo,
i also have this problem...it sucks!
what can be the reason? my system is absolutly clear an optimated for running audio software on my pc.

my components: athlon 64 3800+ X2
2gb ram
sataII hd an
m-audio fw audiofile
xp incl sp2 and so on

every other programms and softwares are runnig without any problem! please help!

thanks a lot, pila

 

kore crashes: error NTDLL.DLL

hallo,
hallo,
i have this problem! sometimes my kore crashes withou a reason...then the i can see the message: "conflicts between kore and ntdll.dll"
what can be the reason? my system is absolutly clear an optimized for running audio software on my pc.

my components: athlon 64 3800+ X2
2gb ram
sataII hd an
m-audio fw audiofile
xp incl sp2 and so on

every other programms and softwares are runnig without any problem! please help!

thanks a lot, pila

 

Can either or both of you send the Dr. Watson log to support?

If you don't have error reporting turned on, turn it on- you'll need it to generate the report

Clear out your old logs first; they're in Documents and Settings/All users/Application Data/Microsoft/DrWatson (turn on show hidden files and folders in your view menu). Then, the next time it crashes, zip up the DrWatson report in that folder and send it along...

ew

 

ok, i will try it. shoud i send this dates to the support? or have you a adress where i can it send dirctly?

 

Send it to support...

Thanks,
ew

 

This is actually the same dll that crashes for me when trying to run Waldorf Attack 1.21 on my new system. See my original post here.

I tried Waldorf Attack 1.21 on my old P4 system and it works without any issue. In my case it has nothing to do with the CPU load, I can reproduce the crash running just Kore and opening up an instance of Waldorf Attack.

The specs on my system are:
- Intel Core 2 Duo E6700
- Asus P5W DH (Intel 975X chipset)
- 2 GB DDR2 800 Memory
- Seagate SATA II HDDs
- RME Multiface

I captured the Dr. Watson data and sent it to NI Support.

EDIT: I should clarify this only happens in standalone mode, I can't get Kore to crash when using it as a wrapper for Attack within Cubase SX3.

 

I got a reply from NI support regarding my crash problem, they say a 1.03 update should be coming "very soon".

 

Have the same problem.
Send you my crashlog too

 

i got another problem too.
"Cant save sound file"
if you say ok the application shut down and can not load the soundfile on the next start.
Both the performace and the sound!
Have you had this too?

 

Are you trying to resave one of the factory sounds or performances to its original location? You can't do that- it won't let you overwrite the factory sounds. You CAN save them to your user folder and then move them over, though.

It still shouldn't crash, though...

ew

 

Its no original sound, it is a user defind sound

 

I had the same thing again.
So i had to build the sound again.
Even if i would try to overwrite a original sound the program dont have to crash.
But maybe its coming from a sample in Intakt which had not the same basicsampletime (a mistake) like the others and was played in timemachine mode.
Intakt can only stretch or expand samples with the same groundtempo in a correct way. Clearly.........
So this could cause the crash by saving.
I still work to find out the reason.