Topic: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

Hi,

Fireface 400 driver version : 3.124
Hardware revision : 1.70
Operating System : Windows 10 Pro x64 (French) 1809 update (installed 5 october 2018)

After one hour playing music (using AIMP freeware application), Windows crashes (blue screen of death)

This is the WhoCrashed Crash Dump Analysis

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: AF-PC
Windows version: Windows 10 , 10.0, build: 17763
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., ROG MAXIMUS X HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17105346560 bytes total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 07/10/2018 09:32:43 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100718-15187-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80278217FDE)
Bugcheck code: 0xA (0xFFFF8B85A0DBEEA8, 0x2, 0x0, 0xFFFFF80278217FDE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 07/10/2018 09:32:43 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fireface_64.sys (fireface_64+0x3DCA)
Bugcheck code: 0xA (0xFFFF8B85A0DBEEA8, 0x2, 0x0, 0xFFFFF80278217FDE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\fireface_64.sys
product: Windows (R) Win 7 DDK driver
company: RME
description: Fireface Audio Driver (WDM)
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: fireface_64.sys (Fireface Audio Driver (WDM), RME).
Google query: fireface_64.sys RME IRQL_NOT_LESS_OR_EQUAL

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

======> fireface_64.sys (Fireface Audio Driver (WDM), RME)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

2

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

You should roll back to 1803.

Regards
Matthias Carstens
RME

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

BTW ... Microsoft withdraws 1809 upgrade because of issues for some users (loss of user data).

https://www.heise.de/newsticker/meldung … 82651.html

BR
Ramses
X10SRi-F, E5-1650v4, Win10Pro21H1, Cub11Pro, UFX+, XTC, 12Mic, ADI-2 Pro FS R BE, RayDAT

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

Back to Windows 10 1803. No more crash.

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

I answered too fast. Same problem with 1803.
This time the crash occurs approximately 1 hour and 30 minutes after playing music with AIMP.

On Mon 08/10/2018 12:50:06 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fireface_64.sys (fireface_64+0x3DCA)
Bugcheck code: 0xA (0xC80000002C, 0x2, 0x0, 0xFFFFF8010C6329DB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\fireface_64.sys
product: Windows (R) Win 7 DDK driver
company: RME
description: Fireface Audio Driver (WDM)

6

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

You did not write about two important things: since when do you have that crash? And how loong do you own the FF400? What is your FireWire card and chip used in that computer?

Regards
Matthias Carstens
RME

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

Crash since... yesterday (07 october)
Crash only with the WDM driver (FF400 settings : 1 WDM device).  ASIO driver works very well when I use Cubase 9.5

I have the FF400 since 2009

Noname PCI-E IEEE1394a (2P+1P) CARD (F-261)
Part : IE-T08-2121-00-00012
TI chipset XIO2200A

Regards.

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

XIO2200A is a bogus TI chipset.

BR
Ramses
X10SRi-F, E5-1650v4, Win10Pro21H1, Cub11Pro, UFX+, XTC, 12Mic, ADI-2 Pro FS R BE, RayDAT

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

Hello, I wasusing FF400 for many years with a Macbook pro 2007 over Firewire, never a problem. Last August after a lot of research I decided to switch to Windows and got a very good zBook laptop from HP running Windows 10. I soon encountered the problems others have noticed: clicks and system crashes. I use the Apple double-dongle solution (TB3-TB2-FW800). It seems to consistently recognise the FF400 and on that level everything is fine. I would love to be able to keep using the FF with my new machine, rather than buying an expensive new interface, though if I must I will do it. I know RME is consistently updating the old drivers, do you think this is something which might possible be adressed? Thank you in advance. Unfortunately the sound problems are inconsistent. Sometimes days pass no problem, then while screening a video during a performance the laptop clicks, peeps and after some minutes just crashes, leaving the Fireface emitting a long steady squarewave. Very frustrating.

10 (edited by firefacefan 2019-03-14 20:29:43)

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

To any Fireface400 users on Windows 10, please read this carefully if you are getting the blue screen of death:

I also regularly had the blue screen of death after going to Windows 10, with the "IRQL_NOT_LESS_OR_EQUAL" message. And when it wasn't giving me the BSOD I would get clicks/glitches when trying to things like Youtube videos. Turns out this is not a problem with the Fireface400 and it's drivers at all, it's a problem with the 1394 OHCI Compliance Host Controller driver on Windows 10.

This problem can be fixed by installing the legacy 1394 OHCI driver instead of using the standard Win 10 driver:
https://www.studio1productions.com/Arti … wire-1.htm

I can confirm that since installing and using the legacy driver I have not had a single BSOD, not even one - where previously it was a daily occurence.

Hope that helps 000masa000 and others, your problem sounds similar to mine (it would often crash when I was playing youtube videos).

Another recent problem I have had with the Fireface was I was getting a horrible distorted sound on all outputs, which had been getting worse and worse over a few months - the very loud distortion was not shown in TotalMix channel meters which made me realise it was a hardware issue. I was honestly starting to contemplate that my good old reliable Fireface was finally going to die after many many years of faithful service - but I thought I would try one thing, replacing the power supply. I googled the model number of the old power supply, and although I was not able to find the exact same one I found a replacement on ebay. Literally got it in the post today and can confirm this has also resolved the issue - the Fireface400 is now working perfectly with a new power supply! It's an understatement to say I am extremely happy!

I am utterly amazed at the build quality of the Fireface400, which is AT LEAST 10 years old (possibly 13 or 14 years, can't quite remember the exact year I bought it). It has been absolutely rock solid until recently, and as discussed above it was the power supply (which wasn't developed by RME) which failed and not the unit itself. One of the best investments I have ever made - if anyone from RME is reading this and was involved in the development of the 400, well done

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

Dear firefacefan, I tried the same approach, but in my case the legacy driver isn't working. I guess you might have a different Firewire card/port. In my situation, I only have Thunderbolt 3 or USB on my laptop, a new zBook from HP which is fully functional on all other fronts, but without FW port, so I am using the (currently) only available solution: a double dongle from Apple which converts TB3 to TB2 and then on to FW800, then linked to FF400 by a FW800 to FW400 cable. Since everything works (in terms of the FF showing up) I don't think cabling is the issue. But when I switched to legacy drivers, even with buffer set high I had frozen audio (squarewave) and massive glitching. Regular driver works a little better, but not professionally useable. So disappointed because as you say, the hardware is FINE! The device works perfectly on a new Macbook with the same adapter and cable, so it is Windows 10 driver Firewire issues. I wish this would work!

12

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

The Apple TB3 to TB2 adapter IMHO is not certified for the HP. You might (no guarantee) have more luck with the StarTech TB3 to TB2 adapter.

Regards
Matthias Carstens
RME

13 (edited by idomaimon 2021-09-15 02:35:58)

Re: WARNING: Fireface 400 crashes with last update of Windows 10 Pro x64

Oh lawd
i need an urgent help with this issue

Since the last update of win 10 (2004, updated on 06/06/21) I got all of there crashes, restarts (especially when changing buffer size and its really embarassing in front of the singer/customer to restart the computer in a middle of a session)

FireFace 400, WIN 10 PRO 2004. original chip by Texas instruments (1394 OHCI) inside my computer.

i offer even to pay somebody who will save me with this one
i can't roll back windows updates
and i dont understand what should i do with the bios or the legacy driver
plz help me
im going to read the whole thread and try once again, but i need a pro here

ido@idomaimon.com
+972-52-6366527

ATTACHING CRASH REPORT:
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: ffffd795fc2f1558, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80360873a28, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3327

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 25197

    Key  : Analysis.Init.CPU.mSec
    Value: 374

    Key  : Analysis.Init.Elapsed.mSec
    Value: 10957

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 82

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffd795fc2f1558

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80360873a28

READ_ADDRESS: fffff803610fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffd795fc2f1558

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

DPC_STACK_BASE:  FFFFF80366816FB0

TRAP_FRAME:  fffff80366816780 -- (.trap 0xfffff80366816780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000d783bfb9 rbx=0000000000000000 rcx=ffffd78f40ba45b0
rdx=ffffd78f40111760 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80360873a28 rsp=fffff80366816910 rbp=0000000000000510
r8=ffffd78f410ff8b8  r9=0000000000000510 r10=ffffd78f40ba45b0
r11=fffff80366816860 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!HalPutScatterGatherList+0x144c88:
fffff803`60873a28 4d8b6cc630      mov     r13,qword ptr [r14+rax*8+30h] ds:00000006`bc1dfdf8=????????????????
Resetting default scope

STACK_TEXT: 
fffff803`66816638 fffff803`60808e69     : 00000000`0000000a ffffd795`fc2f1558 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff803`66816640 fffff803`60805169     : fffff803`66816819 fffff803`606854b7 00000000`00000000 fffff803`6104b978 : nt!KiBugCheckDispatch+0x69
fffff803`66816780 fffff803`60873a28     : 00000000`00000004 ffffd78f`394eba10 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
fffff803`66816910 fffff803`643d52fa     : 00000000`00000000 ffffd78f`41194140 00000000`00000000 ffffd78f`410ff8b8 : nt!HalPutScatterGatherList+0x144c88
fffff803`66816990 fffff803`643d55fa     : ffffd78f`41194140 ffffd78f`348e0cc8 ffffd78f`00000000 00000000`00000000 : Wdf01000!FxDmaScatterGatherTransaction::PutScatterGatherList+0x46 [minkernel\wdf\framework\kmdf\inc\private\FxDmaTransactionScatterGather.hpp @ 197]
fffff803`668169c0 fffff803`643d65f3     : fffff803`741fc170 fffff6d4`53d75364 00000000`00000000 00000000`00000000 : Wdf01000!FxDmaScatterGatherTransaction::TransferCompleted+0x1a [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionscattergather.cpp @ 479]
fffff803`668169f0 fffff803`643d01f7     : fffff803`66816ae0 fffff803`66816c00 ffffd78f`348e0cc8 ffffd78f`396a2e78 : Wdf01000!FxDmaTransactionBase::DmaCompleted+0x13f [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionbase.cpp @ 542]
fffff803`66816a70 fffff803`741d7fe7     : ffffd78f`41194140 00000000`00000000 ffffb381`7b1c5000 ffffd78f`41804800 : Wdf01000!imp_WdfDmaTransactionDmaCompletedFinal+0x57 [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionapi.cpp @ 654]
fffff803`66816aa0 fffff803`741e43e3     : fffff803`00000000 00000000`07d1c000 fffff803`66816c00 fffff803`66816e70 : 1394ohci!IoWorkers::FlushWdfDmaTransaction+0x3b
fffff803`66816ae0 fffff803`643b940b     : ffffd78f`418046f0 00000000`00400a00 fffff803`66816cb0 fffff803`66816e70 : 1394ohci!IsochTx::WdfEvtNotificationDpc+0x183
fffff803`66816b70 fffff803`6069a3be     : fffff803`5d423240 ffffd78f`307ec000 fffff803`66816e80 fffff803`00000002 : Wdf01000!FxDpc::FxDpcThunk+0x5b [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 361]
fffff803`66816bb0 fffff803`606996a4     : fffff803`5d420180 00000000`00000000 00000000`00000029 00000000`000646ef : nt!KiExecuteAllDpcs+0x30e
fffff803`66816d20 fffff803`607fdf65     : 00000000`00000000 fffff803`5d420180 ffffb381`7b1c5640 00000000`00000000 : nt!KiRetireDpcList+0x1f4
fffff803`66816fb0 fffff803`607fdd50     : 000000c3`07bfdcf0 fffff803`60725e2a ffffd78f`00000000 ffffd78f`3fc79080 : nt!KxRetireDpcList+0x5
ffffb287`c2c1f9c0 fffff803`607fd605     : 00000000`00000000 fffff803`607f8271 00000d82`00211418 ffffd78f`3fc79080 : nt!KiDispatchInterruptContinue
ffffb287`c2c1f9f0 fffff803`607f8271     : 00000d82`00211418 ffffd78f`3fc79080 00000d82`002b5058 ffffb287`c2c1fa80 : nt!KiDpcInterruptBypass+0x25
ffffb287`c2c1fa00 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1


SYMBOL_NAME:  1394ohci!IoWorkers::FlushWdfDmaTransaction+3b

MODULE_NAME: 1394ohci

IMAGE_NAME:  1394ohci.sys

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  3b

FAILURE_BUCKET_ID:  AV_1394ohci!IoWorkers::FlushWdfDmaTransaction

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fa13b40e-ecf1-fe22-8656-05ff0d55a01a}

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