1 Topic by jcitarello (edited by jcitarello 2010-01-27 05:22:54)

  • Registered: 2010-01-27
  • Posts: 17

Topic: Windows 7 Crashing (iMac 24)

I own a Fireface 800 and have recently installed the retail release of Windows 7 (32 bit) on my iMac 24 using bootcamp.  Along with the install, I updated my firmware and driver to the latest versions. My system is now crashing with a blue screen intermittently with any of the Windows media programs.  I haven't yet installed my DAW (Sonar 6 PE), as I'd like to get this resolved first.  It seemed to work fine with the Beta version using the previous drivers/firmware.  What do I need to do to troubleshoot?

BTW, I had captured the error after it rebooted but I overwrote is with your forum password.  I'll be sure to grab it next time. 

Thanks!

  • Registered: 2008-01-01
  • Posts: 3,025

Re: Windows 7 Crashing (iMac 24)

Bootcamp 3.1 update installed?

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Nope, 2.1 currently.  Is this available from the Apple site?  I did however update both the video and network drivers from the Nvidia site directly.  I will take a look and see if I can locate 3.1.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Now here's another question, do you know if Windows 7 64 is now fully supported by Apple?  I had read that there were some issues with a few of the drivers including the camera.  As mentioned, I did install the 32 bit version based on what I had read.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Ack!  I already have Windows 7 32bit installed and it's 2.1.  Apples instructions state:

Upgrading the Boot Camp Drivers
If you?ve already installed Windows on this computer, you can install the updated
Mac drivers for Windows.
Important: If you?ve customized your Windows environment, write down your settings
before updating the drivers.
To update the Boot Camp drivers for Windows:
1 Restart your Mac using Windows.
2 Click the Boot Camp icon in the system tray and choose About Boot Camp.
3 If the version is 3.0 or later, use Apple Software Update to check for updated drivers.
4 If the version is earlier than 3.0, insert your Mac OS X version 10.6 installation disc.
When the installer starts, click Repair.

Do I *NEED* to order the Snow Leopard disk in order to acquire the 3.0 version of the drivers or is there another way?  I honestly have no interest whatsoever in upgrading the Mac side as I never use it.  The disc is $29 but still, pointless for me as far as I can see.

  • Registered: 2008-01-01
  • Posts: 3,025

Re: Windows 7 Crashing (iMac 24)

http://www.apple.com/downloads/macosx/apple/windows/

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Timur, I am confused.  I can see where you can download 3.1, but the instructions state: 

"If the version is earlier than 3.0, insert your Mac OS X version 10.6 installation disc.
When the installer starts, click Repair."

I am on 2.1 currently.  Does anyone know if I can download 3.0 seperately somewhere without buying the stinky disc?

  • Registered: 2008-01-01
  • Posts: 3,025

Re: Windows 7 Crashing (iMac 24)

I didn't check, but knowing Apple as what it is I would say: You have to buy the stinking disc.

Did you try downloading the 3.1 update and just run it over your 2.1 installation? The update installer does *not* ask for the disc, it just runs on top of the already installed 3.0 drivers.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

I tried it, didn't work.  Stinky disk ordered and I will reinstall with the 64 bit version of Win7.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Same problem, sent some files off to support, but this may be of interest....


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Joseph\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
Debug session time: Sat Jan 30 17:21:55.183 2010 (GMT-6)
System Uptime: 0 days 0:07:27.275
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd5018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80002a077f7}

*** ERROR: Module load completed but symbols could not be loaded for fireface_64.sys
PEB is paged out (Peb.Ldr = 000007ff`fffd5018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd5018).  Type ".hh dbgerr001" for details
Probably caused by : 1394ohci.sys ( 1394ohci!IsochTx::Release+e1 )

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

0: 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: 0000000000000008, 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: fffff80002a077f7, address which referenced memory

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

PEB is paged out (Peb.Ldr = 000007ff`fffd5018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd5018).  Type ".hh dbgerr001" for details

READ_ADDRESS:  0000000000000008

CURRENT_IRQL:  2

FAULTING_IP:
hal!HalPutScatterGatherList+a7
fffff800`02a077f7 4d8b642408      mov     r12,qword ptr [r12+8]

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  audiodg.exe

TRAP_FRAME:  fffff88007fdc3e0 -- (.trap 0xfffff88007fdc3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000fff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a077f7 rsp=fffff88007fdc570 rbp=0000000000000930
r8=0000000000000000  r9=0000000000000930 r10=0000000000000024
r11=fffffa80051f50ac r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hal!HalPutScatterGatherList+0xa7:
fffff800`02a077f7 4d8b642408      mov     r12,qword ptr [r12+8] ds:9250:0008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002abd469 to fffff80002abdf00

