Rpm1580
Mar 2, 2025, 07:30 GMT+2
I can't open Virtual DJ. I've been through this a number of times, the last time looks like October, 2024.
I reviewed previous communications with you folks in 2024 about the same problem and tried to troubleshoot already.
Problem: Error message is "Virtual DJ is not responding, Close the program or Wait for the program to respond". Everything is grayed out.
Computer: HP I7 Gen 8 with 32 GB RAM.
Windows 11: - Version 24H2 26100.3194
I removed recently added utility programs. The other recent updates are mostly Windows 11, Windows Office 16 dropbox or web browser updates.
I deleted the VDJ Settings file - didn't work.
I completed 3-4 clean installs - didn't help.
I was running the latest version of VDJ yesterday when it happened and I use VDJ da.
I Windows permissions are okay - full control for the vdj exe file.
Downloaded and opened with User Account with Full Admin privileges and tried as Administrator. Nothing worked. Mouse just set there spinning with VDJ grayed out. I do have a backup of the complete VDJ Home folder before this happened. Been using VDJ daily; last outage with same problem in October 2024.
How do I fix this?
Thoughts?
thanks,
Richard
Posted Mon 03 Mar 25 @ 5:42 am
So it happens right after you try to start VirtualDJ ?
Here is a few things you can try....
- Open the settings.xml file you will find in the HomeFOlder of VirtualDJ and look for the line <lastSelectedFolder>. Delete the line, save and try to restart.
Could be a specific folder/list you have selected from previous sessions
- If the above doesnt help, rename the file settings.xml (but dont delete it) and start VirtualDJ.
- If none of the above helps, it could be some problem with your database.
In any case if you still get the same issue, please contact Support
Here is a few things you can try....
- Open the settings.xml file you will find in the HomeFOlder of VirtualDJ and look for the line <lastSelectedFolder>. Delete the line, save and try to restart.
Could be a specific folder/list you have selected from previous sessions
- If the above doesnt help, rename the file settings.xml (but dont delete it) and start VirtualDJ.
- If none of the above helps, it could be some problem with your database.
In any case if you still get the same issue, please contact Support
Posted Mon 03 Mar 25 @ 1:10 pm
I tried your solutions but none of them worked. I went back to my original backup VDJ Home folder each time before modifying the Settings.xml file - none worked.
If it's a corrupt database file, perhaps I ought to try using one of my recent database.xml backup files. Is that what you would suggest. Also, does the VirtualDJ System Report help debug the problem. I'm going to include it her just in case you have any more ideas.
thanks,
Richard
--- VirtualDJ System Report --- 850.8502.pc64 --- 2025-02-27 18:16 ---
-- System info --
CPU: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
GPU: Intel(R) UHD Graphics 620
Memory: 32582 MB
Power Mode: Balanced
-- MIDI Devices --
Midi in device: drivername="Input Volume Control" vid="0x0C60" pid="0x0016" mid="0x0000" interface="\\?\tusbaudio_enum#vid_0c60&pid_0016&ks#9900000000000587#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi_in_00_00"
Midi out device: drivernameout="Microsoft GS Wavetable Synth"
Midi out device: drivernameout="9900000000000587" vid="0x0C60" pid="0x0016" mid="0x0000" interface="\\?\tusbaudio_enum#vid_0c60&pid_0016&ks#9900000000000587#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi_out_00_00"
-- HID Devices --
HID Device (unknown): vid="0x2A94" pid="0xC04D" path="\\?\hid#gtch7503&col02#5&c31435e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"
HID Device (unknown): vid="0x06CB" pid="0x82F5" path="\\?\hid#syna3091&col03#5&148b1800&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"
HID Device (unknown): vid="0x06CB" pid="0x82F5" path="\\?\hid#syna3091&col04#5&148b1800&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"
HID Device (unknown): vid="0x0001" pid="0x0001" path="\\?\hid#hpq6001#3&1f700816&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
-- Audio Devices --
Audio device: asio="Apogee USB ASIO Driver" hardwareID:"7D0FB778-980D-4FD2-BEA530A00D850B39"
Audio device: input name="Apogee Duet" vid="0x0C60" pid="0x0016" hardwareID:"{0.0.1.00000000}.{13e29c1f-ae09-46dd-a826-847ac974bc12}"
Audio device: input name="IntelĀ® Smart Sound Technology (IntelĀ® SST)" vid="0x8086" pid="0xAE20" hardwareID:"{0.0.1.00000000}.{a10bd8f9-30d0-4401-bbfb-7899c4054f8d}"
Audio device: name="Apogee Duet" vid="0x0C60" pid="0x0016" hardwareID:"{0.0.0.00000000}.{6d4b0cf8-0908-414d-bf74-d8b0c121c476}"
Audio device: name="Intel(R) Display Audio" vid="0x8086" pid="0x280B" hardwareID:"{0.0.0.00000000}.{0e65bf2f-9e5b-4864-a8be-aa5141bedf18}"
Audio device: name="Realtek(R) Audio" vid="0x10EC" pid="0x0215" hardwareID:"{0.0.0.00000000}.{a1761c70-e8cf-4c41-89d0-3691c44d6f49}"
-- Audio Devices Used --
asio://7D0FB778-980D-4FD2-BEA530A00D850B39 (Apogee USB ASIO Driver) 48000 Hz, Int32LSB, 4 chan out, 2 chan in, 512 samples
-- Performance Log --
Performance stats (session duration: 30:40)
avg peak audio cpu: 4% - low skin fps avg: 25 fps - periods with skin drops (<24fps): 40% - periods with skin drops (<15fps): 2%
-- Database --
Loading database C: (40.36 MB)
Database loading time: 167.86 ms - Number of entries: 60403
If it's a corrupt database file, perhaps I ought to try using one of my recent database.xml backup files. Is that what you would suggest. Also, does the VirtualDJ System Report help debug the problem. I'm going to include it her just in case you have any more ideas.
thanks,
Richard
--- VirtualDJ System Report --- 850.8502.pc64 --- 2025-02-27 18:16 ---
-- System info --
CPU: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
GPU: Intel(R) UHD Graphics 620
Memory: 32582 MB
Power Mode: Balanced
-- MIDI Devices --
Midi in device: drivername="Input Volume Control" vid="0x0C60" pid="0x0016" mid="0x0000" interface="\\?\tusbaudio_enum#vid_0c60&pid_0016&ks#9900000000000587#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi_in_00_00"
Midi out device: drivernameout="Microsoft GS Wavetable Synth"
Midi out device: drivernameout="9900000000000587" vid="0x0C60" pid="0x0016" mid="0x0000" interface="\\?\tusbaudio_enum#vid_0c60&pid_0016&ks#9900000000000587#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\midi_out_00_00"
-- HID Devices --
HID Device (unknown): vid="0x2A94" pid="0xC04D" path="\\?\hid#gtch7503&col02#5&c31435e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"
HID Device (unknown): vid="0x06CB" pid="0x82F5" path="\\?\hid#syna3091&col03#5&148b1800&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"
HID Device (unknown): vid="0x06CB" pid="0x82F5" path="\\?\hid#syna3091&col04#5&148b1800&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"
HID Device (unknown): vid="0x0001" pid="0x0001" path="\\?\hid#hpq6001#3&1f700816&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
-- Audio Devices --
Audio device: asio="Apogee USB ASIO Driver" hardwareID:"7D0FB778-980D-4FD2-BEA530A00D850B39"
Audio device: input name="Apogee Duet" vid="0x0C60" pid="0x0016" hardwareID:"{0.0.1.00000000}.{13e29c1f-ae09-46dd-a826-847ac974bc12}"
Audio device: input name="IntelĀ® Smart Sound Technology (IntelĀ® SST)" vid="0x8086" pid="0xAE20" hardwareID:"{0.0.1.00000000}.{a10bd8f9-30d0-4401-bbfb-7899c4054f8d}"
Audio device: name="Apogee Duet" vid="0x0C60" pid="0x0016" hardwareID:"{0.0.0.00000000}.{6d4b0cf8-0908-414d-bf74-d8b0c121c476}"
Audio device: name="Intel(R) Display Audio" vid="0x8086" pid="0x280B" hardwareID:"{0.0.0.00000000}.{0e65bf2f-9e5b-4864-a8be-aa5141bedf18}"
Audio device: name="Realtek(R) Audio" vid="0x10EC" pid="0x0215" hardwareID:"{0.0.0.00000000}.{a1761c70-e8cf-4c41-89d0-3691c44d6f49}"
-- Audio Devices Used --
asio://7D0FB778-980D-4FD2-BEA530A00D850B39 (Apogee USB ASIO Driver) 48000 Hz, Int32LSB, 4 chan out, 2 chan in, 512 samples
-- Performance Log --
Performance stats (session duration: 30:40)
avg peak audio cpu: 4% - low skin fps avg: 25 fps - periods with skin drops (<24fps): 40% - periods with skin drops (<15fps): 2%
-- Database --
Loading database C: (40.36 MB)
Database loading time: 167.86 ms - Number of entries: 60403
Posted Tue 04 Mar 25 @ 3:00 am
I finally solved the problem. The solution was simply unplugging all of the usb connections to the computer before clicking on the VirtualDJ exe file just the first time. After that, you can keep the USB devices plugged in and VirtualDJ opens normally.
I'm using the same database file and its fine.
Richard
Posted Fri 07 Mar 25 @ 10:13 pm
What kind of USB devices ? Storage ones ?
If one of the devices could cause this, then my guess is that you can discover which one is the problematic by trying one by one.
If one of the devices could cause this, then my guess is that you can discover which one is the problematic by trying one by one.
Posted Sat 08 Mar 25 @ 12:43 pm
I've had a similar series of crashes in 2025 that can only be exited by powering off the computer. It's linked to scanning the ext USB, every time it's crashed it's been scanning. I'm inclined to just blame USB but then it doesn't happen on other exact setups.
Posted Wed 12 Mar 25 @ 12:20 pm
Have you tried to check with HP in case there are any new driver updates for your device chipset ?
Chipset driver updates are crucial for USB devices as they can fix or brake anything USB related.
So, give it a go, and if HP has multiple versions of chipset drivers for your laptop, try to use different versions to see if any of them makes any difference..
Chipset driver updates are crucial for USB devices as they can fix or brake anything USB related.
So, give it a go, and if HP has multiple versions of chipset drivers for your laptop, try to use different versions to see if any of them makes any difference..
Posted Wed 12 Mar 25 @ 12:43 pm