Topic: Win7 +FFUC = Blue Screen

I have FFUC working perfectly in OSX (Logic/VLC/iTunes), however when trying to use it in Win7 I quickly get a Blue Screen of death from usb_driver.

I've tested with both Win7 32 and 64 bit fresh install
I use latest RME firmware and drivers available on RME web site.
I switch to appropriate PC/AP mode before booting OS.

The only variable here is OS and RME firmware/drivers.  The hardware is exactly the same in both cases - Intel DP35DP (ICH9R).

2

Re: Win7 +FFUC = Blue Screen

You use the latest Win or Mac firmware? The latest Mac firmware might cause problems under Windows. It should not, but so far it is not released for Windows, therefore you might be the only one experiencing this right now.

Regards
Matthias Carstens
RME

Re: Win7 +FFUC = Blue Screen

I am using the latest drivers available under downloads for FFUC on the main web site.
I've got Firmware 91 from 09/03/2009.  I even reset the firmware and applied version 91 from Win7 in case windows firmware process is different from OSX, but it seems to be exactly the same.  Only PC/AP selection changes the actual firmware used in the given OS.
Windows driver version 0.938 from 03/30/2010

I am not using any drivers that were posted on the forums.

Re: Win7 +FFUC = Blue Screen

I've run a debugger against minidump that windows generated and this is what I got:

Probably caused by : fireface_usb_64.sys ( fireface_usb_64+6744 )
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp
    that is already pending in the USB bus driver.
Arg2: fffffa8005d30350, Address of IRP
Arg3: fffffa800544f568, Address of URB
Arg4: fffffa80055d4a60

LAST_CONTROL_TRANSFER:  from fffff88003ce5eb7 to fffff800028d8f00

STACK_TEXT:  
fffff880`02b279c8 fffff880`03ce5eb7 : 00000000`000000fe 00000000`00000004 fffffa80`05d30350 fffffa80`0544f568 : nt!KeBugCheckEx
fffff880`02b279d0 fffff880`03cf1356 : fffffa80`04c81000 fffffa80`052a5530 00000000`00000000 fffffa80`04c81050 : USBPORT!USBPORT_Core_DetectActiveUrb+0x127
fffff880`02b27a20 fffff880`03cf9d44 : fffffa80`05d30350 fffffa80`051a0009 fffffa80`05d30350 fffffa80`0544f568 : USBPORT!USBPORT_ProcessURB+0xad6
fffff880`02b27ad0 fffff880`03cd3ad4 : 00000000`00000000 fffffa80`051af050 fffffa80`060f4320 fffffa80`05d30350 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`02b27b10 fffff880`042cc566 : fffffa80`051b1050 fffffa80`0531e060 fffffa80`05d30350 fffffa80`051b11a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`02b27b50 fffff880`042fccab : 00000000`00000000 00000000`00000000 fffffa80`0531e060 fffffa80`060ed250 : usbhub!UsbhFdoUrbPdoFilter+0xde
fffff880`02b27b80 fffff880`042cafb7 : 00000000`00000000 fffffa80`05d30350 fffffa80`0544b1a0 00000000`00000000 : usbhub!UsbhPdoInternalDeviceControl+0x373
fffff880`02b27bd0 fffff880`04212744 : fffffa80`05485840 fffffa80`05d30350 fffffa80`0544b1a0 00000000`00000000 : usbhub!UsbhGenDispatch+0x57
fffff880`02b27c00 fffff880`042128fd : 00000000`00000000 fffffa80`0544b1a0 fffffa80`0544fc34 fffffa80`0544fc28 : fireface_usb_64+0x6744
fffff880`02b27c30 fffff880`0420e0a1 : fffffa80`060ed250 00000000`00000240 00000000`00000080 fffffa80`0544b1a0 : fireface_usb_64+0x68fd
fffff880`02b27c70 fffff880`04211572 : fffffa80`00000240 fffffa80`05451850 fffffa80`05451850 00000000`00000000 : fireface_usb_64+0x20a1
fffff880`02b27ce0 fffff800`02b7c166 : fffffa80`05497040 00000000`00000080 fffffa80`039434a0 00000000`00000001 : fireface_usb_64+0x5572
fffff880`02b27d40 fffff800`028b7486 : fffff800`02a51e80 fffffa80`05497040 fffffa80`03958680 fffff880`0125fa90 : nt!PspSystemThreadStartup+0x5a
fffff880`02b27d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fireface_usb_64+6744
fffff880`04212744 488b6c2438      mov     rbp,qword ptr [rsp+38h]

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  fireface_usb_64+6744

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fireface_usb_64

IMAGE_NAME:  fireface_usb_64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb45f68

FAILURE_BUCKET_ID:  X64_0xFE_fireface_usb_64+6744

BUCKET_ID:  X64_0xFE_fireface_usb_64+6744

I can upload dump files if necessary. 
Can we get an RME Windows driver developer look at this?

Thanks.

5

Re: Win7 +FFUC = Blue Screen

Thanks, the developer is looking into this.

Regards
Matthias Carstens
RME

Re: Win7 +FFUC = Blue Screen

In which situation do you get this BSOD?
Did you try the mediaplayer?
Which format/samplerate did you select? (e.g. 48kHz, 2 Channels, 24 Bit)
Are you able to change the settings (e.g. Phantom Power)?

/Uwe

Re: Win7 +FFUC = Blue Screen

I get BSOD a second after trying to play any WDM audio through any player including windows media player, vlc or even test sound output when configuring speaker setup.  I only hear sound coming out for a second before everything stops, shortly followed by BSOD message.
First I had it at default setting of 44Khz, same issue with 48Khz. 
Yes I can change the settings otherwise, I can see the volume slider move as I rotate the dial on the device and vice versa the numbers on FFUC change when I move the slider inside of totalmix.  External inputs work and are reflected in totalmix too, so there is definitely communication between the computer and the card and the drivers are working, but it's the WDM playback that causes a problem.

Re: Win7 +FFUC = Blue Screen

Hello vigor,

you are not alone with the bluescreen. I open a new task.

http://www.rme-audio.de/forum/viewtopic.php?id=8114

Sascha

Re: Win7 +FFUC = Blue Screen

Hello Sascha,

Thank you for your post, but I am not sure our issues are identical.  We are both experiencing the BSOD from the same driver but Arg1 is different.  In any case, the driver is far from perfect.  It should not be possible to cause BSOD regardless of options and parameters selected, especially when the system is stable using another sound card.

Uwe, if you or another developer would like to take a look at my system configuration I'd be happy to let you in through remote connection.

Re: Win7 +FFUC = Blue Screen

I've narrowed down this issue happens only when I have another USB device on the same USB High-Speed Bus.  The funny thing is OSX installation helped me here as it shows USB Device Tree in System Profiler.  If I move the other USB device to a different USB High Speed Bus everything works fine on Win7.   However this is still an RME windows driver issue, because when I run OSX on the same machine there is no problem sharing USB High-Speed Bus between this USB device and RME FFUC.  This doesn't seem to be a bandwidth issue  as win7 reports RME is using 26% of bandwidth, 20% is reserved and 1% is used by the other USB device.

I found that my motherboard has 2 USB High-Speed Buses.  One serves 6 usb ports on the back and the other serves 2 usb ports on the front of the case.

Hopefully this will be helpful to someone experiencing similar problems until the drivers are fixed.

11

Re: Win7 +FFUC = Blue Screen

Thanks for the additional information, this might help. BTW, the busses and real connection to the USB controller is shown in Device manager too - see FF UC manual...

Regards
Matthias Carstens
RME