STACK_TEXT: 
fffff880`07fdc298 fffff800`02abd469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07fdc2a0 fffff800`02abc0e0 : 00000000`00000000 fffffa80`041b77d0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`07fdc3e0 fffff800`02a077f7 : fffffa80`041b77d0 00000000`00000930 00000000`00000230 fffffa80`073ffba0 : nt!KiPageFault+0x260
fffff880`07fdc570 fffff880`00e86c65 : 00000000`00000000 0000057f`f9aa3700 00000000`00000001 00000000`00000000 : hal!HalPutScatterGatherList+0xa7
fffff880`07fdc5d0 fffff880`00e86793 : fffffa80`041b7890 fffff880`07fdc670 fffff880`04032638 00000000`00000014 : Wdf01000!FxDmaScatterGatherTransaction::ReleaseResources+0x39
fffff880`07fdc600 fffff880`00e8438a : fffffa80`040ca4d0 00000000`00000000 fffffa80`065b0014 fffff880`07fdc6b8 : Wdf01000!FxDmaTransactionBase::ReleaseForReuse+0x63
fffff880`07fdc650 fffff880`0401e125 : fffffa80`041b7890 0000057f`f9aa3700 00000000`00000001 00000000`00000001 : Wdf01000!imp_WdfDmaTransactionRelease+0x82
fffff880`07fdc690 fffff880`040166d9 : 00000000`00000000 0000057f`f9aa3788 fffffa80`0516cd90 fffffa80`03e41820 : 1394ohci!IsochTx::Release+0xe1
fffff880`07fdc700 fffff880`04015d25 : 0000057f`f9aa3788 0000057f`fae93618 00000000`00000028 fffffa80`0655c870 : 1394ohci!Isoch::HandleIsochFreeResources+0xe9
fffff880`07fdc750 fffff880`00eca047 : fffffa80`0655c870 fffffa80`04856cb0 fffffa80`04856cb0 fffffa80`04856cb0 : 1394ohci!Isoch::WdfEvtIoInternalDeviceControl+0x161
fffff880`07fdc7c0 fffff880`00ec999f : fffffa80`0516c9e0 fffffa80`0655c870 fffffa80`0516c9e0 fffffa80`0655c900 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`07fdc840 fffff880`00ec91ab : fffffa80`0516c9e0 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`07fdc8b0 fffff880`00ec7f1e : 00000000`00000000 fffffa80`0521d8d0 fffffa80`0516c9e0 fffffa80`0655c998 : Wdf01000!FxIoQueue::QueueRequestFromForward+0x1f7
fffff880`07fdc910 fffff880`00ec8555 : fffffa80`0516c900 fffff880`00ec8555 fffffa80`0521d8d0 fffff880`04032688 : Wdf01000!FxIoQueue::ForwardRequestWorker+0x17a
fffff880`07fdc980 fffff880`00ea5cd6 : 00000000`00000000 fffffa80`04856cb0 00000000`00000000 fffffa80`04856cb0 : Wdf01000!FxIoQueue::ForwardRequest+0x185
fffff880`07fdc9f0 fffff880`04012440 : fffffa80`0516c9e0 0000057f`f9aa3788 fffffa80`0655c870 fffffa80`0521dc80 : Wdf01000!imp_WdfRequestForwardToIoQueue+0x12e
fffff880`07fdca40 fffff880`04012181 : 0000057f`f9aa3788 0000057f`fade2728 00000000`00000028 fffffa80`0521dc80 : 1394ohci!Dispatch::DispatchIrbRequest+0xa8
fffff880`07fdca90 fffff880`00eca047 : fffffa80`0655c870 fffffa80`04856cb0 fffffa80`04856cb0 fffffa80`04856cb0 : 1394ohci!Dispatch::WdfEvtIoInternalDeviceControl+0x131
fffff880`07fdcb00 fffff880`00ec999f : fffffa80`0655c870 fffffa80`0655c870 fffffa80`0521d8d0 fffffa80`0521d8d0 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`07fdcb80 fffff880`00ec8f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0655c9c2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`07fdcbf0 fffff880`00ece558 : fffffa80`0446db00 fffffa80`0655c870 fffffa80`0446da60 fffffa80`0655c870 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`07fdcc60 fffff880`00eb8245 : fffffa80`0655c870 00000000`00000000 00000000`00000000 0000057f`f9ab1d88 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`07fdcce0 fffff880`00ea46d0 : 00000000`00000000 00000000`00000000 0000057f`f9ab1d88 fffff880`07fdcd90 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`07fdcd10 fffff880`0400fd0c : fffffa80`04856e00 fffffa80`0654e270 fffffa80`06511df0 fffffa80`0651dfc0 : Wdf01000!imp_WdfRequestSend+0x37c
fffff880`07fdcd60 fffff880`0400ff2b : fffffa80`03e41820 0000057f`f9ab1d88 fffffa80`066a5c30 0000057f`f9ab1d88 : 1394ohci!ChildDevice::DispatchIrbRequest+0x60
fffff880`07fdcdb0 fffff880`0400ef0d : 0000057f`f9ab1d88 0000057f`f9aeefd8 00000000`00000028 fffffa80`0651dfc0 : 1394ohci!ChildDevice::HandleIrbRequest+0x1c3
fffff880`07fdcdf0 fffff880`00eca047 : fffffa80`0654e270 fffffa80`04856cb0 fffffa80`04856cb0 fffffa80`04856cb0 : 1394ohci!ChildDevice::WdfEvtIoInternalDeviceControl+0x141
fffff880`07fdce60 fffff880`00ec999f : 00000000`00000000 fffffa80`0654e270 fffffa80`06511020 fffffa80`06511020 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`07fdcee0 fffff880`00ec8f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0654e3c2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`07fdcf50 fffff880`00ece558 : fffffa80`0446dc00 fffffa80`0654e270 fffffa80`0446da60 fffffa80`0654e270 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`07fdcfc0 fffff880`00eb8245 : fffffa80`0654e270 0000057f`fbf35c28 00000000`00000000 fffffa80`065a11a0 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`07fdd040 fffff880`03c21447 : fffffa80`0446da60 0000057f`fbf35c28 fffffa80`30384646 0000057f`0000022e : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`07fdd070 fffff880`03c1eefd : 00000000`00000000 00000000`00000000 00000000`00000002 fffffa80`065a11a0 : fireface_64+0xc447
fffff880`07fdd130 fffff880`03c25659 : 00000000`00000000 00000000`00000000 fffffa80`06532810 00000000`00000c00 : fireface_64+0x9efd
fffff880`07fdd170 fffff880`03c2634c : ffffffff`fff0bdc0 00000000`00000000 fffffa80`00000000 fffff880`04015f00 : fireface_64+0x10659
fffff880`07fdd1a0 fffff880`03c27467 : fffffa80`04067750 fffffa80`03fddd18 00000000`00000002 00000000`00000002 : fireface_64+0x1134c
fffff880`07fdd1e0 fffff880`03c42d85 : 00000000`00000003 fffff880`03c5efc5 fffff880`07fdd318 00000000`00000003 : fireface_64+0x12467
fffff880`07fdd220 fffff880`03c65813 : 00000000`00000002 00000000`00000002 00000000`00000000 00000000`00000028 : portcls!CPortPinWaveCyclic::SetDeviceState+0x59
fffff880`07fdd2a0 fffff880`03c64fed : fffffa80`03eaa7c0 fffffa80`03fddd00 00000000`00000000 fffffa80`03eaa7c0 : portcls!CPortPinWaveCyclic::DistributeDeviceState+0x57
fffff880`07fdd300 fffff880`0535a815 : fffffa80`03e08010 fffffa80`065a1050 fffffa80`051bb260 00000000`00000000 : portcls!PinPropertyDeviceState+0xa1
fffff880`07fdd340 fffff880`0536653f : fffffa80`03e08010 fffffa80`00000005 fffff880`07fdd460 fffff8a0`019ca620 : ks!KspPropertyHandler+0x735
fffff880`07fdd3b0 fffff880`03c56944 : fffff880`07fdd460 fffff8a0`019ca620 fffffa80`03e08010 00000000`00000000 : ks!KsPropertyHandler+0x1b
fffff880`07fdd400 fffff880`03c64d4c : 00000000`00000018 fffffa80`0659d900 fffffa80`03e08010 00000000`00000000 : portcls!PcHandlePropertyWithTable+0x64
fffff880`07fdd430 fffff880`03c55fa1 : fffffa80`03e08010 fffffa80`065a1050 fffffa80`065a11a0 00000000`00000002 : portcls!CPortPinWaveCyclic::DeviceIoControl+0x2bc
fffff880`07fdd4a0 fffff880`0535a01b : 00000000`c000000d 00000000`00000000 00000000`c000000e fffffa80`065a1050 : portcls!DispatchDeviceIoControl+0x79
fffff880`07fdd4d0 fffff880`03c5506c : 00000000`00000000 fffffa80`06468860 fffffa80`03e08248 00000000`00000000 : ks!KsDispatchIrp+0xdb
fffff880`07fdd500 fffff880`03c1b841 : 00000000`00000000 fffffa80`00000000 00000000`00000000 fffffa80`03fddd00 : portcls!PcDispatchIrp+0x5c
fffff880`07fdd530 fffff880`041f9674 : fffffa80`065a1050 fffffa80`00000000 fffffa80`03e08248 fffffa80`06468860 : fireface_64+0x6841
fffff880`07fdd840 fffff880`041f6c21 : 00000000`00000001 fffffa80`03e08290 fffff880`07fddb00 fffffa80`0435c800 : ksthunk!CKernelFilterDevice::SynchronousForwardIrp+0x70
fffff880`07fdd8a0 fffff880`041f6a87 : fffffa80`03e08005 fffffa80`03e08010 00000000`00000000 fffff880`07fdd9e0 : ksthunk!CKSThunkDevice::CheckIrpForStackAdjustmentNative+0x171
fffff880`07fdd940 fffff880`041f679b : 00000000`00000001 fffffa80`03e08290 fffffa80`06468860 fffffa80`03e08010 : ksthunk!CKSThunkDevice::DispatchIoctl+0xcf
fffff880`07fdd970 fffff800`02dd63a7 : fffffa80`0719ff20 fffff880`07fddc60 fffffa80`00000000 fffffa80`0719ff20 : ksthunk!CKernelFilterDevice::DispatchIrp+0x93
fffff880`07fdd9d0 fffff800`02dd6c06 : 00000000`0213f570 00000000`00000285 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07fddb00 fffff800`02abd153 : fffffa80`06bfdb60 00000000`0213f558 fffff880`07fddb88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`07fddb70 00000000`777cff2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0213f528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777cff2a


