My hardware config is an ASUS P5Q Deluxe Intel Core 2 duo E7300 processor, 4GB RAM and NVIDIA GeForce 7300 LE
/Erik > Peter/Erik > > I checked my device driver details .. Even though it lists the driver > as LSI or TI it is still using 1394ohci.sys for the driver. > You're both right :-) . > > Right now I am using my LSI PCIe card .. I get a BSOD only if I leave > PowerSDR and VAC based software running continuous for 5 hours + > > The last time I ran with my on board Texas Instruments based firewire > I/F the BSOD's occur more frequently . > > My hardware config is an Nforce 680LT motherboard Q6600 quad 4GB > Graphics card Nvidia GE Force 7300 GT. > > Dave > > Peter G. Viscarola wrote: >> I don't know, but there are many possible reasons. The first thing I'd >> suggest is that you look at the driver version information in Device >> Manager, and see if it agrees with what I provided in the minidump. If it >> does not, we have a mystery on our hands. If it does, then... the Microsoft >> 1394 driver is what's installed. >> >> I don't see ANY reason, by the way, for there to be an LSI-specific 1394 >> OHCI driver. The whole POINT of 1394 OHCI is that the host controller's all >> provide the same standardized interface (the "Open Host Controller >> Interface") thus alleviating the need for each vendor to supply their own >> driver. Very confusing... >> >> These are really things ordinary users shouldn't have to get involved in, >> >> P >> >> >>> -----Original Message----- >>> From: Erik Jakobsen [mailto:[email protected]] >>> Sent: Wednesday, December 30, 2009 11:45 AM >>> To: Peter G. Viscarola >>> Cc: Tim Ellison; David Beumer W0DHB; [email protected] >>> Subject: Re: [FlexEdge] FireWire query >>> >>> Hi Peter. >>> >>> Thank you so much for your help. I will carefully study what you have >>> written here. >>> One thing. I have choosen option 3 in the screenshot here: >>> >>> http://www.urbakken.dk/native.jpg >>> >>> But if it's an M$, why is it then named LSI ?. >>> >>> Be back later Peter, and also directly :-) >>> >>> /Erik OZ4KK >>> >>> >>>> I've briefly examined both of the minidumps that Erik sent (Win7, 64- >>>> >>> bit). >>> >>>> As is typical, it's not clear what's causing this crash. It COULD be >>>> >>> the FlexRadio driver, or it could be the 1394OHCI controller driver. >>> Both of Erik's crashes look similar to W0DHB's crashes that I analyzed >>> last month. Of course, this similarity COULD be due to the fact that >>> the system load (1394 isochronous traffic being processed) is pretty >>> much the same as well. >>> >>>> I've included the clean stack trace information for both dumps below >>>> >>> in case anyone is interested. >>> >>>> Given that he'll have the symbols and sources for the FlexRadio >>>> >>> driver, the dev that owns FlexRadio.sys should be able to determine >>> which driver is at fault with a bit of work. It's possible he'll need >>> a full kernel dump (not just a minidump). If he thinks it's likely to >>> be a Microsoft 1394 OHCI driver problem, I strongly recommend the OEM >>> gets Microsoft support involved (either through the OEM's TAM or via >>> per-incident WDK support) and get this tracked down. >>> >>>> These random crashes should NOT occur. >>>> >>>> Though this shouldn't matter, I think Erik said he's running the LSI- >>>> >>> supplied 1394 OHCI driver. However, this doesn't appear to be the >>> case. The data from the crashing module suggests that he's running the >>> Microsoft 1394 driver in both crashes: >>> >>>> Image name: 1394ohci.sys >>>> Timestamp: Mon Jul 13 20:07:12 2009 (4A5BCC30) >>>> CheckSum: 000397AE >>>> ImageSize: 0003E000 >>>> File version: 6.1.7600.16385 >>>> Product version: 6.1.7600.16385 >>>> File flags: 0 (Mask 3F) >>>> File OS: 40004 NT Win32 >>>> File type: 3.7 Driver >>>> File date: 00000000.00000000 >>>> Translations: 0409.04b0 >>>> CompanyName: Microsoft Corporation >>>> ProductName: Microsoft® Windows® Operating System >>>> InternalName: 1394ohci.sys >>>> OriginalFilename: 1394ohci.sys >>>> ProductVersion: 6.1.7600.16385 >>>> FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255) >>>> FileDescription: 1394 OpenHCI Driver >>>> LegalCopyright: © Microsoft Corporation. All rights reserved. >>>> >>>> >>>> The version of the FlexRadio driver that Erik's running dates from 2 >>>> >>> November: >>> >>>> Image path: \SystemRoot\System32\Drivers\FlexRadio.sys >>>> Image name: FlexRadio.sys >>>> Timestamp: Mon Nov 02 16:41:48 2009 (4AEF521C) >>>> CheckSum: 00036485 >>>> ImageSize: 00032580 >>>> Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 >>>> >>>> >>>> Hope some of this is helpful, >>>> >>>> Peter >>>> K1PGV >>>> >>>> --------------- >>>> >>>> Clean Stack Traces >>>> >>>> 12/29 minidump: >>>> >>>> nt!KeBugCheckEx >>>> Wdf01000!FxDmaTransactionBase::Initialize >>>> Wdf01000!imp_WdfDmaTransactionInitialize >>>> 1394ohci!IsochRx::HandleIsochAttachBuffers >>>> 1394ohci!Isoch::HandleIsochAttachBuffers >>>> 1394ohci!Isoch::WdfEvtIoInternalDeviceControl >>>> Wdf01000!FxIoQueue::DispatchRequestToDriver >>>> Wdf01000!FxIoQueue::DispatchEvents >>>> Wdf01000!FxIoQueue::QueueRequestFromForward >>>> Wdf01000!FxIoQueue::ForwardRequestWorker >>>> Wdf01000!FxIoQueue::ForwardRequest >>>> Wdf01000!imp_WdfRequestForwardToIoQueue >>>> 1394ohci!Dispatch::DispatchIrbRequest >>>> 1394ohci!Dispatch::WdfEvtIoInternalDeviceControl >>>> Wdf01000!FxIoQueue::DispatchRequestToDriver >>>> Wdf01000!FxIoQueue::DispatchEvents >>>> Wdf01000!FxIoQueue::QueueRequest >>>> Wdf01000!FxPkgIo::Dispatch >>>> Wdf01000!FxDevice::Dispatch >>>> Wdf01000!imp_WdfRequestSend >>>> 1394ohci!ChildDevice::DispatchIrbRequest >>>> 1394ohci!ChildDevice::HandleIrbRequest >>>> 1394ohci!ChildDevice::WdfEvtIoInternalDeviceControl >>>> Wdf01000!FxIoQueue::DispatchRequestToDriver >>>> Wdf01000!FxIoQueue::DispatchEvents >>>> Wdf01000!FxIoQueue::QueueRequest >>>> Wdf01000!FxPkgIo::Dispatch >>>> Wdf01000!FxDevice::Dispatch >>>> FlexRadio >>>> 0x0 >>>> 0x0 >>>> FlexRadio >>>> 0x0 >>>> >>>> >>>> >>>> 12/30 minidump: >>>> >>>> nt!KeBugCheckEx >>>> Wdf01000!imp_WdfDmaTransactionRelease >>>> 1394ohci!IsochRx::WdfEvtNotificationDpc >>>> Wdf01000!FxDpc::FxDpcThunk >>>> nt!KiRetireDpcList >>>> nt!KxRetireDpcList >>>> nt!KiDispatchInterruptContinue >>>> >>>> >>>> >>>>> -----Original Message----- >>>>> From: [email protected] [mailto:flexedge-boun...@flex- >>>>> radio.biz] On Behalf Of Tim Ellison >>>>> Sent: Wednesday, December 30, 2009 10:33 AM >>>>> To: Erik Jakobsen; David Beumer W0DHB >>>>> Cc: [email protected] >>>>> Subject: Re: [FlexEdge] FireWire query >>>>> >>>>> The problem probably isn't a FlexRadio issue. It looks like it is >>>>> >>> most >>> >>>>> probably the LSI driver that is failing. There isn't much FlexRadio >>>>> can do with the dump. >>>>> >>>>> I recommend that you try and contact the tech support @ LSI and see >>>>> >>> if >>> >>>>> they want the dump file. >>>>> >>>>> This is not an uncommon situation with a new operating system and >>>>> >>> the >>> >>>>> fact that Microsoft changed the 1394 driver architecture is >>>>> >>> compounding >>> >>>>> the problems. >>>>> >>>>> The quickest solution might be to get a different Firewire card that >>>>> does not use the LSI chipset or use the generic (not legacy) Win7 >>>>> 1394ohci.sys driver for the Firewire card. >>>>> >>>>> >>>>> >>>>> -Tim >>>>> >>>>> -----Original Message----- >>>>> From: Erik Jakobsen [mailto:[email protected]] >>>>> Sent: Wednesday, December 30, 2009 12:21 AM >>>>> To: David Beumer W0DHB >>>>> Cc: Tim Ellison; [email protected] >>>>> Subject: Re: [FlexEdge] FireWire query >>>>> >>>>> Yes I did, and after I switched to the LSI chipset based firewire I >>>>> >>> got >>> >>>>> a BSOD. >>>>> I will send you the dump file directly. >>>>> >>>>> -- >>>>> Med venlig hilsen / Best regards >>>>> Erik Jakobsen OZ4KK >>>>> [email protected] >>>>> >>>>> >>>>> >>>>> >>>>>> Erik >>>>>> >>>>>> did you look in c:\windows\minidump ? >>>>>> >>>>>> I was looking at your hardware configuration -- I also have an LSI >>>>>> chipset based firewire card . >>>>>> >>>>>> Dave W0DHB >>>>>> >>>>>> Erik Jakobsen wrote: >>>>>> >>>>>> >>>>>>> Thanks for your comments David. >>>>>>> >>>>>>> I searched for a file, but the 2 I had has dissappeared. >>>>>>> If happens again, I will send it to you. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> _______________________________________________ >>>>> Flexedge mailing list >>>>> [email protected] >>>>> http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz >>>>> This is the FlexRadio Systems e-mail Reflector called FlexEdge. It >>>>> >>> is >>> >>>>> used for posting topics related to SDR software development and >>>>> experimentalist who are using alpha and beta versions of the >>>>> >>> software. >>> >>> -- >>> Med venlig hilsen / Best regards >>> Erik Jakobsen OZ4KK >>> [email protected] >>> >> >> >> >> -- Med venlig hilsen / Best regards Erik Jakobsen OZ4KK [email protected] _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using alpha and beta versions of the software.
