Topic: UFX+ MADI crashes

Hello
I have the UFX+ configured in a MADI daisychain with a Ferrofish a32pro and Ferrofish Pulse 16 DX and I'm trying to track down the source of these BSOD crashes. All three devices show solid MADI sync and the devices route audio as expected.

The crash only seems to happen when opening Ableton and while loading it will time out and give a DPC_WATCHDOG_VIOLATION and crash.

I've tried just about everything to attempt to fix this including: Flash to latest firmware, Remove rme driver and upgrade/downgrade to various versions, Look through the memory dump with winDBG & event Viewer, Change NVIDIA driver to studio driver, LatencyMon to hunt down and address DPC based dropouts, reinstalling drivers for a bunch of onboard peripherals,  even new USB cable, Changing power management settings amongst other things.

I was told to send the following data that we get from the WinDBG logs:

The dae7 offset in the FAILURE_BUCKET_ID points to a specific location inside madiface_usb_64.sys that’s consistently failing. Combined with the identical FAILURE_ID_HASH across every crash, this is a reproducible bug in the 0.9845 driver on your specific hardware combination — AMD X870 + Ryzen + the way Windows 11 26100.1 schedules USB interrupts.

∙    FAILURE_BUCKET_ID: 0x133_DPC_madiface_usb_64!unknown_function
∙    FAILURE_ID_HASH: {606c54ec-6d64-c0ee-21ed-5e9e952bfcd5}
∙    OS: Windows 11 26100.1
∙    Hardware: ASUS ROG STRIX X870-A, AMD Ryzen

Let me know if I can help determine if this is a configuration issue on my end or a legitimate bug?
thank you
kris

Re: UFX+ MADI crashes

To find out if it is a bug or failure of the interface, I would do some tests with another DAW, Reaper.
cost no money and is done over night

M1-Tahoe, Madiface Pro, Digiface USB, Babyface silver and blue

3

Re: UFX+ MADI crashes

Current driver is 1.015. Was that one tested?

Is the UFX+ on the latest firmware state which is

Fireface UFX+ (Hw. Rev. A): USB 55 DSP 62 Thunderbolt 112
Fireface UFX+ (Hw. Rev. E): USB 72 DSP 62 Thunderbolt 167

?

Regards
Matthias Carstens
RME

Re: UFX+ MADI crashes

MC wrote:

Current driver is 1.015. Was that one tested?

Is the UFX+ on the latest firmware state which is

Fireface UFX+ (Hw. Rev. A): USB 55 DSP 62 Thunderbolt 112
Fireface UFX+ (Hw. Rev. E): USB 72 DSP 62 Thunderbolt 167

?

yes, the error I posted was from the end of a day of testing where I attempted to rollback the driver.
Currently 1.015 with Fireface UFX+ (Hw. Rev. A): USB 55 DSP 62 Thunderbolt 112 firmware.

5

Re: UFX+ MADI crashes

DPC Watchdog violation I have never seen/heard of with USB, but with Thunderbolt.

Current Windows 11 on my system is 26200.

The issue might also lie in outdated USB support for your AMD system - just a theory from history, I have no current info on that.

As you can read here in the forum we do have lots of AMD users, still you are the only one with such an error. Therefore it's quite hard to provide efficient help.

Regards
Matthias Carstens
RME

Re: UFX+ MADI crashes

Having the same issue with a UFX 3, issue also started after adding a second Ferrofish Pulse 16 MX to a daisy chain.
Everything is on latest firmware and driver. Also running an AMD CPU (x870e motherboard).

Here is one of the WinDbg dump extracts:
- SYMBOL_NAME:  madiface_usb_amd+1c284

MODULE_NAME: madiface_usb_amd

IMAGE_NAME:  madiface_usb_amd.sys

STACK_COMMAND: .process /r /p 0xfffff805f19cef00; .thread 0xfffff805f19d15c0 ; kb

BUCKET_ID_FUNC_OFFSET:  1c284

FAILURE_BUCKET_ID:  0x133_DPC_madiface_usb_amd!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3545975a-2cac-c662-5b61-361929cec39a}

Followup:     MachineOwner.

Re: UFX+ MADI crashes

Switched to driver 1.0.5.0, seems to run better?

Re: UFX+ MADI crashes

Hi, stumbled upon this thread researching this- Just recently built a new computer and switched from intel to amd- running a 9950x3d on a x870E (asrock taichi lite) and Fireface UFX + , internal UAD octo card. I have the same BSOD issues when loading ableton (its a crapshoot) and sometimes when loading windows (windows would go into a bootloop sometimes). I found a work around by removing the extra outputs that are not in use in the device manager (as it seems to create new driver entries everytime you switch sample rate/bit rate)
Im running the latest bios and drivers available.