problems

Hi Guys

Heres the story bought Traktor and the BCD2000 in November

tried to get cykokrauts midi rules working...failed miserably

so...

DJ'd with B-DJ for December played 20 gigs no problem then I got my first crash and it keeps on crashing so since then I've changed to Future decks pro (yup still crashes!) to the point I have BCD2000 out now into my regular mixer with a standby minidisc player on channel B

Spent 2 hours on the phone setting up Traktor with the very helpful DJ Syndrome (thanks Nigel) so now I have Traktor working

Set about adding music folders to my collection this morning

and...10 minutes in...poooof...blue screen

BAD_POOL_CALLER

Edit: and again!!! made a note of the error message...this:-

*** STOP: 0x00000c2 (0x00000007, 0x00000CD4, 0x00000000, 0x86022B1C)


I have a brand new lappy with a celeron 1.46 and 1Gb of ram...I'll upgrade it to 2 gig of Ram if I have to

anyone else get this BAD_POOL_CALLER message?


cause it driving me nutz!!


regards


Lee

 

Can I get you to please post your Cracklogs to this thread. BY the pool caller most commonly is not a Traktor Fault I have seen the pool caller issue many times in the last 2-3 years mostly never associated with Traktor at all. Now for the bad news....

This problem can and often is returned when one of two conditions is true. Bad Sector on a hard disk Hard disk Logic or controller problem.

Several things here point you to where the problem lies. One is that you fixed your system then when loading music back in again you saw the problem return. What you can do is this first off get one of the MP3 tester utils and test all of your MP3s to make sure you don't have a corrupt file. My bet is that somewhere along the line while testing the files you will Bluescreen. Moe to step 2,which is to backup proceeding further (Ghost 2003 is best, but it too might not complete successfully) . Find out the brand and model of disk drive your system has in it and get the disk test tools from the Mfr website Run those tools and do a thorough surface test (non-destructive if possible) of the entire disk surface. Have the disk lock out bad sectors and relocate data if possible. Once done once retest your disk with the same tools. If there are any problems relocating files whatsoever then restore from your backup then do a hot reinstall of your O/S (you won't loose any files or settings but may need to run Windows update to get hotfixed.

Win XP is extremely sensitive to DISK errors and Ram Errors and generally handles neither gracefully. My personal experience has been that while there are a great many root cuases, systems systwem that have had no config changes that sudedenly start exhibiting this issue have hardware going bad. With a little tenactiy you can debug these problems, see here.
http://support.microsoft.com/kb/265879/

You can also see form this list that a great many things can cause this problem
http://search.technet.microsoft.com...YAwLM2NutCQLz7vjkDfpIJoIZt96jNZ3QwUQNLlvEAAos

Phil

 

Hi Phil thanks for the reply

Sorry to sound dumb but is the "cracklog" the message I got on the bluescreen? If not where do I find them?

I shall look into what you say and let you know


I'm flippin well convinced its the darned controller....but we shall see

thanks


Lee

 

What is it with these forums...I don't get it

Phil asked me to post my "cracklogs" in this thread

I will gladly do it

but, what are they?

I've asked nicely...and yet no-one answers?


Its rather frustrating

okay I know I haven't been posting here long...but, I've only just bought the darned thing!!!

can someone please help


