Attn: Chris and/or MOTU - please fix BSOD in driver

[torrentg]

The latest version which caused this crash posted and also the previous version have been having major bsod issues at boot and otherwise. This one posted is a 0xD1 stop involving a write operation, just as a few years ago you had fixed for me, but there have also been other memory corruption types.

This happens all the same on Windows 8 and Windows 7, the two oses that I have. Both x86. Both oses work flawlessly for any given amount of time when MOTU is powered off.

Please fix this asap. I can easily help testing if needed. I will be looking on MOTU.com for an update, otherwise.

I'm fairly sure that Adobe Flash is freezing on me due to the same issue, when going full screen, because when it does not freeze the machine completely, it does instead trigger the bsod.

I don't think it matters, but in case it does, were talking about an original Traveler hardware 1.07 boot 1.01 and HIS AGP ATI 3850 Turbo (latest driver which is perfect).

Thanks for the great service in the past with a similar issue. It is always appreciated:

https://rapidshare.com/files/2636540431 ... 812-01.dmp

Code: Select all

STACK_TEXT:  
9ff87ba8 8131b600 0000000a 00006664 00000002 nt!KiBugCheck2
9ff87ba8 8e6ee6a9 0000000a 00006664 00000002 nt!KiTrap0E+0x2c8
WARNING: Stack unwind information not available. Following frames may be wrong.
9ff87c3c 8e6ee7bf 838d6610 00000012 838d6610 motufwa+0x326a9
9ff87c54 8e6ee9ab 838d6610 8388b690 9ff87cc8 motufwa+0x327bf
9ff87c64 8e6f20fc 00000005 8e6f4793 8388b7e8 motufwa+0x329ab
9ff87cc8 8e6f25f1 00000000 8388b7e0 00000000 motufwa+0x360fc
9ff87d04 8e6f260c 838d69e0 8e6ee54f 9ff87d48 motufwa+0x365f1
9ff87d14 8e6eefd8 838d6478 00000000 85d74860 motufwa+0x3660c
9ff87d48 8e6d7600 8385c840 00000000 83665cc0 motufwa+0x32fd8
9ff87d74 81451275 85d74860 ef75976f 00000000 motufwa+0x1b600
9ff87db0 8131cdd1 8e6d7590 85d74860 00000000 nt!PspSystemThreadStartup+0x4a
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

Code: Select all

0: kd> lmvm motufwa
start    end        module name
8e6bc000 8e735000   motufwa  T (no symbols)           
    Loaded symbol image file: motufwa.sys
    Image path: \SystemRoot\system32\drivers\motufwa.sys
    Image name: motufwa.sys
    Timestamp:        Thu Sep 06 18:13:47 2012 (5049201B)
    CheckSum:         0007B8C8
    ImageSize:        00079000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[UltimateOutsider]

Hmm. I just got a PCIe 424 system last week and started getting blue screens in both Win 8 and Win 7. It only happens at system startup, sometimes I don't even notice because Windows just reboots again and works the second time, but I'll get these notices once I log on to Windows that it just recovered from a crash.

I have the same version of that driver, but it's the 64-bit version.

I've been trying to get Windbg installed all day so I can see what the DMP files say, but the Win 7 SDK won't install it for some reason. Doesn't look like there's a standalone download for that stuff anymore.

[torrentg]

There is a standalone somewhere but good luck finding it, heh.

You can upload the minidump(s) to Rapidshare or similar and I'll run them to see if you're having the same issue, if ya want. I'm sure you probably are.

[billruys]

This may be a dumb question, but why are you guys not raising a Techlink with MOTU tech support? It's fine to let the community here know that you have a problem, but MOTU does have a process set up for logging technical problems.

BTW, I have found that the PCIe-424 does crash at start-up in Windows 8, but I have never seen the problem in Windows 7. This doesn't surprise me as MOTU has not officially released a Win8 driver yet.

[UltimateOutsider]

This may be a dumb question, but why are you guys not raising a Techlink with MOTU tech support? It's fine to let the community here know that you have a problem, but MOTU does have a process set up for logging technical problems.

Because without Windbg I haven't seen any data linking the crashes to the MOTU stuff yet. Once I do, you can bet I'll file a report if it turns out to be the same problem as the OP.

