This particular Bug Check (BS0D) is due to the Windows 1394a bus driver
and not with the FLEX-5000 Firewire device driver. From what we have
been told, there is a long standing bug in the Windows XP bus driver
that will corrupt 1394 data packets due to a sequencing problem when
streaming at high data rates causing memory errors (bits in the wrong
place). This software defect in the Windows XP driver is the triggering
mechanism for the Bug Check. There are other factors in play too such
as Firewire card/chipset and bus type (PCIe). It is difficult to
quantify the exact factors that can be changed to mitigate the problem.
As Brian noted, some people experience it, most do not. The previous
3.x version of the FLEX Firewire driver does not stream data as
efficiently (or as quickly) as the 4.0 driver which is why the older
driver version does not usually experience this Bug Check condition.
The out of ordering packet sequencing issue was fixed in Vista. To the
best of my knowledge, this specific issue to date has not been reported
on Vista, Win7, or Win8 machines.
Tim Ellison
On 12/28/2012 12:36 PM, Brian Lloyd wrote:
On Fri, Dec 28, 2012 at 9:30 AM, Bill K7UOP <[email protected]> wrote:
This started happening with installation of PowerSDR 2.4.4 where the radio
firmware and computer Firewire drivers were changed.
I'm closely associated with two stations that run Flex 5000 on Windows XP.
Both stations experience computer crashes to the so called Blue Screen Of
Death (BSOD). The blue screen refers to DRIVER_IRQL_NOT_LESS_OR_EQUAL .
The BSOD only occurs when the Flex 5000 radio is turned on. PowerSDR can be
but does not have to be running.
Analysis of the Minidump file (located in the C:\WINDOWS\Minidump folder)
indicates that the module name is "ohci1394". This is the Firewire
(IEEE-1394) driver.
I know FlexRadio is aware of the problem and has brought it to the
attention of the 3rd party vendor of the Firewire driver used. But the
problem has not been resolved since September. I guess we're at the mercy
of the 3rd party vendor's schedule. I rolled back to PowerSDR 2.3.5 and can
not upgrade until this is fixed.
So, I'm wondering:
1. How many folks running Windows XP are experiencing this?
I have certainly not seen it and I run several machines that use XP and run
3000's and 5000's.
2. Has anyone found a solution?
Have you tried uninstalling the driver through the device manager and then
reinstalling?
_______________________________________________
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 innovation and other technical SDR
topics.