(I know it may be such a dumb question for many...but...I'm lost and need help)


Lee

 

it's been mispelled, he meant *crashlog*.
perform a search for that on your system, these are small textfiles.

besides that i personally cannot help you, this is beyond my knowledge.

 

Thanks Native girl

I shall see if I can find a crashlog


geeeez what have I got into here??...Cds were so easy



regards


Lee

 

Hi Native Girl

I've searched google cause I can't find the crash log (man...I'm dumb...it can't be so hard surely?)

anyways I came accross this bit of info in my search

"you can find the crash log here

~[username]/Library/Logs/CrashReporter/TraktorDJStudio3.crash.log"

so duh (as usual) I can't find that

the " ~ "

am I suppose to know what that means is it short for

C> programs> etc etc?

does that make sense?


Seaside (starting to pull hair out with this!! grrr!)

 

Looks like you're on Windows. I don't have a Mac, but it sort of looks like you got your "bit of info" from a Mac User.

What you should try is search your harddisk for "CrashReporter" or sth else from the path you found. Good candidates are the dir you installed Traktor to or your Application Data folder parallel to "My Documents"...

Also, as Phil aready posted, this really smells a bit like hardware problems, so there's no guarantee someone can help. But if you describe your setup more precisely and give ppl some time to sort it out, there's a good chance you get good feedback. Have you checked the links he posted already?

There's always Native Instruments' support if you're stuck...

Cheers, h00la

 

Hi h00la

I have searched "my computer"

for crash log
crashlog
crack log
cracklog
crash reporter
crashreporter
CrashReporter
Crash Reporter

and found nothing so far...grrr!

yes I had a look at the links Phil posted...and I realize I am just so out of my depth here

my laptop is an advent 7109 bought from PC World in November 2006

it hasn't been used for anything other than B-DJ, futuredecks pro and traktor

It has been optomized following the instructions I followed through a link from here

it has an intel Celeron M CPU 1.46 ghz and 1gig of Ram..I have my music stored on an external Western digital 250gb hard drive


haven't tried the disc scan thing yet to be honest


thanks


Lee

 

hold the phone!!!!!!!!!!!!!!!!!!!!!!

I found the crash log (OMG!!)

hope it means something to someone??? (fingers crossed)

Logged at Monday, January 15, 2007 13:54:25
FileVersion: 3.0.0.41
ProductVersion: 3.0.0.0

Exception Code: 0xC0000005
Exception Addr: 0x001B:0x007E719B
Exception Module: TraktorDJStudio3.exe
Exception Description: EXCEPTION_ACCESS_VIOLATION, Attempt to read from address 0x00000004 The memory could not be "read"

Call Stack Trace:
6) ID3_TagHeader:arseExtended()
5) dami::id3::v2:arse()
4) ID3_TagImpl:arseReader()
3) ID3_TagImpl:arseFile()
2) ID3_TagImpl::Link()
1) ID3_TagImpl::Link()



Logged at Monday, January 15, 2007 14:23:46
FileVersion: 3.0.0.41
ProductVersion: 3.0.0.0

Exception Code: 0xC0000005
Exception Addr: 0x001B:0x007E719B
Exception Module: TraktorDJStudio3.exe
Exception Description: EXCEPTION_ACCESS_VIOLATION, Attempt to read from address 0x00000004 The memory could not be "read"

Call Stack Trace:
6) ID3_TagHeader:arseExtended()
5) dami::id3::v2:arse()
4) ID3_TagImpl:arseReader()
3) ID3_TagImpl:arseFile()
2) ID3_TagImpl::Link()
1) ID3_TagImpl::Link()


regards


Lee

these crashes happened when I began importing my entire external hard drive into my collection

I have Traktor on this PC too and it imported everything the day before (it took over 24 hours to complete but, it did it no problems) I was hoping that once the files were tagged they would be read by the laptop too but, that didn't happen which is why I was starting over with the laptop

 

yes these help first off upgrade to Traktor 3.1.x there were some import bugs fixed between the version you are running and 3.1. See if the problems persist there.

Next, if you have not yet done so file a support ticket for it and post your number here I need that to link the support message I'll send in to your support ticket.

Next some easier answers.
Does the crash always occur on the same folder and file(s)?
How many total tracks are you trying to import?
How many do you get through before the crash?

Now for the thorny question. Did you look at the stuff I posted and suggested? Did you run any of those base diagnostics?

The pool caller problem you are seeing is indicitave of deeper hardware issues. Those things should be looked into tested for and fixed if found before digging in higher level software problems. Rule out the hardware issues first before proceeding.

Phil

 

Hi Phil

Thanks

That may explain something traktor didn't crash on this machine as it is upgraded I haven't upgraded the laptop because it has not been on the internet and I cannot figure out how to do it without going on?

a support ticket?....hmmm...I better do a search for what you mean...duh!

and to be honest I haven't done those things you linked to...cause I looked and it all looked a bit complicated to be honest.

I'll have a sit down with it tonight and try and force myself to understand it

Its a good job I'm a one off...or you'll be pulling your hair out!!

thanks


I'll be back


Lee

 

Nah quite a few people experience similar issues just google for 'Bad Pool Caller' or go to Microsoft.com and search for the same.

 

Hi Phil

Just wanted to let you know I have upgraded traktor on my lappy now...removed B-DJ and future decks pro and this saturday it played for 6 hours no crashes....hallelujah!!

This is a relief I can tell ya!...I'll keep using it and hopefully it will keep stable

thanks for all the help so far

hopefully I won't be back with any more problems for a while

next thing I need to learn is how to beat map...yikes!


regards


Lee

Oh yeah one last thing I nearly forgot... syndrome (Nigel) your midi rules "MB4 guns" is da bomb...I love it ...thanks again for all your help..I mic'd through my analogue mixer and it worked fine...maybe one day I'll work out how to mike through the BCD but hey, I can get by

 

jst for completelyness:

a support ticket number is what you get back after you get in touch with the NI support, which means: you write to them and then you get an automated number back, which makes it easier for everybody to track your issue.