And I definitely experienced Win 7 crash reports over the weekend, in addition to Win 8.

[UltimateOutsider]

Turns out my crash issue (at least on Win 7) is due to an NVIDIA driver, Nvlddkm.sys, installed by version 306.23 of the NVIDIA graphics drivers for my card. I just installed these drivers over the weekend- just coincidence I installed the PCIe-424 the same week.

Haven't looked into the Win 8 crash yet.

[torrentg]

lol heh tehchlink....Jesus will return to Earth before they fix anything through there.

Chris M., when he is around here, personally gets the engineers to fix the issue(s) in less than 24 hrs and supplies a new driver before even the public receives it.

It's not at all about tattling to the public about the drivers. I'm a major supporter of MOTU and recommend them any chance I get, precisely because of how they've perfected the driver in the past...but now the problem has cropped up again...I'm sure they will fix it quickly when made aware.

I'm not a software engineer, but I don't think this is something they lose sleep over. A little work and done.

This particular crash is being caused by the kernel mode driver (MOTU's) trying to access a pageable or invalid address, and the IRQL is too high.


I might call them if 3 or 4 business days go by without a fix, just to give a polite nudge.

[torrentg]

Turns out my crash issue (at least on Win 7) is due to an NVIDIA driver, Nvlddkm.sys, installed by version 306.23 of the NVIDIA graphics drivers for my card. I just installed these drivers over the weekend- just coincidence I installed the PCIe-424 the same week.

Haven't looked into the Win 8 crash yet.

That's still very likely due to MOTU. NVIDIA drivers almost never crash because of their own fault. Possible exception here or there may be SLI, and similar for Crossfire.

[torrentg]

Here is a different memory type of crash with the MOTU driver. It's a 0xA stop. MOTU, please see what you can do about these.

Before, I had some Suicidal Tendencies blasting and went away from the pc with nothing else but Winamp running. Heard a loud extremely high-pitched squeal at something like 15 kHz or higher. That actually was a 0x124 stop which is almost always hardware, but I don't have the issue when MOTU is turned off, ever.

But anyhow, as you can see, MOTU is in the stack trace of now this 0xA. And even in this 0xA, HAL is referenced.

LINK TO MINIDUMP:

http://www.4shared.com/file/SjmHQh-t/10 ... 59-01.html

Code: Select all

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {60018, 2, 0, 82c089e9}

*** WARNING: Unable to verify timestamp for motufwa.sys
*** ERROR: Module load completed but symbols could not be loaded for motufwa.sys
Probably caused by : ohci1394.sys ( ohci1394!OhciStartIo+97b )

Followup: MachineOwner
---------

1: 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: 00060018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82c089e9, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d9a828
Unable to read MiSystemVaType memory at 82d7ad80
 00060018 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalBuildScatterGatherList+175
82c089e9 8b5018          mov     edx,dword ptr [eax+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 82c08c16 to 82c089e9

STACK_TEXT:  
a84e3a88 82c08c16 880bfec8 872a8028 8603ab18 hal!HalBuildScatterGatherList+0x175
a84e3ab8 9372e0d5 87398640 872a8028 8603ab18 hal!HalGetScatterGatherList+0x26
a84e3b0c 82d070c8 872a8028 8603af00 872a965c ohci1394!OhciStartIo+0x97b
a84e3b30 9372e7a2 872a8028 8603af00 00000000 nt!IoStartPacket+0x85
a84e3b70 82c6a04a 872a8028 8603af00 85fda250 ohci1394!OhciIOCtl+0x542
a84e3b88 93742cbf a84e3bb4 93742f18 872f2008 nt!IofCallDriver+0x63
a84e3b90 93742f18 872f2008 85fda250 8603af00 1394BUS!Bus1394IsochChainToPort+0x1d
a84e3bb4 9373ded8 85fda250 8603af00 87c3d940 1394BUS!Bus1394DispatchIsochRequest+0x36
a84e3bdc 82c6a04a 87c3d940 8603af00 85fda250 1394BUS!Bus1394IOCtl+0x2b6
a84e3bf4 91e9160c 85fda3c8 000000ba 87c36000 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
a84e3c08 91e92395 85fda238 00000006 000000ba motufwa+0x3260c
a84e3c28 91e916b4 a84e3c48 91e917bf 85fda3c8 motufwa+0x33395
a84e3c30 91e917bf 85fda3c8 00000000 85fda3c8 motufwa+0x326b4
a84e3c48 91e919ab 85fda3c8 85fc29b8 a84e3c88 motufwa+0x327bf
a84e3c58 91e9870a 00000000 91e96f89 85fda470 motufwa+0x329ab
a84e3c88 91e988d2 00000000 85fc2b08 85fc2b10 motufwa+0x3970a
a84e3ce0 91e98dbc 85fda470 91e9154f a84e3d24 motufwa+0x398d2
a84e3cf0 91e91fd8 85fda230 00000000 87e28738 motufwa+0x39dbc
a84e3d24 91e7a600 00000000 859b8520 00000000 motufwa+0x32fd8
a84e3d50 82e2350a 87e28738 95347ddb 00000000 motufwa+0x1b600
a84e3d90 82cc4879 91e7a590 87e28738 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

[PedroCruz]

Hello Guys,
This week i built a new PC for live audio recording which i intend to work with an old PCI 424 and 2x2408mk3.
I installed WIN8 and fitted the pci424, installed drivers, and i get BSOD aswell on a cold-start, and after rebooting it seems fine...
Every time i cold start the PC i get that BSOD.
Does anyone have news about this issue???
All drivers, updates etc are the latest! bios, motu driver, win8 updates, nuendo version etc etc

Thanks guys!

[UltimateOutsider]

Every time i cold start the PC i get that BSOD.
Does anyone have news about this issue???
All drivers, updates etc are the latest! bios, motu driver, win8 updates, nuendo version etc etc

Unfortunately, according to MOTU, their products currently support Windows 8, so I don't expect much investigation on this on their end until people start submitting support tickets. The version of drivers they recommended is the same one I experienced BSODs with, and where I experienced crummy DAWBench performance on PCIe-424 and Ultralite-mk3 on Win 8 vs. Win 7.

[PedroCruz]

Every time i cold start the PC i get that BSOD.
Does anyone have news about this issue???
All drivers, updates etc are the latest! bios, motu driver, win8 updates, nuendo version etc etc

Unfortunately, according to MOTU, their products currently support Windows 8, so I don't expect much investigation on this on their end until people start submitting support tickets. The version of drivers they recommended is the same one I experienced BSODs with, and where I experienced crummy DAWBench performance on PCIe-424 and Ultralite-mk3 on Win 8 vs. Win 7.

Hi and thank you!
At least is good to know this is common and im not the only one, and maybe my choice of Hardware is ok, and its only a driver issue!
Although after the BSOD and system reboot, i dont notice any performance diference.
System starts up fast, Nuendo starts fast and i can listen to a 56 track through 2408mk3...
Weird hummm?

[UltimateOutsider]

Hi and thank you!
At least is good to know this is common and im not the only one, and maybe my choice of Hardware is ok, and its only a driver issue!
Although after the BSOD and system reboot, i dont notice any performance diference.
System starts up fast, Nuendo starts fast and i can listen to a 56 track through 2408mk3...
Weird hummm?

The performance difference is only noticeable in projects with huge numbers of active plugins or notes of polyphony. On Win 8 the audio stream breaks down under much less system strain on Windows 8 than on Windows 7 (with the current interfaces and the latest drivers). Day-to-day usage is pretty much the same. You only feel the difference if you really push your system hard.

EDIT: My Virus TI performed exactly the same in interface mode on both OSes, on the other hand (unfortunately it's a pretty crummy interface), and my NI KA6 only performed about 12% worse (versus up to 43% worse for the MOTUs), so it really seems to vary by driver. I haven't found a single reason to switch to Win 8 though, so I only keep that partition around for experimentation in hopes that MOTU releases some new drivers.

[PedroCruz]

Unfortunately i had no chance yet to test the system performance after the BSOD in win8, as soon as i can, ill let you know what i get from it.
ive just contacted motu tech support to see what they say about it, but i imagine the guys know about this already pretty well...
Cheers

[PedroCruz]

Hi Guys!
So ive contacted Motu Support team, and i got a reply very quickly saying they are aware of this problem and it should be fixed in the next driver update...
I believe it would be nice to share with you guys
Fingers crossed!
All the best!