Windb output:
Probably caused by : DJM-850Audio64.sys ( DJM_850Audio64+b6d0 )
Followup: MachineOwner
Aktionen für Kommentare
Post
Folgen
[SOLVED] DJM 850 - USB driver causes regular crashes on my laptop - Windows 8
Hi,
since one week I own the new DJM 850 mixer. The usb driver for this console keeps my laptop crashing.
Just for the background:
The setup, before the acquisition of the DJM 850, was/is:
- DJM 800 - already sold
- Denon MC3000 - using just the jog wheels, no sound - no AISO driver installed, just knob mapping or Traktor Pro
- Native Instruments Audio 10 USB soundcard
- Traktor Pro - 4 decks
The reason, why I bought the DJM 850, I was tired of the wiring, before and after a gig, of the cinch cables, between the DJM 800 and the Native Instruments Audio 10 soundcard.
As I got the DJM 850, I deinstalled the AISO driver for the Native Instruments soundcard, never had the AISO driver of the MC3000 installed, just the mapping of the jog wheels. And cleaned as well in the registry of the laptop, not deinstalled fragments of the AISO driver of the Audio 10 card.
Ok, installed the then the driver for the DJM 850 from the CD and started Traktor Pro. Changed inside Traktor Pro settings for DJM 850. Was happy that everything was straight forwad ... was !!!
By playing maximum two/three songs, Windows 8 results in a blue screen. GREAT !!! Debugged then on Windows 8 one of the plenty of dump files (DMP) with the reoccuring result:
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
FAULTING_MODULE: fffff802abc72000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 50c69d06
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
_ fffffffffffffffc _
CURRENT_IRQL: 0
FAULTING_IP: _
_DJM_850Audio64+b6d0
fffff880`1bbc96d0 8946fc mov dword ptr [rsi-4],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from fffff802abccb769 to fffff802abccc440
STACK_TEXT:
fffff880032ff5b8 fffff802abccb769 : 000000000000000a fffffffffffffffc 0000000000000002 0000000000000001 : nt+0x5a440
fffff880032ff5c0 000000000000000a : fffffffffffffffc 0000000000000002 0000000000000001 fffff8801bbc96d0 : nt+0x59769
fffff880032ff5c8 fffffffffffffffc : 0000000000000002 0000000000000001 fffff8801bbc96d0 fffff802abee3409 : 0xa
fffff880032ff5d0 0000000000000002 : 0000000000000001 fffff8801bbc96d0 fffff802abee3409 0000000000000000 : 0xffffffff`fffffffc
fffff880032ff5d8 0000000000000001 : fffff8801bbc96d0 fffff802abee3409 0000000000000000 0000000000000000 : 0x2
fffff880032ff5e0 fffff8801bbc96d0 : fffff802abee3409 0000000000000000 0000000000000000 3f8000003f800000 : 0x1
fffff880032ff5e8 fffff802abee3409 : 0000000000000000 0000000000000000 3f8000003f800000 3f8000023f800002 : DJM_850Audio64+0xb6d0
fffff880032ff5f0 0000000000000000 : 0000000000000000 3f8000003f800000 3f8000023f800002 0000000000000000 : nt+0x271409
STACK_COMMAND: kb
FOLLOWUP_IP: _
_DJM_850Audio64+b6d0
fffff880`1bbc96d0 8946fc mov dword ptr [rsi-4],eax
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: DJM_850Audio64+b6d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: DJM_850Audio64
IMAGE_NAME: DJM-850Audio64.sys <<---- keep on reocuring
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
By investigating in the DJM-850.sys file got the following output:
kd> lmvm DJM_850Audio64
start end module name
fffff8801bbbe000 fffff8801bbce000 DJM_850Audio64 T (no symbols)
Loaded symbol image file: DJM-850Audio64.sys
Image path: \SystemRoot\system32\drivers\DJM-850Audio64.sys
Image name: DJM-850Audio64.sys
Timestamp: Tue Dec 11 03:40:06 2012 (50C69D06)
CheckSum: 00012FBB
ImageSize: 00010000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
By the way, the driver for the DJM 850, which is younger and can be downloaded from the Pioneer Homepage, results in the same crashes/blue screens.
@Pioneer
Such a great console and such a fragile driver. Is there any improvement ongoing or do I need to replace this DJM 850 with something else ? Just for info, had this Saturday a scheduled gig, but, the USB driver for DJM 850 keeps on crashing, with the Audio 10 :-((
With the "old" setup never had problems, no crashes, no dropouts ... for 1,500.00 EUR I expect something, which is plug and play an not only plug an maybe play.
Post ist für Kommentare geschlossen.
Datum
Stimmen
4 Kommentare
@Mick04 >
We would advise Mick04 to completely uninstall the audio driver of DJM-850, then install it again.
- Select Program (Programs and Features) from Control Panel.
Click [DJM-850 Driver] in the list, then select the Uninstall/Change button.
- Please take the steps below in order to make sure that the driver is completely uninstalled:
Open [C:\Program Files\Pioneer] to see [DJM-850] folder does not exist there.
Open [C:\Windows\System32\Drivers] to see [DJM-850Audio64.sys] file does not exist there.
Open [C:\Windows\SysWOW64] to see [DJM-850_Asio.dll] file does not exist there.
- After making sure the above, please reboot the OS and reinstall DJM-850 audio driver.
We were not able to reproduce this issue.
Please let us know the following information.
・Machine spec: CPU, memory, OS, etc.
・The setup of the devices: How they are connected with other devices including ones you did not mention in the thread when Windows 8 results in a blue screen.
・Does the same issue occur when only DJM-850 and the PC are connected via a USB cable?
Aktionen für Kommentare
As mentioned above, as I installed the DJM850 driver, the PC (Acer 7560G) kept on crashing. And performed all the steps as well, as Gavin from Pioneer mentioned. Unfortunately no solution.
So, I was tired of searching, where the error is, and I needed the PC for gigs, following steps were performed
- Windows 8 reinstalled
- Latest bios update
- Latest drivers installed (video, network, ...)
Now, the ASIO driver of Pioneer AND the ASIO driver of the Denon MC3000 are installed, just for verfication. No problems, all runs fine. To be honest, it was some faulty issue in Windows OS. I have the laptop just for 1 1/2 years now ...
The problem has been solved by reinstalling Win 8 and the BIOS/drivers upgrade.
Aktionen für Kommentare
@Mick04 > Thats great news, thanks for letting us know!
Aktionen für Kommentare