BSOD when using M-Audio M-Track Eight

[victorasantos10]

Hello everybody!

I'm facing a long-time problem when using my M-Audio M-Track Eight USB audio interface. It yields a IRQL_NOT_LESS_OR_EQUAL BSOD an a non specific time.

Some information:

1 - It isn't 'triggered' by any action like opening a specific program or file. It happens when the interface is on and plugged via USB to my computer. Sometimes it happens after 5 minutes on, sometimes after 1 hour.
2 - I've tested it in another computer. Just left it for 3 days turned on, and no BSOD in this one.
3 - When the interface remains conected, but on standby mode, the error doesn't happen.
4 - Connected it on all the USB ports that i have, and the error still happen.
5 - Updated all my drivers, including USB, chipset and other stuff. And no solution.
6 - I've already contacted the manufacturer support, but they keep saying that the problem is on my pc.
7 - I've already formatted my PC.

For real, i don't know what to test anymore. Whan can I do to track the real problem? And, of course, solve it?

I uploaded the .zip file as said on the instructions.

 

[fireberd]

I haven't looked at your dumps as they wouldn't do me any good.
But a comment (and it may or may not be related). I see you have a 64 bit OS but only 4GB of RAM. A 64 bit OS uses more basic memory and thus less left for programs. If you only have 4GB or less best to use a 32 bit OS.

(I have a Sonar recording studio)

 

[victorasantos10]

I haven't looked at your dumps as they wouldn't do me any good.
But a comment (and it may or may not be related). I see you have a 64 bit OS but only 4GB of RAM. A 64 bit OS uses more basic memory and thus less left for programs. If you only have 4GB or less best to use a 32 bit OS.

(I have a Sonar recording studio)

Didn't know this one, fireberd! I'll buy some new PC stuff soon. Thanks a lot!

 

[Pauly]

Just checked a few of your dumps and they are identical all blaming the driver for that device
Have you tried uninstalling it and reinstalling/tried a different driver if one is available
The driver you have installed is dated Jan 2015 so not that old but a newer one may be available or even try an older one if there is no newer one ?

Looking at their site there is drivers and firmwares dated July/October this
year so may be worth a try
Scratch that look like you have the latest driver I was looking at the wrong bit
M-Audio - Acclaimed audio interfaces, studio monitors, and keyboard controllers

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {44, 2, 1, fffff800030840cc}
[B][U]*** WARNING: Unable to verify timestamp for MAudioMTrackEight.sys[/U][/B]
[U][B]*** ERROR: Module load completed but symbols could not be loaded for MAudioMTrackEight.sys[/B][/U]
[U][B]Probably caused by : MAudioMTrackEight.sys ( MAudioMTrackEight+16483 )[/B][/U]
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030840cc, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003314100
GetUlongFromAddress: unable to read from fffff800033141c0
 0000000000000044 Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
nt!IoCancelIrp+2c
fffff800`030840cc c6434401        mov     byte ptr [rbx+44h],1
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME:  fffff880031bd970 -- (.trap 0xfffff880031bd970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff88002f63860
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030840cc rsp=fffff880031bdb00 rbp=0000000000000005
 r8=000000004f444600  r9=0000000000000000 r10=fffff80003063000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!IoCancelIrp+0x2c:
fffff800`030840cc c6434401        mov     byte ptr [rbx+44h],1 ds:00000000`00000044=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800030d61e9 to fffff800030d6c40
STACK_TEXT:  
fffff880`031bd828 fffff800`030d61e9 : 00000000`0000000a 00000000`00000044 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`031bd830 fffff800`030d4e60 : fffffa80`05655050 fffffa80`046d5100 00000000`70627375 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031bd970 fffff800`030840cc : fffffa80`064984b0 00000000`00000000 00000000`00000005 fffff800`030dbaa2 : nt!KiPageFault+0x260
fffff880`031bdb00 fffff880`06132483 : 00000000`00000000 fffffa80`04c8f500 00000000`00000005 fffffa80`000e0082 : nt!IoCancelIrp+0x2c
fffff880`031bdb40 00000000`00000000 : fffffa80`04c8f500 00000000`00000005 fffffa80`000e0082 fffffa80`042da5b0 : MAudioMTrackEight+0x16483
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
MAudioMTrackEight+16483
fffff880`06132483 ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  MAudioMTrackEight+16483
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: MAudioMTrackEight
IMAGE_NAME:  MAudioMTrackEight.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54af345e
FAILURE_BUCKET_ID:  X64_0xA_MAudioMTrackEight+16483
BUCKET_ID:  X64_0xA_MAudioMTrackEight+16483
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0xa_maudiomtrackeight+16483
FAILURE_ID_HASH:  {d00cdb4b-2904-1a29-e9d8-93516c95605c}
Followup: MachineOwner
---------
2: kd> lmvm MAudioMTrackEight
start             end                 module name
fffff880`0611c000 fffff880`0619f000   MAudioMTrackEight T (no symbols)           
    Loaded symbol image file: MAudioMTrackEight.sys
    Image path: MAudioMTrackEight.sys
    Image name: MAudioMTrackEight.sys
    [B][U]Timestamp:        Fri Jan 09 01:52:30 2015 (54AF345E)[/U][/B]
    CheckSum:         0009052E
    ImageSize:        00083000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[victorasantos10]

Just checked a few of your dumps and they are identical all blaming the driver for that device
Have you tried uninstalling it and reinstalling/tried a different driver if one is available
The driver you have installed is dated Jan 2015 so not that old but a newer one may be available or even try an older one if there is no newer one ?

