Quick Sign In:  

Forum: VirtualDJ Technical Support

Topic: CRASH AND RESTART ver. b3217

This topic is old and might contain outdated or incorrect information.

Deck 1 was playing an mp4 and i was at the ask the dj tab. After a few seconds vdj crashed and restarted, without saving my settings that i had done. Using windows 10 with Mc6000MK2.
 

Posted Fri 10 Jun 16 @ 4:07 am
Anybody can see the crash report????
 

Posted Fri 10 Jun 16 @ 6:58 pm
Does VDJ store crash reports local aswell and in that case , where ?
 

Posted Fri 10 Jun 16 @ 7:50 pm
Ok just now i had like 10 crashes and restarts back to back.... As soon as set the ask.the.dj feature to monitor my hashtag at twitter it crashes and restarts. I didn't even need a controller to make it crash. I wasn't connected on the internet so only the crash from yesterday has been sent
 

Posted Fri 10 Jun 16 @ 8:04 pm
Also with any skin i put it will crash and restart.
 

Posted Fri 10 Jun 16 @ 8:05 pm
MrJackson2014 wrote :
Does VDJ store crash reports local aswell and in that case , where ?


Anybody from the team i mean. If they got it.
 

Posted Fri 10 Jun 16 @ 8:06 pm
Yes I know what you mean , but once I heard those crash reports was stored also local on the machine.
This was not a question for you , but hopefully some one else knows the answer
 

Posted Fri 10 Jun 16 @ 8:28 pm
replicated.

from windows event viewer

Faulting application name: SkypeHost.exe, version: 10.1.2123.36, time stamp: 0x56eb679c
Faulting module name: combase.dll, version: 10.0.10586.103, time stamp: 0x56a84cbb
Exception code: 0xc000027b
Fault offset: 0x00166fb1
Faulting process id: 0x3870
Faulting application start time: 0x01d1c3588a97e93b
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Messaging_2.15.20002.0_x86__8wekyb3d8bbwe\SkypeHost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\combase.dll
Report Id: 427f145b-5921-469d-90fd-9fe7715499b4
Faulting package full name: Microsoft.Messaging_2.15.20002.0_x86__8wekyb3d8bbwe
Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1


Windows reportng:

Fault bucket , type 0
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Messaging_2.15.20002.0_x86__8wekyb3d8bbwe
P2: praid:ppleae38af2e007f4358a809ac99a64a67c1
P3: 10.1.2123.36
P4: 56eb679c
P5: combase.dll
P6: 10.0.10586.103
P7: 56a84cbb
P8: 80004004
P9: 000b9e0b
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Messag_24e2743892f95decf6aeed457199fe985cfb6a_37f1fbc4_629189e3

Analysis symbol:
Rechecking for solution: 0
Report Id: 427f145b-5921-469d-90fd-9fe7715499b4
Report Status: 6
Hashed bucket:
 

Posted Fri 10 Jun 16 @ 9:06 pm
MrJackson2014 wrote :
Yes I know what you mean , but once I heard those crash reports was stored also local on the machine.
This was not a question for you , but hopefully some one else knows the answer


Yes they are stored on your computer. Its a DMP file.
 

Posted Fri 10 Jun 16 @ 10:13 pm
Update: So far I solved it by turning the feature off. It won't crash.
 

Posted Fri 10 Jun 16 @ 10:16 pm
djcelPRO InfinityModeratorMember since 2004
No crash report received from you.


MrJackson2014 wrote :
Does VDJ store crash reports local aswell and in that case , where ?

C:\Users\{username}\AppData\Local\Temp\
 

Posted Sat 11 Jun 16 @ 8:31 am
Ok. Thanks. Is this the same report that is sent to Atomix in an event of a crash ?
 

Posted Sat 11 Jun 16 @ 11:06 am
Dj CEL. I'll post here the DMP file. But you can give it a go replicate. Turn wifi off, go to ask the dj tab, monitor twitter and you'll get instant crash and restart.
 

Posted Sat 11 Jun 16 @ 1:37 pm
 

Posted Sat 11 Jun 16 @ 2:06 pm
It was discovered last night that if you have ask.the.dj set to check Twitter, but you are not connected to the Internet, VDJ 8.2 will crash.
 

Posted Sat 11 Jun 16 @ 3:08 pm
NytroMix wrote :
It was discovered last night that if you have ask.the.dj set to check Twitter, but you are not connected to the Internet, VDJ 8.2 will crash.


Actually it was discovered 2 days ago when i made this report and yesterday I posted the video on the group to prove it.
Solution is to NOT monitor Twitter.
 

Posted Sat 11 Jun 16 @ 3:36 pm
I had the same thing last night - and yes, just replicated it by turning the wi-fi off.
 

Posted Sun 12 Jun 16 @ 8:34 pm
Glad I reverted back to 2857 before my gig last night then.

Seems to be fixed in the latest update.
 

Posted Sun 12 Jun 16 @ 8:51 pm


(Old topics and forums are automatically closed)