STACK_COMMAND:  kb

FOLLOWUP_IP:
1394ohci!IsochTx::Release+e1
fffff880`0401e125 410fb6f4        movzx   esi,r12b

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  1394ohci!IsochTx::Release+e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 1394ohci

IMAGE_NAME:  1394ohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc30

FAILURE_BUCKET_ID:  X64_0xA_1394ohci!IsochTx::Release+e1

BUCKET_ID:  X64_0xA_1394ohci!IsochTx::Release+e1

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

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

FYI, this is seeming more and more to me that I need to switch the 1394 driver back the "Legacy".  I thought this was supposed to be remedied with the latest Fireface driver?

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Well the iMac quickly corrected me on that assumption..still crashed with "Legacy" driver selected for 1394 fryingpan

  • Registered: 2008-01-01
  • Posts: 3,025

Re: Windows 7 Crashing (iMac 24)

Did you install Sonar yet? I'd really like to know if you run into troubles when *not* using a media player application.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

No, no Sonar installation as yet.  I guess I can try it sometime day and send you my findings.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Sonar installed up to 6.2.1, still "crashing", but I can kill the audio engine before it blue screens.  When it dies, the audio hangs and "stutters", before it dies.  Same thing with Media Player.  Sometimes it takes a longer than other times, but always consistent.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

So here's a question:  Does anyone have Windows 7 64 bit running a Fireface successfully on an iMac?  If so, what model do you have?  Mine is the 24" "Early 2009" breed.  Is there something about this particular model perhaps?  Also, how does one determine what firewire chipset is installed in one of these systems?  The driver in this case is not telling me a thing about it.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Hmm, no response in two days.  I get the feeling we'll see another driver shortly.  :-)

  • Registered: 2008-01-01
  • Posts: 3,025

Re: Windows 7 Crashing (iMac 24)

I had the FF400 running successfully on both a current Imac 21.5" and 27" (both use TI chipsets). But I just did some short test runs (mostly using ASIO).

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

Why do you (and others) keep insisting that the chipset is an issue?  TI might indeed make a superior chipset, but if the Agere (Lucent?) chipset was suspect,  I would expect to be having problems on both the Mac side and on XP.  This is not the case and both of which run flawlessly.  Also, unless I am missing something, the debug analysis seems to make it pretty clear that it's a driver issue and not a hardware issue.  Am I missing something here?

  • Registered: 2008-01-01
  • Posts: 3,025

Re: Windows 7 Crashing (iMac 24)

I'm successfully using LSI/Agere chipsets as well (rev. 6 needed a Repeater cable in between and rev. 7 works out of the box), both in Windows and OS X. If a chipset works in one OS it doesn't necessarily mean it works in another OS though, because drivers access hardware functions differently.

  • From: Gothenburg, Sweden
  • Registered: 2007-05-01
  • Posts: 441

Re: Windows 7 Crashing (iMac 24)

Hi,

To my knowledge Apple and Texas Instrument, Sony, IBM develop the firewire chipset technic together
and TI have been the leading one in this field and LSI/Agere is a newer company I belive
good technic will cost some more but in the end it pays off. JMHO :-)

http://en.wikipedia.org/wiki/IEEE_1394_interface

regards S-EH

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

So what do I need to do to get this working?  Should I expect that you will eventually fix this problem at the driver level?  I need some real answers here folks.

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

No one?  Anyone?  Hello?  Five days since I sent this information to support and no formal response, what gives?  Is this all I can expect to hear on the matter?  I was really hoping to hear that someone is working in this and I can expect something soon, but no such response has been received.

Here's my take:  TI is quickly becoming a less and less used chipset. In fact, I've only been able to identify two laptop manufacturers that are actually installing these anymore.  Apple & HP.  Even then, it's apparently a crap-shoot as to whether they are going to stick these in the latest models.  Given that the Agere chipsets work without issue in both the Mac OS and XP, the only logical conclusion I can come to is that this is strictly a driver defect and RME should be responsible to fix it.  Here's the real kicker, *ALL* the audio interface manufacturers have spread completely erroneous rumors trying to convince everyone that TI is the only chipset that works, when in fact, it's the freakin driver that is the culprit "...because because drivers access hardware functions differently".  Ricoh worked just dandy in my E1705, and as mentioned already, the Agere set works great on the iMac in both Leopard and XP. 

Currently, these are my options, none of which appeal to me in the least:

1.  Sell my six month old iMac and buy a new one, with a smaller screen for the same money.  Cost:  At least $500 in deprecation between the two.  Plus, the 179$ I spent on Windows 7 and $29 I spent on the useless Snow Leopard disc.

2.  Sell the Fireface 800 and swap it for the UC, though I am not even sure this is a solution.  Cost:  At least $500 in depreciation between them.

3.  MOTU claims that their driver has no such issues with the Agere chips in the iMac under Boot Camp. Cost:  0$ as the MOTU 828mk3 is about the same price as I could get for the Fireface.  Chances are better than average that this may actually be true.  More research is needed.

4.  (..and this is my personal favorite!)  Sell both the iMac and the Fireface out of spite because this problem should have been solved by now, and neither of you can apparently agree on who's responsible for fixing it.  In the meantime, us as customers are getting the deep-dark unlubricated shaft because neither of you can agree on who's responsibility it is, or much less what to do about it.

I guess what I really need to do is start posting my findings over at Gearslutz and few other forums so people can actually see for themselves that it's not the chipset but the drivers that are the are causing this issue.  Maybe if we make enough noise about this someone will actually do something about it.  On my way there now, soapbox out!

  • From: Germany
  • Registered: 2007-04-10
  • Posts: 9,774

Re: Windows 7 Crashing (iMac 24)

jcitarello wrote:

Here's the real kicker, *ALL* the audio interface manufacturers have spread completely erroneous rumors trying to convince everyone that TI is the only chipset that works, when in fact, it's the freakin driver that is the culprit "...because because drivers access hardware functions differently".

Why would other manufacturers blame chipsets for issues of our driver, which never would affect their devices? HeadScratch
I'm afraid you have gotten several unrelated issues mixed up here. Separate issues of LSI or Ricoh/Via/JMicron chips do not involve BSODs.

I guess what I really need to do is start posting my findings over at Gearslutz and few other forums so people can actually see for themselves that it's not the chipset but the drivers that are the are causing this issue.  Maybe if we make enough noise about this someone will actually do something about it.  On my way there now, soapbox out!

The discussion continues here.

Regards
Daniel Fuchs
RME

Regards
Daniel Fuchs
RME

RME Support's Website

  • Registered: 2010-01-27
  • Posts: 17

Re: Windows 7 Crashing (iMac 24)

More excuses.  Read and responded Daniel.

  • From: Germany
  • Registered: 2007-04-10
  • Posts: 9,774

Re: Windows 7 Crashing (iMac 24)

I'm afraid I have to say you continue to mix up unrelated issues.
Since you've decided to bring the issue up on GS, and to avoid confusion with two separate threads, I will close this one and monitor the other. However, I don't see much of a point clearing up obvious misconceptions continuously. The old LSI/Agere issue is not related to this, and we never blamed specific FW chipsets for BSODs or other crashes.


Regards
Daniel Fuchs
RME

Regards
Daniel Fuchs
RME

RME Support's Website