Looking at their site there is drivers and firmwares dated July/October this
year so may be worth a try
Scratch that look like you have the latest driver I was looking at the wrong bit
M-Audio - Acclaimed audio interfaces, studio monitors, and keyboard controllers

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {44, 2, 1, fffff800030840cc}
[B][U]*** WARNING: Unable to verify timestamp for MAudioMTrackEight.sys[/U][/B]
[U][B]*** ERROR: Module load completed but symbols could not be loaded for MAudioMTrackEight.sys[/B][/U]
[U][B]Probably caused by : MAudioMTrackEight.sys ( MAudioMTrackEight+16483 )[/B][/U]
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030840cc, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003314100
GetUlongFromAddress: unable to read from fffff800033141c0
 0000000000000044 Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
nt!IoCancelIrp+2c
fffff800`030840cc c6434401        mov     byte ptr [rbx+44h],1
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME:  fffff880031bd970 -- (.trap 0xfffff880031bd970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff88002f63860
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030840cc rsp=fffff880031bdb00 rbp=0000000000000005
 r8=000000004f444600  r9=0000000000000000 r10=fffff80003063000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!IoCancelIrp+0x2c:
fffff800`030840cc c6434401        mov     byte ptr [rbx+44h],1 ds:00000000`00000044=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800030d61e9 to fffff800030d6c40
STACK_TEXT:  
fffff880`031bd828 fffff800`030d61e9 : 00000000`0000000a 00000000`00000044 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`031bd830 fffff800`030d4e60 : fffffa80`05655050 fffffa80`046d5100 00000000`70627375 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031bd970 fffff800`030840cc : fffffa80`064984b0 00000000`00000000 00000000`00000005 fffff800`030dbaa2 : nt!KiPageFault+0x260
fffff880`031bdb00 fffff880`06132483 : 00000000`00000000 fffffa80`04c8f500 00000000`00000005 fffffa80`000e0082 : nt!IoCancelIrp+0x2c
fffff880`031bdb40 00000000`00000000 : fffffa80`04c8f500 00000000`00000005 fffffa80`000e0082 fffffa80`042da5b0 : MAudioMTrackEight+0x16483
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
MAudioMTrackEight+16483
fffff880`06132483 ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  MAudioMTrackEight+16483
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: MAudioMTrackEight
IMAGE_NAME:  MAudioMTrackEight.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54af345e
FAILURE_BUCKET_ID:  X64_0xA_MAudioMTrackEight+16483
BUCKET_ID:  X64_0xA_MAudioMTrackEight+16483
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0xa_maudiomtrackeight+16483
FAILURE_ID_HASH:  {d00cdb4b-2904-1a29-e9d8-93516c95605c}
Followup: MachineOwner
---------
2: kd> lmvm MAudioMTrackEight
start             end                 module name
fffff880`0611c000 fffff880`0619f000   MAudioMTrackEight T (no symbols)           
    Loaded symbol image file: MAudioMTrackEight.sys
    Image path: MAudioMTrackEight.sys
    Image name: MAudioMTrackEight.sys
    [B][U]Timestamp:        Fri Jan 09 01:52:30 2015 (54AF345E)[/U][/B]
    CheckSum:         0009052E
    ImageSize:        00083000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hmmm, so the problem is really on the driver? I thought it wasn't, cause it worked properly in another computer. And M-Audio support wasn't so helpful

The fact of working in another PC doesn't mean that the problem isn't related to the driver?

I'm thinking about changing my memory to 6+GB. According to the dumps, does it have any remote possibility to solve the problem? Thanks in advance!

 

[fireberd]

Upgrading the memory would be my first step, since you have the 64 bit OS. The dumps refer to the driver, but as it works in another PC and does work in this one at least for a while, memory could be an issue.

You note you have already reformatted the PC. But, which driver did you install? The one that came with the unit or one downloaded from MAudio? If you just used the one that came with the unit, try the driver on the MAudio downloads and see if it makes any difference.

M-Audio - Acclaimed audio interfaces, studio monitors, and keyboard controllers

 

[Pauly]

The installed driver is dated Jan 15 which matches the newest one available from Maudio website, although the dump blames the driver for the crash this is telling you the driver was basically active and at the centre of the crash but does not necessarily mean the driver is faulty or corrupt it is feasible that running out of memory could cause the driver to crash but it would be tricky to prove.
I would definitely try removing and reinstalling the driver if you haven't already just incase you have a corrupted install.

You could also try watching memory usage as you are running your adiou device and see if the crashes match up with memory maxing out

 

[fireberd]

Pauly's comments on memory go back to my original comment about only 4GB of RAM and the 64 bit OS.

As it works for a while, it could very well be a memory issue.

 

[victorasantos10]

Good. So i'll consider buying a new motherboard too (my one is a bit old, doesn't support more than 4GB).

About the questions about the driver: Really, it is the newest one. And in the M-Audio site isn't possible to download previous versions. I've also tried to uninstall and delete the driver and let Windows install it automatically when I reconnect the device, but Windows fails to do it. So i need to use the CD that came with the device or install the latest driver by the site (both options install the same version).

I have noticed that sometimes, while i'm listening to an audio file, some glitches start to happen (the audio stops approximately 2 seconds, then come back to play) and, not too much time later, the BSOD blow again. But, as said, it happens independent of being with an audio file open or not.

About the memory usage, i've not paid attention to this. I'll try to use some "memory stressing" program while listening to music and notice if the BSOD is triggered.

Thanks a lot!!