0xc0000005 error in Cross 3.4

[JimSpin76]

Hi all,

Was playing a gig last night and Cross DVS stopped working, mid set, slightly embarrassing, luckily had some vinyl with me so so was able to restart my laptop and all seemed ok after.. Looking at the error logs this morning gave a 0xc0000005 error. I've cleaned the registry now as this may have been the cause but I thought I better report it.

Full log message here:
Faulting application name: Cross.exe, version: 3.4.0.0, time stamp: 0x582f158c
Faulting module name: Cross.exe, version: 3.4.0.0, time stamp: 0x582f158c
Exception code: 0xc0000005
Fault offset: 0x0000000000963b8c
Faulting process id: 0x17b8
Faulting application start time: 0x01d2524e9c6bb4b6
Faulting application path: C:\Program Files\MixVibes\Cross 3.4.0\win64\Cross.exe
Faulting module path: C:\Program Files\MixVibes\Cross 3.4.0\win64\Cross.exe
Report Id: f5ec521f-6bbf-4477-9991-307d9481ad96
Faulting package full name:
Faulting package-relative application ID:

[RoJeC]

Thanks for reporting. Any crash of Cross is important to report, especially with such a clear message pointing to Cross.
It may be the devteam gets more of it, but to me it seems the info doesn't provide more than references to more detailed info, so it bit hard to find out what's going on.

Could you please check if there also is an error report if Cross. C:\users\[username]\appdata\roaming\mixvibes\crashes\

Cleaning registry not likely to be of any influence to this.

Could you also please provide some description of what you were doing (around) the moment Cross crashed; so some circumstantial info.

[JimSpin76]

Thanks for the reply, unfortunately there wasn't a crash log produced I'm guessing because I killed the task from the task manager before it could be produced.

I wasn't doing anything sophisticated when Cross locked up, just playing a track via DVS, no loops, no effects, I was queueing up a vinyl record on the the other deck and had my mixer set to phono to bypass Cross. So halfway through the tune in Cross just stopped, and wasn't reacting to anything. Quickly popped the queued record on, stopped the Cross process via task manager, rebooted just in case and the started Cross again, worked fine again for the rest of the night.

I do do a lot of swapping from actual vinyl to DVS mode, so perhaps the Cross got 'confused' by the non-timecode pitch from the normal records? I''ll try and recreate the issue at home this week.

Sorry the info probably isn't particularly helpful.

[alexanderperchey]

Hi JimSpin76,

Do you think you could follow these instructions to get the crash dump?

PC: Type Windows+R (that is hold the windows key and press R) and type AppData, followed by enter. This will open an explorer window in the hidden folder “AppData”. Navigate through “Roaming” > “MixVibes” > “Crashes”. From there you will find the crash dumps useful for debugging. Locate, by date, the one related to the crash you want to describe. This is the file you need to send us. Note that this file is not a text file and can’t be opened (usefully) by anyone than us.

Thanks

[JimSpin76]

As I said before, in the case of the crash on friday, a .dmp file wasn't created. There are other dmp files but not for that date and I'm fairly sure what the cause for the crashes where for those (windows trying to update a restart the machine for one!)

I ran Cross last night for 3 or 4 hours last night and had no probs. Obviously if it locks up again I'll wait for the time out and hopefully and dmp file will be produced.

[RoJeC]

At MAc most crashes are written in a crash file. The debugging process of OSX can usually catch it. At Windows it very much depending on the cause. If Cross process is still active it can be written. there's about a 50% chance..

[JimSpin76]

Fair enough, looks like this was one that got away.. Obviously I'll report any further issues and if available give you the dmp file.